Is robrichards/xmlseclibs vulnerable?

Composer robrichards/xmlseclibs has 5 known advisories in the phpwarden feed. Feed 2026.10.29.1, updated 2026-10-28.

5advisories
0critical
0on CISA KEV
0no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2019-3465Signature validation bypass in XmlSecLibshigh8.8>=3.0.0 and <3.0.4 or >=1.0.0 and <2.1.1 or >=1.0.0 and <2.0.0 or >=2.0.0 and <2.1.13.0.4, 2.1.1
CVE-2025-66578robrichards/xmlseclibs has an Libxml2 Canonicalization error which can bypass Digest/Signature validationmedium6.0<3.1.43.1.4
CVE-2026-32313xmlseclibs: Missing AES-GCM Authentication Tag Validation on Encrypted Nodes Allows for Unauthorized Decryptionhigh8.2<3.1.53.1.5
GHSA-2g98-f9jv-w8c5robrichards/xmlseclibs XPath injectionhigh7.5>=1.0.0 and <3.0.23.0.2
2018-09-27Filter input to avoid XPath injectionunknown0.0>=1.0.0 and <2.0.0 or >=2.0.0 and <3.0.0 or >=3.0.0 and <3.0.23.0.2

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# one-time install
pip install phpwarden

# then
phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.