CVE-2026-44649

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
12.2%
KEV
Not listed

Published

May 29, 2026

Last Modified

June 2, 2026

Advisory Details (1)

Auto-updated Jun 20, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Authentication Bypass via SSO Header Injection · Advisory · SillyTavern/SillyTavern · GitHub

https://github.com/SillyTavern/SillyTavern/security/advisories/GHSA-gxx6-h3g6-vwjh

Vendor Advisories for CVE-2026-44649(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
sillytavern1.18.0

Weakness Classification(4)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 89× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 199 total refreshes for this CVE.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-14 18:29 UTCEG score recompute
  4. 2026-07-14 14:06 UTCEG score recompute
  5. 2026-07-13 22:30 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-12 02:49 UTCEG score recompute
  8. 2026-07-11 22:24 UTCEG score recompute
  9. 2026-07-11 17:32 UTCEG score recompute
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-08 22:42 UTCEG score recompute
  13. 2026-07-08 17:23 UTCEG score recompute
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-06 16:27 UTCEPSS rescore
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-02 23:32 UTCEG score recompute
  21. 2026-07-02 19:14 UTCEG score recompute
  22. 2026-07-02 14:08 UTCEG score recompute
  23. 2026-07-02 09:21 UTCEG score recompute
  24. 2026-07-02 04:15 UTCEG score recompute
  25. 2026-07-01 18:51 UTCEG score recompute
Show 75 more
  1. 2026-07-01 15:07 UTCEPSS rescore
  2. 2026-07-01 12:57 UTCEG score recompute
  3. 2026-07-01 08:39 UTCEG score recompute
  4. 2026-07-01 01:31 UTCEG score recompute
  5. 2026-06-30 23:22 UTCEPSS rescore
  6. 2026-06-30 05:38 UTCEG score recompute
  7. 2026-06-30 00:56 UTCEG score recompute
  8. 2026-06-29 19:35 UTCEG score recompute
  9. 2026-06-29 14:06 UTCEPSS rescore
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-29 12:45 UTCEG score recompute
  12. 2026-06-29 00:39 UTCEG score recompute
  13. 2026-06-28 20:21 UTCEG score recompute
  14. 2026-06-28 15:57 UTCEG score recompute
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 11:40 UTCEG score recompute
  17. 2026-06-28 07:22 UTCEG score recompute
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 03:06 UTCEG score recompute
  20. 2026-06-27 22:49 UTCEG score recompute
  21. 2026-06-27 18:32 UTCEG score recompute
  22. 2026-06-27 14:15 UTCEG score recompute
  23. 2026-06-27 09:58 UTCEG score recompute
  24. 2026-06-27 05:41 UTCEG score recompute
  25. 2026-06-27 03:08 UTCEPSS rescore
  26. 2026-06-27 01:24 UTCEG score recompute
  27. 2026-06-26 20:31 UTCEG score recompute
  28. 2026-06-26 16:15 UTCEG score recompute
  29. 2026-06-26 01:50 UTCEG score recompute
  30. 2026-06-25 20:17 UTCEG score recompute
  31. 2026-06-25 15:58 UTCEG score recompute
  32. 2026-06-25 13:49 UTCEPSS rescore
  33. 2026-06-25 13:49 UTCEPSS rescore
  34. 2026-06-25 11:37 UTCEG score recompute
  35. 2026-06-25 07:20 UTCEG score recompute
  36. 2026-06-25 03:01 UTCEG score recompute
  37. 2026-06-24 22:33 UTCEG score recompute
  38. 2026-06-24 15:17 UTCEG score recompute
  39. 2026-06-24 14:05 UTCEPSS rescore
  40. 2026-06-23 21:33 UTCEPSS rescore
  41. 2026-06-22 14:25 UTCEPSS rescore
  42. 2026-06-22 14:25 UTCEPSS rescore
  43. 2026-06-21 14:56 UTCEPSS rescore
  44. 2026-06-21 14:56 UTCEPSS rescore
  45. 2026-06-21 01:59 UTCEPSS rescore
  46. 2026-06-19 19:25 UTCEPSS rescore
  47. 2026-06-18 22:26 UTCEG score recompute
  48. 2026-06-18 17:52 UTCEPSS rescore
  49. 2026-06-18 17:52 UTCEPSS rescore
  50. 2026-06-18 10:23 UTCEG score recompute
  51. 2026-06-18 02:16 UTCEG score recompute
  52. 2026-06-17 22:00 UTCEG score recompute
  53. 2026-06-17 17:53 UTCEPSS rescore
  54. 2026-06-17 17:43 UTCEG score recompute
  55. 2026-06-17 12:36 UTCEG score recompute
  56. 2026-06-17 08:19 UTCEG score recompute
  57. 2026-06-17 04:02 UTCEG score recompute
  58. 2026-06-16 23:45 UTCEG score recompute
  59. 2026-06-16 19:28 UTCEG score recompute
  60. 2026-06-16 17:52 UTCEPSS rescore
  61. 2026-06-16 15:12 UTCEG score recompute
  62. 2026-06-16 10:02 UTCEG score recompute
  63. 2026-06-16 05:44 UTCEG score recompute
  64. 2026-06-16 01:28 UTCEG score recompute
  65. 2026-06-15 21:11 UTCEG score recompute
  66. 2026-06-15 17:49 UTCEPSS rescore
  67. 2026-06-15 13:50 UTCEG score recompute
  68. 2026-06-15 09:34 UTCEG score recompute
  69. 2026-06-15 05:14 UTCEG score recompute
  70. 2026-06-15 00:52 UTCEG score recompute
  71. 2026-06-14 20:35 UTCEG score recompute
  72. 2026-06-14 16:19 UTCEG score recompute
  73. 2026-06-14 12:02 UTCEG score recompute
  74. 2026-06-14 07:46 UTCEG score recompute
  75. 2026-06-14 03:29 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-44649?
CVE-2026-44649 is a critical vulnerability published on May 29, 2026. 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…
When was CVE-2026-44649 disclosed?
CVE-2026-44649 was first published in the National Vulnerability Database on May 29, 2026, with the most recent update on June 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44649 actively exploited?
CVE-2026-44649 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44649?
CVE-2026-44649 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-44649?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44649, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44649

Explore →

Is Your Infrastructure Affected by CVE-2026-44649?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.