How severe is CVE-2017-5992?

CVE-2017-5992 has a CVSS 3.x base score of 8.2, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity none, and availability high.

Is CVE-2017-5992 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (63rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-5992?

CVE-2017-5992 affects Python Openpyxl. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2017-5992?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2017-5992 published?

CVE-2017-5992 was published on 2017-02-15 and last updated on 2026-06-17.

CVE-2017-5992

CVE-2017-5992 is a high-severity vulnerability in Python Openpyxl with a CVSS 3.x base score of 8.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-611.

Key facts

Severity: High (CVSS 3.x base score 8.2)
CVSS v2: 5.8
EPSS exploit prediction: 1% (63rd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-611
Affected product: Python Openpyxl
Published: 2017-02-15
Last modified: 2026-06-17

Description

Openpyxl 2.4.1 resolves external entities by default, which allows remote attackers to conduct XXE attacks via a crafted .xlsx document.

Frequently asked questions

What is CVE-2017-5992?: Openpyxl 2.4.1 resolves external entities by default, which allows remote attackers to conduct XXE attacks via a crafted .xlsx document.
How severe is CVE-2017-5992?: CVE-2017-5992 has a CVSS 3.x base score of 8.2, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity none, and availability high.
Is CVE-2017-5992 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (63rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-5992?: CVE-2017-5992 affects Python Openpyxl. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-5992?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-5992 published?: CVE-2017-5992 was published on 2017-02-15 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:python:openpyxl:2.4.1:*:*:*:*:*:*:*

Other CWE-611 (Improper Restriction of XML External Entity Reference (XXE)) vulnerabilities

CVE-2022-22486 — Critical (CVSS 10.0): IBM Tivoli Workload Scheduler 9.4, 9.5, and 10.1 is vulnerable to an XML External Entity Injection (XXE) attack when…
CVE-2019-14678 — Critical (CVSS 10.0): SAS XML Mapper 9.45 has an XML External Entity (XXE) vulnerability that can be leveraged by malicious attackers in…
CVE-2015-9280 — Critical (CVSS 10.0): MailEnable before 8.60 allows XXE via an XML document in the request.aspx Options parameter.
CVE-2018-1000838 — Critical (CVSS 10.0): autopsy version <= 4.9.0 contains a XML External Entity (XXE) vulnerability in CaseMetadata XML Parser that can result…
CVE-2018-1000837 — Critical (CVSS 10.0): UML Designer version <= 8.0.0 contains a XML External Entity (XXE) vulnerability in XML parser for plugins that can…
CVE-2018-1000835 — Critical (CVSS 10.0): KeePassDX version <= 2.5.0.0beta17 contains a XML External Entity (XXE) vulnerability in kdbx file parser that can…

Browse all CWE-611 (Improper Restriction of XML External Entity Reference (XXE)) vulnerabilities →