Vulnerability in Freedesktop Poppler (CVE-2026-93313)
Summary
Vulnerability in Freedesktop Poppler (CVE-2026-93313). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
A vulnerability was found in Freedesktop Poppler 26.07.0. The impacted element is the function JBIG2Stream::readCodeTableSeg of the file poppler/JBIG2Stream.cc. Performing a manipulation results in integer overflow. The attack can be initiated remotely. The exploit has been made public and could be used. The patch is named eb87cf711563894649bd0c365baa479401dc6d51. To fix this issue, it is recommended to deploy a patch.
Source: NIST National Vulnerability Database 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-93313 has been found in Freedesktop Poppler.
Risk of unauthorized operations or information disclosure. CVSS score: 6.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Freedesktop Poppler CVE-2026-93313" on the vendor's site.
CVE-2026-93313 (Freedesktop Poppler) — CWE-189 / CVSS v3 6.3
Attack vector: remote (network-reachable) / unauthenticated
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-189) exists in Freedesktop Poppler.
Check the vendor advisory for the affected versions of Freedesktop Poppler.
Severity: Medium (CVSS 6.3/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・依存マニフェストで Freedesktop Poppler を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com
- web gitlab.freedesktop.org
- web gitlab.freedesktop.org
- web gitlab.freedesktop.org
- web vuldb.com
- web vuldb.com
- web vuldb.com
- web vuldb.com
- web nvd.nist.gov
- web github.com