The XML parsers used in iText versions prior to 5.5.12 and 7.x prior to 7.0.3 do not have external entity processing disabled. This allows attackers to exploit XML External Entity (XXE) vulnerabilities by submitting crafted PDF files containing malicious XML. The vulnerable code path is triggered when iText parses XML content embedded in or referenced by a PDF, allowing the attacker to influence the XML parser's behavior.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept (POC) exploit for CVE-2017-9096, targeting XXE (XML External Entity) vulnerabilities in PDF processing libraries, specifically iText 7.0.2 for Java. The repository contains instructions and code to craft a malicious PDF file with embedded XXE payloads in both the XMP metadata and XFA form sections. The README.md provides detailed steps for modifying a sample PDF to include the XXE payload, referencing an attacker-controlled URL (http://attacker.net). The Java code (Exec.java) loads the crafted PDF and processes its XMP metadata and XFA form, demonstrating how a vulnerable application might trigger the XXE payload. The attack vector is file-based, requiring a victim application to open the malicious PDF. The repository structure includes a Maven build file (pom.xml), the exploit code, and documentation. No weaponized or automated exploitation is present; this is a POC for research and demonstration purposes.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.