ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2017-16931

parser.c in libxml2 before 2.9.5 mishandles parameter-entity references because the NEXTL macro calls the xmlParserHandlePEReference function in the case of a '%' character in a DT

Published Nov 23, 2017 · catalog updated Oct 14, 2026 · parser.c in libxml2 before

Check if you run it

No confirmed exploitation is on record for CVE-2017-16931. EPSS is 4.58%. Act only if a listed version of parser.c in libxml2 before is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (parser.c in libxml2 before).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical9.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
4.58%
Remediation
Advisory link
Affected products
Debian:12 libxml2 · Debian:13 libxml2 · Debian:14 libxml2 · cpe xmlsoft/libxml2

parser.c in libxml2 before 2.9.5 mishandles parameter-entity references because the NEXTL macro calls the xmlParserHandlePEReference function in the case of a '%' character in a DTD name.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Debian:12 libxml20 → 2.9.4+dfsg1-3.1
  • Debian:13 libxml20 → 2.9.4+dfsg1-3.1
  • Debian:14 libxml20 → 2.9.4+dfsg1-3.1
  • cpe xmlsoft/libxml2version unspecified

How to fix CVE-2017-16931

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2017-16931. EPSS is 4.58%. Act only if a listed version of parser.c in libxml2 before is installed.

Which versions are affected?

Compare what you have installed with 0 → 2.9.4+dfsg1-3.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-119: Buffer Overflow. EPSS 4.58%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Debian security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Nov 23, 2017 · NIST NVD

    Detected

    parser.c in libxml2 before 2.9.5 mishandles parameter-entity references because the NEXTL macro calls the xmlParserHandlePEReference function in the case of a '%' character in a DTD name.

  2. Oct 14, 2026 · NIST NVD

    Updated

    parser.c in libxml2 before 2.9.5 mishandles parameter-entity references because the NEXTL macro calls the xmlParserHandlePEReference function in the case of a '%' character in a DTD name.

  3. Oct 14, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    libxml2 fixed in 2.9.4+dfsg1-3.1; libxml2 fixed in 2.9.4+dfsg1-3.1; libxml2 fixed in 2.9.4+dfsg1-3.1

  4. Oct 14, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    libxml2 fixed in 2.9.4+dfsg1-3.1

  5. Oct 14, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    parser.c in libxml2 before 2.9.5 mishandles parameter-entity references because the NEXTL macro calls the xmlParserHandlePEReference function in the case of a '%' character in a DTD name.

Sources

  • CVE.orgVulnerability recordCVE-2017-16931

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2017-16931

    30-day exploitation probability 4.6%

    first.org
  • NIST NVDVulnerability recordCVE-2017-16931

    parser.c in libxml2 before 2.9.5 mishandles parameter-entity references because the NEXTL macro calls the xmlParserHandlePEReference function in the case of a '%' character in a DTD name.

    nvd.nist.gov
  • OpenSSF OSV / OSV ScannerPackage advisoryDEBIAN-CVE-2017-16931
    osv.dev

References

Freshness

Last verified in this catalog Oct 16, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.