How severe is CVE-2019-3465?

CVE-2019-3465 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-3465?

CVE-2019-3465 affects the following packages: robrichards/xmlseclibs (Packagist), robrichards/xmlseclibs (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2019-3465?

Update robrichards/xmlseclibs to 3.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-3465 is resolved across your whole dependency graph.

How do I detect CVE-2019-3465 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for robrichards/xmlseclibs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-3465 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2019-3465 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-3465 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-3465?

CVE-2019-3465 has an EPSS (Exploit Prediction Scoring System) score of 3.0%, placing it in the 87th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-3465?

CVE-2019-3465 is classified as CWE-347 (CWE-347). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-3465 published, and has it been updated?

CVE-2019-3465 was published on November 7, 2019 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

CVE-2019-3465 — xmlseclibs

HIGHFix: robrichards/xmlseclibs@0a53d3c

CVE-2019-3465 is a high-severity (CVSS 8.8) CWE-347 vulnerability in robrichards/xmlseclibs. A fix is available for robrichards/xmlseclibs — see the affected versions and patch details below.

Signature validation bypass in XmlSecLibs

Also known asGHSA-pqm6-cgwr-x6pf

Published

Nov 7, 2019

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐘robrichards/xmlseclibs🐘robrichards/xmlseclibs

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Rob Richards XmlSecLibs, all versions prior to v3.0.3, as used for example by SimpleSAMLphp, performed incorrect validation of cryptographic signatures in XML messages, allowing an authenticated attacker to impersonate others or elevate privileges by creating a crafted XML message.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`robrichards/xmlseclibs`	≥ 3.0.0&&< 3.0.4	3.0.4`composer require robrichards/xmlseclibs:^3.0.4`
🐘Packagist	`robrichards/xmlseclibs`	≥ 1.0.0&&< 2.1.1	2.1.1`composer require robrichards/xmlseclibs:^2.1.1`

Affected Products

3 products · 7 configurations

debian linuxdebian

3 versions

8.09.010.0

Application

simplesamlphpsimplesamlphp

≤ 1.17.6

range

Application

xmlseclibsxmlseclibs_project

≥ 3.0.0 && ≤ 3.0.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for robrichards/xmlseclibs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update robrichards/xmlseclibs to 3.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-3465 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-3465 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works