Is robrichards/xmlseclibs 2.1 vulnerable?
Composer · 2 releases from 2.1.0 to 2.1.1 · latest robrichards/xmlseclibs is 4.0.2 · checked 18 Nov 2026
Yes: 3 known advisories
Yes. robrichards/xmlseclibs 2.1.1, the last 2.1 release, is affected by 3 known security advisories (2 high, 1 medium), including CVE-2026-32313, CVE-2025-66578. 1 more affects earlier 2.1.x releases. Upgrade to 3.1.5 or later to fix all of them.
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
Advisories affecting robrichards/xmlseclibs 2.1.1
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
robrichards/xmlseclibs XPath injection
- Affected
- >=1.0.0 <3.0.2
- Fixed in
- 3.0.2
Fixed within 2.1.x, affecting earlier releases
Signature validation bypass in XmlSecLibs
- Affected
- >=3.0.0 <3.0.4 · >=1.0.0 <2.1.1
- Fixed in
- 2.1.1, 3.0.4
Every robrichards/xmlseclibs 2.1.x release
Affected: 2.1.0 to 2.1.1. Latest robrichards/xmlseclibs: 4.0.2.
| Version | Known advisories |
|---|---|
| robrichards/xmlseclibs 2.1.1 | CVE-2026-32313, CVE-2025-66578, GHSA-2g98-f9jv-w8c5 |
| robrichards/xmlseclibs 2.1.0 | CVE-2026-32313, CVE-2025-66578, GHSA-2g98-f9jv-w8c5, CVE-2019-3465 |
Which of your client projects are still on robrichards/xmlseclibs 2.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.