CVE-2026-32600
XML-security lib auth tag length bypass enables decryption and forgery.
Is CVE-2026-32600 being exploited?
Not confirmed. CVE-2026-32600 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.15% probability of exploitation in the next 30 days.
How severe is CVE-2026-32600?
CVE-2026-32600 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-32600?
Yes. A fix has been recorded for CVE-2026-32600. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-32600 affect?
CVE-2026-32600 affects XML-Security library (pre-2.3.1, pre-1.13.9). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-32600?
Upgrade to 2.3.1 or 1.13.9+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker can brute-force tag length to decrypt data, recover GHASH key, and forge ciphertexts, bypassing authentication.
Patch when possible
- affected>= 2.0.0 and < 2.3.1
- affected< 1.13.9
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.