Skip to content
Fencer Intel
high 8.8

CVE-2017-9096 json

Improper Restriction of XML External Entity Reference in iText

published 9y ago modified 4mo ago also GHSA-86p9-x5pw-94qx , EUVD-2022-3126

cvss
8.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
9.6%
EPSS 9.6% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

The XML parsers in iText before 5.5.12 and 7.x before 7.0.3 do not disable external entities, which might allow remote attackers to conduct XML external entity (XXE) attacks via a crafted PDF.

Patch / fix

  • maven com.itextpdf:itextpdf 5.5.12, 7.0.3
  • itextpdf itext 5.5.12

Is CVE-2017-9096 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-9096 updated cvss 6.5

itext: External entities not disabled

  • Red Hat JBoss Enterprise Application Platform 5 itext itext Red Hat JBoss SOA Platform 5 itext itext
    affected: no fix planned “Will not fix”
  • Red Hat BPM Suite 6 itext itext Red Hat JBoss BRMS 6 itext itext
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

9.57% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven com.itextpdf:itextpdf
<5.5.12
>=7.0.0, <7.0.3
5.5.12
7.0.3
maven com.lowagie:itext
<=4.2.2
 no fix listed

Classification

Weakness
  • CWE-611 Improper Restriction of XML External Entity Reference

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.