Is robrichards/xmlseclibs 3.1 vulnerable?
Composer · 6 releases from 3.1.0 to 3.1.5 · latest robrichards/xmlseclibs is 4.0.2 · checked 18 Nov 2026
No known advisories in the last release
robrichards/xmlseclibs 3.1.5, the last 3.1 release, has no known advisories. 2 advisories affect earlier 3.1.x releases, so update to 3.1.5.
composer require robrichards/xmlseclibs:^3.1.5Is your project on an affected robrichards/xmlseclibs?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 3.1.x, affecting earlier releases
xmlseclibs: Missing AES-GCM Authentication Tag Validation on Encrypted Nodes Allows for Unauthorized Decryption
- Affected
- <3.1.5
- Fixed in
- 3.1.5
robrichards/xmlseclibs has an Libxml2 Canonicalization error which can bypass Digest/Signature validation
- Affected
- <3.1.4
- Fixed in
- 3.1.4
Every robrichards/xmlseclibs 3.1.x release
Affected: 3.1.0 to 3.1.4. 3.1.5 is not affected. Latest robrichards/xmlseclibs: 4.0.2.
| Version | Known advisories |
|---|---|
| robrichards/xmlseclibs 3.1.5 | None |
| robrichards/xmlseclibs 3.1.4 | CVE-2026-32313 |
| robrichards/xmlseclibs 3.1.3 | CVE-2026-32313, CVE-2025-66578 |
| robrichards/xmlseclibs 3.1.2 | CVE-2026-32313, CVE-2025-66578 |
| robrichards/xmlseclibs 3.1.1 | CVE-2026-32313, CVE-2025-66578 |
| robrichards/xmlseclibs 3.1.0 | CVE-2026-32313, CVE-2025-66578 |
Which of your client projects are still on robrichards/xmlseclibs 3.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact robrichards/xmlseclibs version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other robrichards/xmlseclibs versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.