Security readout for executives and security teams
Plain-English summary
SillyTavern instances using Authelia or Authentik SSO before version 1.18.0 can trust login headers sent by any reachable network client. An attacker who can directly reach the SillyTavern port may sign in as any user, including an administrator, without a password.
Executive priority
Treat this as urgent for any SSO-enabled SillyTavern deployment. The vulnerable condition allows passwordless administrative access if the service is directly reachable, so remediation should prioritize upgrade and network exposure reduction.
Technical view
Before 1.18.0, SillyTavern accepts Remote-User and X-Authentik-Username headers for SSO login without validating they came from a trusted reverse proxy. Exposure requires sso.autheliaAuth or sso.authentikAuth set to true. The reported impact is full confidentiality, integrity, and availability compromise with CVSS 3.1 score 9.8.
Likely exposure
Exposure is limited to SillyTavern versions before 1.18.0 with Authelia or Authentik SSO enabled. Risk is highest where the SillyTavern port is reachable directly by untrusted users or networks instead of only through the intended reverse proxy.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. The issue is nevertheless low-complexity and unauthenticated when the vulnerable SSO configuration is enabled and the application port is directly reachable.
Researcher notes
The key exposure condition is configuration-dependent, not default. Focus validation on version, SSO flags, and whether reverse-proxy-only access is actually enforced. The public bundle identifies the fix version but does not provide evidence of exploitation in the wild.
Mitigation direction
- Upgrade SillyTavern to version 1.18.0 or later.
- Disable sso.autheliaAuth and sso.authentikAuth until the fix is applied.
- Block direct access to the SillyTavern port from untrusted networks.
- Ensure access flows only through the intended trusted reverse proxy.
- Review the GitHub advisory and CVE record for vendor guidance.
Validation and detection
- Inventory SillyTavern instances and confirm installed versions.
- Check config.yaml for sso.autheliaAuth or sso.authentikAuth set to true.
- Confirm direct network access to the SillyTavern port is blocked.
- Verify upgraded systems report version 1.18.0 or later.
- Review recent authentication and administrative activity for anomalies.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-290: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-346: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-807: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-44649 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/SillyTavern/SillyTavern/security/advisories/GHSA-gxx6-h3g6-vwjhCVE reference, GitHub_M · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.