veraPDF validation up to 1.30.1/1.31.70 AcroForm GFPDAcroForm.java getdynamicRender xml external entity reference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 2.38 |
Summary
A vulnerability categorized as critical has been discovered in veraPDF validation up to 1.30.1/1.31.70. Affected is the function getdynamicRender of the file validation-model/src/main/java/org/verapdf/gf/model/impl/pd/GFPDAcroForm.java of the component AcroForm Handler. Executing a manipulation can lead to xml external entity reference.
This vulnerability is handled as CVE-2026-54079. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability has been found in veraPDF validation up to 1.30.1/1.31.70 and classified as critical. This vulnerability affects the function getdynamicRender of the file validation-model/src/main/java/org/verapdf/gf/model/impl/pd/GFPDAcroForm.java of the component AcroForm Handler. The manipulation with an unknown input leads to a xml external entity reference vulnerability. The CWE definition for the vulnerability is CWE-611. The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
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. This issue is fixed in versions 1.30.2 and 1.31.71.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-54079 since 06/11/2026. The exploitation appears to be easy. The attack can be initiated remotely. There are known technical details, but no exploit is available.
Upgrading to version 1.30.2 or 1.31.71 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
- 1.30.0
- 1.30.1
- 1.31.0
- 1.31.1
- 1.31.2
- 1.31.3
- 1.31.4
- 1.31.5
- 1.31.6
- 1.31.7
- 1.31.8
- 1.31.9
- 1.31.10
- 1.31.11
- 1.31.12
- 1.31.13
- 1.31.14
- 1.31.15
- 1.31.16
- 1.31.17
- 1.31.18
- 1.31.19
- 1.31.20
- 1.31.21
- 1.31.22
- 1.31.23
- 1.31.24
- 1.31.25
- 1.31.26
- 1.31.27
- 1.31.28
- 1.31.29
- 1.31.30
- 1.31.31
- 1.31.32
- 1.31.33
- 1.31.34
- 1.31.35
- 1.31.36
- 1.31.37
- 1.31.38
- 1.31.39
- 1.31.40
- 1.31.41
- 1.31.42
- 1.31.43
- 1.31.44
- 1.31.45
- 1.31.46
- 1.31.47
- 1.31.48
- 1.31.49
- 1.31.50
- 1.31.51
- 1.31.52
- 1.31.53
- 1.31.54
- 1.31.55
- 1.31.56
- 1.31.57
- 1.31.58
- 1.31.59
- 1.31.60
- 1.31.61
- 1.31.62
- 1.31.63
- 1.31.64
- 1.31.65
- 1.31.66
- 1.31.67
- 1.31.68
- 1.31.69
- 1.31.70
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Xml external entity referenceCWE: CWE-611 / CWE-610
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: validation 1.30.2/1.31.71
Timeline
06/11/2026 CVE reserved07/29/2026 Advisory disclosed
07/29/2026 VulDB entry created
07/29/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2026-54079 (🔒)
GCVE (CVE): GCVE-0-2026-54079
GCVE (VulDB): GCVE-100-384196
Entry
Created: 07/29/2026 17:39Changes: 07/29/2026 17:39 (57)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.