Skip to main content
No exploitation reportedFix available

CVE-2020-15216

No exploitation reported by the sources we read.

  • Published2020-09-29
  • WeaknessCWE-347

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

In goxmldsig (XML Digital Signatures implemented in pure Go) before version 1.1.0, with a carefully crafted XML file, an attacker can completely bypass signature validation and pass off an altered file as a signed one. A patch is available, all users of goxmldsig should upgrade to at least revision f6188febf0c29d7ffe26a0436212b19cb9615e64 or version 1.1.0

Timeline

dates in UTC
  1. 2020-09-2916:15CVE publishedNVD

Versions per branch

NVD · OSV
Fedoraproject fedora
BranchAffectedFixed in
32.x= 32no fix published
33.x= 33no fix published
Goxmldsig project goxmldsig
BranchAffectedFixed in
1.1< 1.1.01.1.0

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • golang-github-russellhaering-goxmldsigUbuntu:22.04:LTSall versions · no fixed version listed
  • golang-github-russellhaering-goxmldsigUbuntu:20.04:LTSall versions · no fixed version listed
  • golang-github-russellhaering-goxmldsigUbuntu:18.04:LTSall versions · no fixed version listed
  • golang-github-russellhaering-goxmldsigDebian:12all versions · fixed in 1.1.0-1

Full record on NVD

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CNACVSS 3.15.3known since 2026-10-23
  • NVDCVSS 3.16.5read 2026-10-23
  • NVDCVSS 2.04.3read 2026-10-23
  • CNAweakness (CWE)CWE-347known since 2026-10-23
  • NVDweakness (CWE)CWE-347read 2026-10-23
  • FIRST EPSSEPSS score0.9 %2026-11-08
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryMODERATE2021-05-24

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Published
2020-09-29
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-q547-gmf8-8jr7

Frequently asked questions

What is CVE-2020-15216?

In goxmldsig (XML Digital Signatures implemented in pure Go) before version 1.1.0, with a carefully crafted XML file, an attacker can completely bypass signature validation and pass off an altered file as a signed one. A patch is available, all users of goxmldsig should upgrade to at least revision f6188febf0c29d7ffe26a0436212b19cb9615e64 or version 1.1.0

Is CVE-2020-15216 actively exploited?

Active exploitation of CVE-2020-15216 has not been confirmed. Its EPSS score was 0.9% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-15216?

CVE-2020-15216 has a CVSS v3 base score of 6.5 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N.

Running russellhaering/goxmldsig? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record