SSRF (Server-Side Request Forgery) in JGM Pandoc (CVE-2025-51591)
Summary
SSRF in JGM Pandoc (CVE-2025-51591). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
A Server-Side Request Forgery (SSRF) in JGM Pandoc v3.6.4 allows attackers to gain access to and compromise the whole infrastructure via injecting a crafted iframe. Note: Some users have stated that Pandoc by default can retrieve and parse untrusted HTML content which can enable SSRF vulnerabilities. Using the ‘--sandbox’ option or ‘pandoc-server’ can mitigate such vulnerabilities. Using pandoc with an external ‘--pdf-engine’ can also enable SSRF vulnerabilities, such as CVE-2022-35583 in wkhtmltopdf.
Source: NIST National Vulnerability Database NVD
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-2025-51591 has been found in JGM Pandoc.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "JGM Pandoc CVE-2025-51591" on the vendor's site.
CVE-2025-51591 (JGM Pandoc) — CWE-918 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
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.
SSRF (CWE-918) exists in JGM Pandoc.
Check the vendor advisory for the affected versions of JGM Pandoc.
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
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・依存マニフェストで JGM Pandoc を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2025-51591 pandoc
- Ubuntu UBUNTU-CVE-2025-51591 pandoc
References
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- report github.com
- report github.com
- report github.com
- web cve@mitre.org
- web github.com
- web github.com
- web wiz.io
- web pandoc.org
- web not-applicable:http://jgm.com/
- web not-applicable:http://pandoc.com/