Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2009-0837: Stack-based Buffer Overflow in Foxit Reader 3.0 Open/Execute Action

Published Mar 10, 2009 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS10.0Critical · v2
EPSS75.8%100th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Foxit Software
IdentifiersCVE-2009-0837CWE-121

A stack-based buffer overflow exists in Foxit Reader 3.0 (builds 1120 and 1301) in the handling of the filename argument for the 'Open/Execute a file' action in PDF files. By supplying an overly long relative or absolute path as the filename, an attacker can trigger a buffer overflow, leading to memory corruption. This vulnerability can be exploited remotely via a maliciously crafted PDF file, potentially allowing arbitrary code execution with the privileges of the user running Foxit Reader. The vulnerability was discovered by Francisco Falcón of Core Security.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to execute arbitrary code on the target system with the privileges of the current user. The attacker can craft a PDF file with a maliciously long filename in an Open/Execute action, which, when opened in a vulnerable version of Foxit Reader, results in memory corruption and control over program execution flow. This can be further facilitated by heap spraying via embedded JavaScript in the PDF.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, block or restrict the opening of untrusted PDF files, especially those containing embedded actions or JavaScript. Disable JavaScript execution in Foxit Reader where feasible. Employ endpoint security solutions to detect and block exploitation attempts.

Remediation

Patch, then assume compromise.

Upgrade Foxit Reader to version 3.0 build 1506 or later, which includes proper length checks on the filename argument and introduces user prompts for local file execution. Ensure all users are running a non-vulnerable version.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Foxit SoftwareReader3.0application
FAQ

Frequently asked questions

Is CVE-2009-0837 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2009-0837 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2009-0837?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2009-0837, the earliest disclosed Mar 9, 2009.
Is there a patch for CVE-2009-0837?
Upgrade Foxit Reader to version 3.0 build 1506 or later, which includes proper length checks on the filename argument and introduces user prompts for local file execution. Ensure all users are running a non-vulnerable version.
What products are affected by CVE-2009-0837?
Foxit Software Reader3.0.
How severe is CVE-2009-0837?
CVE-2009-0837 has a CVSS v2 score of 10.0 (Critical) and an EPSS score of 75.8% (100th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.