CVE-2026-92899

MEDIUMPre-NVD 4.84.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 4.8 from GitHub Security Advisory (severity: MODERATE) published 2026-09-30. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 4.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory

Also known asEUVD-2026-89798 (ENISA EUVD) · GHSA-pw3c-6w58-28w4 (GitHub Security Advisories)Source: ENISA EUVD

4.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 4.8Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

Apache WSS4J remembers the Nonce of each UsernameToken it accepts, so a captured token cannot be reused. It stored the Nonce as raw base64 text, but authentication decodes that text and uses the bytes.The same bytes can be written as base64 in several ways. An attacker who captured an authenticated request could re-send it with a space added to the Nonce: the password digest still verified, but the token no longer matched the remembered one, so the replay was accepted. Since a UsernameToken does not cover the message body, the captured token could then be reused on requests of the attacker's choosing until it expired. Affects deployments with a nonce replay cache configured, as Apache CXF has by default, and only tokens using a password digest. The cache is now keyed on the decoded Nonce. Users are recommended to upgrade to versions 4.0.2 or 3.0.6 or 2.4.4, which fix this issue.

CVSS v3
4.8
EG Score
4.8MEDIUMmedium confidence
EG Risk
22
EG Risk 22/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity48% × 45%
Impact severity (EG Severity): CVSS 4.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.8): severity, escalated by confirmed exploitation. This CVE's 4.8 is its impact severity (EG Severity), not escalated.

EG Severity
4.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-06). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 30, 2026

Last Modified

November 6, 2026

Advisory Details (2)

Auto-updated Sep 30, 2026
Fix named in the CVE record.
Web page

oss-security - CVE-2026-92899: Apache WSS4J: UsernameToken replay protection bypassed by re-encoding the Nonce

http://www.openwall.com/lists/oss-security/2026/09/30/13

Vendor Advisories for CVE-2026-92899(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
wss4j1.6.19-3, 1.6.19-4
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
wss4j1.6.19-4
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
wss4j1.6.19-4
  • every version on: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 34× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  3. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-11-06 19:28 UTCGHSA enrichmentGHSA-pw3c-6w58-28w4 · GitHub severity MODERATE · GitHub CVSS 4.8
  8. 2026-11-06 18:23 UTCEchelonGraph re-scored
  9. 2026-11-06 18:23 UTCGHSA enrichmentGHSA-pw3c-6w58-28w4 · GitHub severity MODERATE · GitHub CVSS 4.8
  10. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-10-30 15:33 UTCEchelonGraph re-scored
  19. 2026-10-30 15:33 UTCGHSA enrichmentGHSA-pw3c-6w58-28w4 · GitHub CVSS 4.8
  20. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-10-25 13:50 UTCEchelonGraph re-scored
Show 57 more
  1. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  2. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  3. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  4. 2026-10-22 12:29 UTCEchelonGraph re-scored
  5. 2026-10-22 12:29 UTCGHSA enrichmentGHSA-pw3c-6w58-28w4 · GitHub CVSS 4.8
  6. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  7. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  8. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  9. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-10-18 02:59 UTCEchelonGraph re-scored
  11. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  14. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  17. 2026-10-12 14:44 UTCEchelonGraph re-scored
  18. 2026-10-11 19:13 UTCEchelonGraph re-scored
  19. 2026-10-11 16:29 UTCEchelonGraph re-scored
  20. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  21. 2026-10-11 13:43 UTCEchelonGraph re-scored
  22. 2026-10-11 09:00 UTCEchelonGraph re-scored
  23. 2026-10-11 09:00 UTCGHSA enrichmentGHSA-pw3c-6w58-28w4 · GitHub CVSS 4.8
  24. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-10-10 10:22 UTCEchelonGraph re-scored
  26. 2026-10-10 10:22 UTCGHSA enrichmentGHSA-pw3c-6w58-28w4 · GitHub CVSS 4.8
  27. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  28. 2026-10-09 11:45 UTCEchelonGraph re-scored
  29. 2026-10-09 11:45 UTCGHSA enrichmentGHSA-pw3c-6w58-28w4 · GitHub CVSS 4.8
  30. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  31. 2026-10-08 12:11 UTCEchelonGraph re-scored
  32. 2026-10-08 12:11 UTCGHSA enrichmentGHSA-pw3c-6w58-28w4 · GitHub CVSS 4.8
  33. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  34. 2026-10-07 13:34 UTCEchelonGraph re-scored
  35. 2026-10-07 13:34 UTCGHSA enrichmentGHSA-pw3c-6w58-28w4 · GitHub CVSS 4.8
  36. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  37. 2026-10-06 14:54 UTCEchelonGraph re-scored
  38. 2026-10-06 14:54 UTCGHSA enrichmentGHSA-pw3c-6w58-28w4 · GitHub CVSS 4.8
  39. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  40. 2026-10-05 16:17 UTCEchelonGraph re-scored
  41. 2026-10-05 16:17 UTCGHSA enrichmentGHSA-pw3c-6w58-28w4 · GitHub CVSS 4.8
  42. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  43. 2026-10-04 17:40 UTCGHSA enrichmentGHSA-pw3c-6w58-28w4 · GitHub CVSS 4.8
  44. 2026-10-03 19:02 UTCEchelonGraph re-scored
  45. 2026-10-03 19:01 UTCGHSA enrichmentGHSA-pw3c-6w58-28w4 · GitHub CVSS 4.8
  46. 2026-10-02 20:22 UTCEchelonGraph re-scored
  47. 2026-10-02 20:22 UTCGHSA enrichmentGHSA-pw3c-6w58-28w4 · GitHub CVSS 4.8
  48. 2026-10-02 13:40 UTCEchelonGraph re-scored
  49. 2026-10-02 13:39 UTCGHSA enrichmentGHSA-pw3c-6w58-28w4 · GitHub CVSS 4.8
  50. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  51. 2026-10-01 14:59 UTCGHSA enrichmentGHSA-pw3c-6w58-28w4 · GitHub CVSS 4.8
  52. 2026-09-30 16:23 UTCEchelonGraph re-scored
  53. 2026-09-30 16:23 UTCGHSA enrichmentGHSA-pw3c-6w58-28w4 · GitHub CVSS 4.8
  54. 2026-09-30 13:18 UTCEchelonGraph re-scoredFirst assessed: 4.8 MEDIUM
  55. 2026-09-30 13:18 UTCNVD updateCVSS v3 → 4.8 · severity → MEDIUM
  56. 2026-09-30 12:28 UTCEchelonGraph re-scored
  57. 2026-09-30 12:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92899?
CVE-2026-92899 is a medium-severity vulnerability; its CVE record was published on September 30, 2026. Apache WSS4J remembers the Nonce of each UsernameToken it accepts, so a captured token cannot be reused. It stored the Nonce as raw base64 text, but authentication decodes that text and uses the bytes.The same bytes can be written as base64 in several ways. An attacker who captured an authenticated…
When was the CVE record for CVE-2026-92899 published?
The CVE record for CVE-2026-92899 was published on September 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 6, 2026; the record at its source may have been updated since.
Is CVE-2026-92899 actively exploited?
CVE-2026-92899 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92899?
CVE-2026-92899 has a CVSS v3.1 base score of 4.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-92899?
The CVE record for CVE-2026-92899 names the fix: "Users are recommended to upgrade to versions 4.0.2 or 3.0.6 or 2.4.4, which fix this issue." The vendor advisories EchelonGraph has for CVE-2026-92899 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-92899?

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