Vulnerability in org.verapdf:parser (CVE-2026-54081)
Summary
Vulnerability in org.verapdf:parser (CVE-2026-54081). Risk of unauthorized operations or information disclosure. Exploitable via for. Mitigation: upgrade to 1.31.23 or later.
Original description
The description as published by the source.
Summary
Description
A PostScript-interpreter-driven Denial of Service (CWE-1325) vulnerability in veraPDF allows a remote attacker to exhaust validator memory or CPU by submitting a PDF whose Type 1 font /FontFile is a font program containing attacker-supplied PostScript. veraPDF's Type 1 font program parser dispatches every cleartext token through a hardcoded operator allow-list whose members include the unbounded array N allocation operator and the for control operator with no zero-increment guard. This affects all current versions of veraPDF-parser.
Details
The vulnerability resides in veraPDF-parser. Type 1 font program streams referenced from any Type 1 font's /FontDescriptor /FontFile are parsed by Type1FontProgram (veraPDF-parser/src/main/java/org/verapdf/pd/font/type1/Type1FontProgram.java), which extends PSParser. parseFont reads cleartext PostScript tokens until it encounters eexec (which switches into the encrypted private dictionary parser) or end-of-stream. Each non-eexec token is dispatched via toExecute, which gates execution behind a hardcoded allow-list.
The allow-list explicitly admits both ARRAY (Type1FontProgram.java:98) and FOR (Type1FontProgram.java:100). When either keyword passes the gate, operator.execute delegates straight into the generic PSOperator implementation (org.verapdf.parser.postscript.PSOperator, methods array() at PSOperator.java:536-547 and opFor() at PSOperator.java:571-592), which apply…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54081 has been found in org.verapdf:parser.
Attackers can target a specific entry point like for over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.verapdf:parser to 1.31.23 or later.
If unsure, ask your IT team or search "org.verapdf:parser CVE-2026-54081" on the vendor's site.
CVE-2026-54081 (org.verapdf:parser) — CWE-1325
Attack surface: for / Type1FontProgram / PSParser / parseFont
Patched: 1.31.23 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1325) exists in org.verapdf:parser. Attackers reach the vulnerable code path via for.
Check the vendor advisory for the affected versions of org.verapdf:parser. Attack surface: for / Type1FontProgram / PSParser / parseFont.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.31.23.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.verapdf:parser を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.verapdf:parser to 1.31.23ステージング環境で 1.31.23 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com