CVE-2020-7595 — libxml as used in Nokogiri has an infinite loop in a certain end-of-file situation
xmlStringLenDecodeEntities in parser.c in libxml2 2.9.10 has an infinite loop in a certain end-of-file situation.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 7.8% (30-day exploitation probability)+14
- Technical severity (high)+6
- CISA SSVC: exploitation "poc"+5
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — gitlab.gnome.org (NIST National Vulnerability Database)
- Documented patch — www.oracle.com (NIST National Vulnerability Database)
- Documented patch — www.oracle.com (NIST National Vulnerability Database)
- Rubygems Nokogiri: fixed in version 1.10.8 — github.com (GitHub Security Advisories)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Canonical Ubuntu Linux, Debian Debian Linux, Fedoraproject Fedora…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- EPSS ahead of 95% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (denial of service), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Canonical | Ubuntu Linux | version 12.04version 14.04version 16.04version 18.04version 19.10 | Vulnerable | NIST National Vulnerability Database |
| Debian | Debian Linux | version 9.0 | Vulnerable | NIST National Vulnerability Database |
| Fedoraproject | Fedora | version 31version 32version 30 | Vulnerable | NIST National Vulnerability Database |
| Netapp | Clustered Data Ontap | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H300e Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H300s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H410c Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H410s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H500e Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H500s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H700e Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | H700s Firmware | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Smi-s Provider | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Snapdrive | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Steelstore Cloud Integrated Storage | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Netapp | Symantec Netbackup | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Oracle | Communications Cloud Native Core Network Function Cloud Native Environment | version 1.10.0 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Enterprise Manager Base Platform | version 13.5.0.0version 13.4.0.0 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Enterprise Manager Ops Center | version 12.4.0.0 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Mysql Workbench | ≤ 8.0.26 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Peoplesoft Enterprise Peopletools | version 8.58 | Vulnerable | NIST National Vulnerability Database |
| Oracle | Real User Experience Insight | version 13.3.1.0version 13.4.1.0version 13.5.1.0 | Vulnerable | NIST National Vulnerability Database |
| Siemens | Sinema Remote Connect Server | < 3.0 | Vulnerable | NIST National Vulnerability Database |
| Xmlsoft | Libxml2 | version 2.9.10 | Vulnerable | NIST National Vulnerability Database |
| Rubygems | Nokogiri | < 1.10.8 | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.1 | High | 3.9 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 7.5 | CVSS 3.1 | High | 3.9 | 3.6 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database |
| 7.5 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 7.5 | CVSS 3.1 | High | — | — | CISA-ADP via CVE Program (cve.org) e CISA ADP |
| 5.0 | CVSS 2.0 | Medium | 10.0 | 2.9 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 7.84%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Track CPU/memory spikes and availability drops correlated with request patterns.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · rubygems/nokogiri
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · xmlsoft/libxml2, fedoraproject/fedora, canonical/ubuntu linux, debian/debian linux, siemens/sinema remote connect server
- CVSS changed · 7.5
- Source status changed · → Modified
- Record created in this database
- 2020
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
24 on the record
- gitlab.gnome.org/GNOME/libxml2/commit/0e1a49c89076
- www.oracle.com/security-alerts/cpuoct2021.html
- www.oracle.com/security-alerts/cpuapr2022.html
- usn.ubuntu.com/4274-1/
- github.com/rubysec/ruby-advisory-db/blob/master/gems/nokogiri/CVE-2020-7595.yml
- cert-portal.siemens.com/productcert/pdf/ssa-292794.pdf
- security.netapp.com/advisory/ntap-20200702-0005/
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/545SPO
- nvd.nist.gov/vuln/detail/CVE-2020-7595
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/5R55
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JDPF
- www.oracle.com/security-alerts/cpujul2020.html
- us-cert.cisa.gov/ics/advisories/icsa-21-103-08
- github.com/sparklemotion/nokogiri/issues/1992
- lists.opensuse.org/opensuse-security-announce/2020-05/msg00047.html
- security.gentoo.org/glsa/202010-04
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JDPF3A
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5R55ZR
- lists.debian.org/debian-lts-announce/2020/09/msg00009.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/545S
- github.com/advisories/GHSA-7553-jr98-vx47
- www.oracle.com/security-alerts/cpujul2022.html
- cert-portal.siemens.com/productcert/html/ssa-398330.html
- cert-portal.siemens.com/productcert/html/ssa-292794.html
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-87264 Improper Access Control in Oracle Peoplesoft Enterprise Peopletools Sep 15, 2026
- High CVE-2026-83018 Improper Access Control in Oracle Peoplesoft Enterprise Peopletools Sep 15, 2026
- High CVE-2026-83019 Improper Access Control in Oracle Peoplesoft Enterprise Peopletools Sep 15, 2026
- High CVE-2026-83017 Improper Access Control in Oracle Peoplesoft Enterprise Peopletools Sep 15, 2026
- High CVE-2026-83016 Improper Access Control in Oracle Peoplesoft Enterprise Peopletools Sep 15, 2026
- High CVE-2026-83014 Improper Access Control in Oracle Peoplesoft Enterprise Peopletools Sep 15, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2020-7595 is "libxml as used in Nokogiri has an infinite loop in a certain end-of-file situation", rated High. It affects Ubuntu Linux (Canonical); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 7.84% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.