Skip to content
major vulnerability· requires attention

Widely-used PHP XML security library; high-severity cryptography flaw enabling data decryption and ciphertext forgery across apps.

Cryptography

CVE-2026-32313

8.2
High
EPSS 0.15%Patch availableMar 16, 2026

xmlseclibs <3.1.5 tag-length validation bypass enables decryption and ciphertext forgery.

common questions

Is CVE-2026-32313 being exploited?

Not confirmed. CVE-2026-32313 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-32313?

CVE-2026-32313 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-32313?

Yes. A fix has been recorded for CVE-2026-32313. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-32313 affect?

CVE-2026-32313 affects xmlseclibs (PHP) <= 3.1.4. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-32313?

Upgrade to 3.1.5+; audit all deployments using xmlseclibs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
xmlseclibs (PHP) <= 3.1.4
impact

Tag-length validation bypass allows brute-forcing and decrypting AES-GCM data; attacker can forge ciphertexts without the key.

action required

Patch when possible

affected versions
robrichards xmlseclibs
  • affected< 3.1.5

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free