PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-54079 veraPDF CVE debrief

veraPDF validation provides PDF/A and PDF/UA validation, feature reporting, and metadata repair. From 1.17.35 until 1.30.2 and 1.31.71, veraPDF-validation contains an XML External Entity (XXE) vulnerability in validation-model/src/main/java/org/verapdf/gf/model/impl/pd/GFPDAcroForm.java in the getdynamicRender() method, where a crafted PDF containing a malicious XFA stream can cause external entity expansion during PDF/UA-1 validation and allow local file disclosure or outbound server-side requests.

Vendor
veraPDF
Product
veraPDF-validation
CVSS
HIGH 8.7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-29
Original CVE updated
2026-10-23
Advisory published
2026-07-29
Advisory updated
2026-10-23

Who should care

Defenders responsible for PDF processing workflows, particularly those using veraPDF-validation, should assess exposure and prioritize updates to mitigate the risk of local file disclosure or unauthorized server-side requests.

Why it matters

The veraPDF-validation XXE vulnerability allows for local file disclosure and potential outbound server-side requests during PDF/UA-1 validation. Defenders should verify and update veraPDF-validation, assess exposure in PDF processing workflows, and monitor for suspicious activities.

  • Local file disclosure through crafted PDF processing
  • Potential for outbound server-side requests via XXE expansion
  • Verification of veraPDF-validation version and exposure in PDF workflows
  • Monitoring for suspicious PDF uploads or processing activities

Technical summary

The veraPDF-validation library, used for PDF/A and PDF/UA validation, contains an XML External Entity (XXE) vulnerability in versions between 1.17.35 and 1.30.2 and 1.31.71. This vulnerability, located in the getdynamicRender() method of GFPDAcroForm.java, allows for external entity expansion during PDF/UA-1 validation when processing crafted PDFs with malicious XFA streams. The vulnerability can lead to local file disclosure or outbound server-side requests.

Defensive priority

Defenders should prioritize verifying and updating veraPDF-validation to versions 1.30.2 or 1.31.71, assessing exposure in PDF processing workflows, and monitoring for suspicious PDF uploads or processing activities.

Recommended defensive actions

  • Verify and update veraPDF-validation to versions 1.30.2 or 1.31.71
  • Assess exposure in PDF processing workflows
  • Monitor for suspicious PDF uploads or processing activities
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the XXE vulnerability in veraPDF-validation, including affected versions and fixed versions. Defenders should verify and update veraPDF-validation to versions 1.30.2 or 1.31.71, assess exposure in PDF processing workflows, and monitor for suspicious PDF uploads or processing activities. Evidence is limited to public CVE details and NVD assessments; further verification is recommended.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-54079 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-54079

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-54079 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-54079

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.