NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

CVE-2020-15216 — goxmldsig

MEDIUMFix: russellhaering/goxmldsig@f6188fe

CVE-2020-15216 is a medium-severity (CVSS 6.5) CWE-347 vulnerability in github.com/russellhaering/goxmldsig. A fix is available for github.com/russellhaering/goxmldsig — see the affected versions and patch details below.

github.com/russellhaering/goxmldsig vulnerable to Signature Validation Bypass

Also known asGHSA-q547-gmf8-8jr7GO-2020-0050
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk
0.00%0.47%0.93%1.40%0.2%0.9%May 26Sep 26Nov 26

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

1 pkg affected
🐹github.com/russellhaering/goxmldsig

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

Description

Impact

With a carefully crafted XML file, an attacker can completely bypass signature validation and pass off an altered file as a signed one.

Patches

A patch is available, all users of goxmldsig should upgrade to v1.1.0.

For more information

If you have any questions or comments about this advisory open an issue at https://github.com/russellhaering/goxmldsig

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/russellhaering/goxmldsigall versions1.1.0go get github.com/russellhaering/goxmldsig@v1.1.0

Affected Products

2 products · 3 configurations
OS
fedorafedoraproject
2 versions
3233
Application
goxmldsiggoxmldsig_project
< 1.1.0
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update github.com/russellhaering/goxmldsig to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-15216 is resolved across your whole dependency graph.

  3. 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

### Impact With a carefully crafted XML file, an attacker can completely bypass signature validation and pass off an altered file as a signed one. ### Patches A patch is available, all users of goxmldsig should upgrade to v1.1.0. ### For more information If you have any questions or comments about this advisory open an issue at https://github.com/russellhaering/goxmldsig
O3 Security · Impact-Aware SCA

Is CVE-2020-15216 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-15216: goxmldsig — Fixed in 1.1.0