Vulnerability in Foxit PDF Editor/Reader's handling of (CVE-2026-91814)
Summary
Vulnerability in Foxit PDF Editor/Reader's handling of (CVE-2026-91814). Data can be tampered with by attackers.
Original description
The description as published by the source.
A signature validation vulnerability exists in Foxit PDF Editor/Reader’s handling of incrementally updated PDF documents. Changes to visible document content may not invalidate the existing signature, allowing attackers to alter signed content and potentially carry out content spoofing while the document continues to appear validly signed.
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-91814 has been found in Foxit PDF Editor/Reader's handling of.
Data can be tampered with by attackers. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Foxit PDF Editor/Reader's handling of CVE-2026-91814" on the vendor's site.
CVE-2026-91814 (Foxit PDF Editor/Reader's handling of) — CWE-347 / CVSS v3 5.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-347) exists in Foxit PDF Editor/Reader's handling of.
Check the vendor advisory for the affected versions of Foxit PDF Editor/Reader's handling of.
Severity: Medium (CVSS 5.3/10). Data can be tampered with by attackers.
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・依存マニフェストで Foxit PDF Editor/Reader's handling of を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web foxit.com
- web nvd.nist.gov
- web github.com