Is simplesamlphp/xml-security 2.1 vulnerable?

Composer · 3 releases from 2.1.0 to 2.1.2 · latest simplesamlphp/xml-security is 3.1.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. simplesamlphp/xml-security 2.1.2, the last 2.1 release, is affected by 1 known security advisory (1 high), including CVE-2026-32600. Upgrade to 2.3.1 or later to fix all of them.

Upgrade with:composer require simplesamlphp/xml-security:^2.3.1

Is your project on an affected simplesamlphp/xml-security?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting simplesamlphp/xml-security 2.1.2

  • HighCVE-2026-32600GHSA-r353-4845-pr5p13 Mar 2026

    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.1.x release

Affected: 2.1.0 to 2.1.2. Latest simplesamlphp/xml-security: 3.1.0.

VersionKnown advisories
simplesamlphp/xml-security 2.1.2CVE-2026-32600
simplesamlphp/xml-security 2.1.1CVE-2026-32600
simplesamlphp/xml-security 2.1.0CVE-2026-32600

Which of your client projects are still on simplesamlphp/xml-security 2.1?

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

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.