CVE-2026-5795

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 57% 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
Trending — 3 sources updated this week
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.4Exploit: None knownExposed: 0

A fix is available — apply it.

In Eclipse Jetty, the class JASPIAuthenticator initiates the authentication checks, which set two ThreadLocal variable.

Upon returning from the initial checks, there are conditions that cause an early return from the JASPIAuthenticator code without clearing those ThreadLocals.

A subsequent request using the same thread inherits the ThreadLocal values, leading to a broken access control and privilege escalation.

CVSS v3
7.4
EG Score
7.4(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

April 8, 2026

Last Modified

September 14, 2026

Advisory Details (1)

Auto-updated Jun 15, 2026
No patch confirmed yet.
generic

[Eclipse Jetty] JASPI access control escalation (#92) · Issues · Eclipse Projects Security / cve-assignment · GitLab

https://gitlab.eclipse.org/security/cve-assignment/-/issues/92

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatoffline-knowledge-portal/rhokp-rhel9:17822393702026-06-23redhat
redhatjetty-ee10-webapp2026-06-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(12 across 5 ecosystems)
Maven(6)
PackageVulnerable rangeFixed inDependents
org.eclipse.jetty.ee10:jetty-ee1012.0.0 ... 12.0.9 (33 versions)9.4.60
org.eclipse.jetty.ee10:jetty-ee10-jaspi12.0.0 ... 12.0.9 (34 versions)12.0.34
org.eclipse.jetty.ee11:jetty-ee11-jaspi12.1.0 ... 12.1.7 (8 versions)12.0.34
org.eclipse.jetty.ee8:jetty-ee8-jaspi12.0.10 ... 12.0.9 (32 versions)12.0.34
org.eclipse.jetty.ee9:jetty-ee9-jaspi12.0.0 ... 12.0.9 (34 versions)12.0.34
org.eclipse.jetty:jetty-jaspi9.4.0.v20161208 ... 9.4.9.v20180320 (74 versions)9.4.61
Debian:13(2)
PackageVulnerable rangeFixed inDependents
jetty1212.0.17-3 ... 12.0.33-1 (6 versions)
jetty99.4.57-1 ... 9.4.58-2 (6 versions)
Debian:14(2)
PackageVulnerable rangeFixed inDependents
jetty1212.0.17-3 ... 12.0.33-1 (6 versions)
jetty99.4.57-1 ... 9.4.58-2 (6 versions)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
jetty99.4.39-3 ... 9.4.58-2 (35 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
jetty99.4.50-4 ... 9.4.58-2 (18 versions)

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 44× 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 223 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-5795?
CVE-2026-5795 is a high vulnerability published on April 8, 2026. In Eclipse Jetty, the class JASPIAuthenticator initiates the authentication checks, which set two ThreadLocal variable. Upon returning from the initial checks, there are conditions that cause an early return from the JASPIAuthenticator code without clearing those ThreadLocals. A subsequent request…
When was CVE-2026-5795 disclosed?
CVE-2026-5795 was first published in the National Vulnerability Database on April 8, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5795 actively exploited?
CVE-2026-5795 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.3% of all scored CVEs.
What is the CVSS score of CVE-2026-5795?
CVE-2026-5795 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-5795?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5795, 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-5795

Explore →

Is Your Infrastructure Affected by CVE-2026-5795?

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