Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2020-29511: The encoding/xml package in Go (all versions) does not correctly preserve the semantics of element namespace p

59
This month
CRITICAL 9.8REMOTEUPGRADEMITIGATE

CVE-2020-29511 is a critical-severity flaw (CVSS 9.8) affecting go, trident. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The encoding/xml package in Go (all versions) does not correctly preserve the semantics of element namespace prefixes during tokenization round-trips, which allows an attacker to craft inputs that behave in conflicting ways during different stages of processing in affected downstream applications.

Why this priority

  • Critical severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score9.8 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance2.0% (top 20%)
CISA exploited listNo
WeaknessCWE-115
Published2020-12-14
Last modified2026-06-17
Publisher (CNA): Mattermost, Inc. · Vendor: golang · netapp

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

golang go UPGRADE
Affected: < 1.17
Fixed in: 1.17
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy go || rpm -q go || go --version
2. UPGRADE to 1.17 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade go
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade go
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
netapp trident MITIGATE
Affected: all versions
Fixed in: no fixed release known
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy trident || rpm -q trident || trident --version
No fixed or unaffected release known
Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-29511?

go: upgrade to 1.17; trident: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2020-29511 being exploited?

CVE-2020-29511 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-29511 affect?

CVE-2020-29511 affects go, trident. Severity is critical (CVSS 9.8). The encoding/xml package in Go (all versions) does not correctly preserve the semantics of element namespace prefixes during tokenization round-trips, which allows an attacker to craft inputs that behave in conflicting ways during different

How urgent is CVE-2020-29511?

Priority 59/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

Go (Golang) vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.