CVE-2026-32600

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 95% 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
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

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

xml-security is a library that implements XML signatures and encryption. Prior to versions 2.3.1 and 1.13.9, XML nodes encrypted with either aes-128-gcm, aes-192-gcm, or aes-256-gcm lack validation of the authentication tag length. An attacker can use this to brute-force an authentication tag, recover the GHASH key, and decrypt the encrypted nodes. It also allows to forge arbitrary ciphertexts without knowing the encryption key. This vulnerability is fixed in 2.3.1 and 1.13.9.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
41(Track)
EG Risk 41/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
Severity82% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

March 16, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 2, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

Missing AES-GCM Authentication Tag Validation on Encrypted Nodes Allows for Unauthorized Decryption · Advisory · simplesamlphp/xml-security · GitHub

https://github.com/simplesamlphp/xml-security/security/advisories/GHSA-r353-4845-pr5p
github_commit Patch Available

commit fdc12449e959 (simplesamlphp/xml-security)

Patch available: simplesamlphp/xml-security v3.0.0 (contains commit fdc12449e959)

https://github.com/simplesamlphp/xml-security/commit/fdc12449e959c610943f9fd428e95e3832d74c25
github_commit

commit cad6d57cf0a5 (simplesamlphp/xml-security)

Fix landed in simplesamlphp/xml-security commit cad6d57cf0a5 — awaiting tagged release

https://github.com/simplesamlphp/xml-security/commit/cad6d57cf0a5a0b7e0cc4e4a5b18752e56eb1520

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
simplesamlphp/xml-securityv0.0.1 ... v1.9.6 (113 versions)1.13.9—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 18:38 UTCOSV refresh
  16. 2026-09-02 14:11 UTCEPSS rescore
  17. 2026-09-01 13:53 UTCEPSS rescore
  18. 2026-09-01 04:39 UTCEPSS rescore
  19. 2026-09-01 04:39 UTCEPSS rescore
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 35 more
  1. 2026-08-24 14:17 UTCEPSS rescore
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 11:28 UTCEG score recompute
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 07:33 UTCEG score recompute
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-12 22:27 UTCEG score recompute
  16. 2026-08-12 13:50 UTCEPSS rescore
  17. 2026-08-11 21:37 UTCEG score recompute
  18. 2026-08-11 04:45 UTCEG score recompute
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-09 18:43 UTCEG score recompute
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-07 17:49 UTCEG score recompute
  23. 2026-08-06 19:43 UTCEG score recompute
  24. 2026-08-06 13:46 UTCEPSS rescore
  25. 2026-08-06 01:48 UTCEG score recompute
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-04 15:10 UTCEPSS rescore
  28. 2026-08-04 00:59 UTCEG score recompute
  29. 2026-08-03 10:36 UTCEPSS rescore
  30. 2026-08-02 17:01 UTCEG score recompute
  31. 2026-08-02 02:27 UTCEPSS rescore
  32. 2026-08-01 04:16 UTCEPSS rescore
  33. 2026-07-30 16:28 UTCEPSS rescore
  34. 2026-07-30 01:30 UTCEPSS rescore
  35. 2026-07-27 14:43 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-32600?
CVE-2026-32600 is a high vulnerability published on March 16, 2026. xml-security is a library that implements XML signatures and encryption. Prior to versions 2.3.1 and 1.13.9, XML nodes encrypted with either aes-128-gcm, aes-192-gcm, or aes-256-gcm lack validation of the authentication tag length. An attacker can use this to brute-force an authentication tag,…
When was CVE-2026-32600 disclosed?
CVE-2026-32600 was first published in the National Vulnerability Database on March 16, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32600 actively exploited?
CVE-2026-32600 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.6% of all scored CVEs.
What is the CVSS score of CVE-2026-32600?
CVE-2026-32600 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-32600?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32600, 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-32600

Explore →

Is Your Infrastructure Affected by CVE-2026-32600?

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

Start Free Scan →Browse All CVEs