CVE-2026-85532

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.5% (45th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS
Trending — 3 sources updated this week

Also known asEUVD-2026-89791 (ENISA EUVD) · GHSA-5x6j-m6jc-q2r5 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

Apache WSS4J accepted attacker-controlled derived-key lengths and offsets without adequate bounds. This could permit cryptographically weak keys or excessive CPU and memory consumption when processing crafted WS-Security messages. The fixes enforce a minimum key length of 16 bytes, a maximum length of 512 bytes, and a maximum offset of 4096 bytes. Users are recommended to upgrade to versions 4.0.2 or 3.0.6 or 2.4.4, which fix this issue.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
45th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.CISA-ADP (Vulnrichment) CVSS v3.1 · CVSS v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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 low or medium mission impact; Attend at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

October 2, 2026

Advisory Details (2)

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

oss-security - CVE-2026-85532: Apache WSS4J: Insufficient Validation of Derived-Key Parameters

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

Vendor Advisories for CVE-2026-85532(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(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 67× 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 it from the CNA feed. 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). Most recent first.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  4. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  5. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  6. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  7. 2026-10-27 12:32 UTCEG score recompute
  8. 2026-10-27 12:32 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  9. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  10. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  11. 2026-10-25 13:55 UTCEG score recompute
  12. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  14. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  15. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  18. 2026-10-19 14:18 UTCEG score recompute
  19. 2026-10-19 14:18 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  20. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  21. 2026-10-18 03:05 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  23. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  24. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
Show 60 more
  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-10-13 05:27 UTCEG score recompute
  3. 2026-10-13 05:26 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-10-12 14:52 UTCEG score recompute
  6. 2026-10-11 23:18 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  7. 2026-10-11 19:17 UTCEG score recompute
  8. 2026-10-11 16:34 UTCEG score recompute
  9. 2026-10-11 13:51 UTCEG score recompute
  10. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-10-11 10:28 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  12. 2026-10-10 21:39 UTCEG score recompute
  13. 2026-10-10 21:38 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  14. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  15. 2026-10-10 08:20 UTCEG score recompute
  16. 2026-10-10 08:20 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  17. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  18. 2026-10-09 19:31 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  19. 2026-10-09 06:42 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  20. 2026-10-08 17:53 UTCEG score recompute
  21. 2026-10-08 17:53 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  22. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  23. 2026-10-08 04:59 UTCEG score recompute
  24. 2026-10-08 04:59 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  25. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  26. 2026-10-07 16:09 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  27. 2026-10-07 03:06 UTCEG score recompute
  28. 2026-10-07 03:06 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  29. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  30. 2026-10-06 14:17 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  31. 2026-10-06 01:27 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  32. 2026-10-06 01:26 UTCEG score recompute
  33. 2026-10-06 01:26 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  34. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  35. 2026-10-05 12:31 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  36. 2026-10-04 23:42 UTCEG score recompute
  37. 2026-10-04 23:42 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  38. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  39. 2026-10-04 10:52 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  40. 2026-10-03 22:04 UTCEG score recompute
  41. 2026-10-03 22:04 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  42. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  43. 2026-10-03 09:14 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  44. 2026-10-02 20:23 UTCEG score recompute
  45. 2026-10-02 20:22 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  46. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  47. 2026-10-02 10:54 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  48. 2026-10-01 22:06 UTCEG score recompute
  49. 2026-10-01 22:05 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  50. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  51. 2026-10-01 09:11 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  52. 2026-09-30 20:23 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  53. 2026-09-30 19:51 UTCEG score recomputeFirst assessed: 7.5 HIGH
  54. 2026-09-30 19:51 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  55. 2026-09-30 19:50 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  56. 2026-09-30 16:23 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  57. 2026-09-30 13:23 UTCGHSA enrichmentGHSA-5x6j-m6jc-q2r5
  58. 2026-09-30 12:20 UTCNVD update
  59. 2026-09-30 12:02 UTCEG score recompute
  60. 2026-09-30 12:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-85532?
CVE-2026-85532 is a high-severity vulnerability; its CVE record was published on September 30, 2026. Apache WSS4J accepted attacker-controlled derived-key lengths and offsets without adequate bounds. This could permit cryptographically weak keys or excessive CPU and memory consumption when processing crafted WS-Security messages. The fixes enforce a minimum key length of 16 bytes, a maximum length…
When was the CVE record for CVE-2026-85532 published?
The CVE record for CVE-2026-85532 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 October 2, 2026; the record at its source may have been updated since.
Is CVE-2026-85532 actively exploited?
CVE-2026-85532 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-85532?
CVE-2026-85532 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-85532?
The CVE record for CVE-2026-85532 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-85532 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-85532

Explore →

Is Your Infrastructure Affected by CVE-2026-85532?

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