Is simplesamlphp/xml-security 2.3 vulnerable?
Composer · 2 releases from 2.3.0 to 2.3.1 · latest simplesamlphp/xml-security is 3.1.0 · checked 18 Nov 2026
No known advisories in the last release
simplesamlphp/xml-security 2.3.1, the last 2.3 release, has no known advisories. 1 advisory affects earlier 2.3.x releases, so update to 2.3.1.
composer require simplesamlphp/xml-security:^2.3.1Is your project on an affected simplesamlphp/xml-security?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 2.3.x, affecting earlier releases
simplesamlphp/xml-security: Missing AES-GCM Authentication Tag Validation on Encrypted Nodes Allows for Unauthorized Decryption
- Affected
- >=2.0.0 <2.3.1 · <1.13.9
- Fixed in
- 1.13.9, 2.3.1
Every simplesamlphp/xml-security 2.3.x release
Affected: 2.3.0. 2.3.1 is not affected. Latest simplesamlphp/xml-security: 3.1.0.
| Version | Known advisories |
|---|---|
| simplesamlphp/xml-security 2.3.1 | None |
| simplesamlphp/xml-security 2.3.0 | CVE-2026-32600 |
Which of your client projects are still on simplesamlphp/xml-security 2.3?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact simplesamlphp/xml-security version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other simplesamlphp/xml-security versions
- simplesamlphp/xml-security 3.1
- simplesamlphp/xml-security 3.0
- simplesamlphp/xml-security 2.2
- simplesamlphp/xml-security 2.1
- simplesamlphp/xml-security 2.0
- simplesamlphp/xml-security 1.13
- simplesamlphp/xml-security 1.12
- simplesamlphp/xml-security 1.11
- simplesamlphp/xml-security 1.10
- simplesamlphp/xml-security 1.9
- simplesamlphp/xml-security 1.8
- All simplesamlphp/xml-security advisories
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.