Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2021-3537: A vulnerability found in libxml2 in versions before 2.9.11 shows that it did not propagate errors while parsin

53
This month
MEDIUM 5.9REMOTEWATCHLISTUPGRADEMITIGATEMITIGATE

CVE-2021-3537 is a medium-severity flaw (CVSS 5.9) affecting libxml2, jboss core services, enterprise linux. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability found in libxml2 in versions before 2.9.11 shows that it did not propagate errors while parsing XML mixed content, causing a NULL dereference. If an untrusted XML document was parsed in recovery mode and post-validated, the flaw could be used to crash the application. The highest threat from this vulnerability is to system availability.

Why this priority

  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score5.9 (Medium)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance3.6% (top 11%)
CISA exploited listNo
WeaknessCWE-476
Published2021-05-14
Last modified2026-10-14
Publisher (CNA): Red Hat, Inc. · Vendor: debian · fedoraproject · netapp · redhat · xmlsoft

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

xmlsoft libxml2 UPGRADE
Affected: < 2.9.11
Fixed in: 2.9.11
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy libxml2 || rpm -q libxml2 || libxml2 --version
2. UPGRADE to 2.9.11 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade libxml2
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade libxml2
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
redhat jboss core services 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 jboss-core-services || rpm -q jboss-core-services || jboss-core-services --version
No fixed or unaffected release known
Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.
redhat enterprise linux MITIGATE
Affected: 6.0 · 7.0 · 8.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 6.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
debian debian linux MITIGATE
Affected: 9.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 9.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
fedoraproject fedora MITIGATE
Affected: 33 · 34
Fixed in: no fixed release known
Safe to downgrade to: a release before 33
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
netapp active iq unified manager 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 active-iq-unified-manager || rpm -q active-iq-unified-manager || active-iq-unified-manager --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-2021-3537?

libxml2: upgrade to 2.9.11; jboss core services: mitigate or apply the listed mitigation; enterprise linux: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2021-3537 being exploited?

CVE-2021-3537 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-2021-3537 affect?

CVE-2021-3537 affects libxml2, jboss core services, enterprise linux. Severity is medium (CVSS 5.9). A vulnerability found in libxml2 in versions before 2.9.11 shows that it did not propagate errors while parsing XML mixed content, causing a NULL dereference. If an untrusted XML document was parsed in recovery mode and post-validated, the

How urgent is CVE-2021-3537?

Priority 53/100. Remotely exploitable, no login, no user action; On your watchlist

Software pages

Debian vulnerabilities · JBoss and WildFly vulnerabilities · libxml2 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.