dbcve.org
CWE-290Weakness · CWE-290

CVE-2026-44649

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SillyTavern is a locally installed user interface that allows users to interact with text generation large language models, image generation engines, and text-to-speech voice models. Prior to 1.18.0, SillyTavern accepts Remote-User (Authelia) and X-Authentik-Username (Authentik) HTTP headers to automatically log in users when SSO is configured. There is no validation that these headers originate from a trusted reverse proxy. Any network client that can reach the SillyTavern port directly can inject these headers and authenticate as any user, including administrators, without a password. This vulnerability is exploitable only when sso.autheliaAuth: true or sso.authentikAuth: true is set in config.yaml (both default to false). This vulnerability is fixed in 1.18.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SillyTavern prior to 1.18.0 trusts SSO headers (Remote-User for Authelia, X-Authentik-Username for Authentik) without validating they originate from a trusted reverse proxy. Any network client that can reach the SillyTavern port directly can inject these headers to authenticate as any user, including administrators, without a password.

MitigationUpgrade to SillyTavern 1.18.0 or later. Additionally, ensure the reverse proxy is the only entity able to reach SillyTavern (not directly exposed) and verify no unauthorized access occurred while SSO was enabled on vulnerable versions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check SillyTavern version
    Locate the installed SillyTavern directory and check the version file (often version.txt, package.json, or shown in the startup logs). Compare the version number to the 1.18.0 release.
    Affected if The installed version is earlier than 1.18.0
  2. Check if autheliaAuth is enabled
    Examine the SillyTavern configuration file (config.yaml, config.json, or the settings UI) for the autheliaAuth setting. Look for a configuration option enabling Authelia SSO integration.
    Affected if autheliaAuth is enabled (set to true or configured with an Authelia provider)
  3. Check if authentikAuth is enabled
    Examine the SillyTavern configuration file (config.yaml, config.json, or the settings UI) for the authentikAuth setting. Look for a configuration option enabling Authentik SSO integration.
    Affected if authentikAuth is enabled (set to true or configured with an Authentik provider)
  4. Verify reverse proxy header sanitization
    Inspect the reverse proxy configuration (nginx, caddy, traefik, or similar) deployed in front of SillyTavern. Confirm that the proxy is configured to strip or override the Remote-User and X-Authentik-Username headers from incoming client requests before forwarding to SillyTavern.
    Affected if No reverse proxy is in use, or the proxy does not sanitize authentication headers from incoming client requests

You are affected if running SillyTavern version before 1.18.0 with either autheliaAuth or authentikAuth enabled, and the deployment does not have a trusted reverse proxy that strips these headers from external requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to SillyTavern 1.18.0 or later. Additionally, ensure the reverse proxy is the only entity able to reach SillyTavern (not directly exposed) and verify no unauthorized access occurred while SSO was enabled on vulnerable versions.

Recommended fix High confidence

1.18.0

  1. 1. Back up your current SillyTavern installation and configuration files before upgrading.
  2. 2. Upgrade SillyTavern to version 1.18.0 or later.
  3. 3. After upgrading, verify that your SSO configuration (sso.autheliaAuth or sso.authentikAuth in config.yaml) is correctly set if you use SSO.
  4. 4. Test authentication to ensure the upgrade did not break legitimate SSO functionality.
  5. 5. If you were not using SSO (both sso.autheliaAuth and sso.authentikAuth were false), the vulnerability was not exploitable, but upgrading to 1.18.0 is still recommended for defense-in-depth.
Caveat Minimal; this is a security patch release. Users using SSO should verify their authentication works correctly after upgrading.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44649 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44649 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data