# CVE-2010-20010: Foxit PDF Reader < 4.2.0.0928 Title Stack Buffer Overflow

> A stack buffer overflow in Foxit PDF Reader allows arbitrary code execution when a user opens a maliciously crafted PDF file.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Aug 2025
- **Updated:** 15 May 2026
- **Also known as:** GHSA-2x66-7652-38fv

## What is CVE-2010-20010?

CVE-2010-20010 is a high-severity memory corruption vulnerability in Foxit PDF Reader, published on 20 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Foxit PDF Reader before 4.2.0.0928 does not properly bound-check the /Title entry in the PDF Info dictionary. A specially crafted PDF with an overlong Title string can overflow a fixed-size stack buffer, corrupt the Structured Exception Handler (SEH) chain, and lead to arbitrary code execution in the context of the user who opens the file.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2010-20010?


## How do I fix CVE-2010-20010?

No fix has been published for CVE-2010-20010 yet. Limit exposure of the affected software until one is available.

## Is CVE-2010-20010 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-20010 exists.

Public exploit code:

- Foxit PDF Reader v4.1.1 Title Stack Buffer Overflow (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-20010 and fix it if it is affected.

What it is: CVE-2010-20010 is a high-severity memory corruption vulnerability in Foxit PDF Reader, published on 20 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2010-20010 exists.

Affected product: Foxit PDF Reader. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2010-20010/ (Markdown: https://insights.sbomify.com/CVE-2010-20010/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2010-20010
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2010-20010
- OSV: https://osv.dev/vulnerability/CVE-2010-20010

---
From sbomify Insights: https://insights.sbomify.com/CVE-2010-20010/
Summaries are generated and may contain mistakes; the official description above is the record.