CVE-2026-12057
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWhen the application executes the JavaScript script embedded in the PDF within the sandbox, it fails to intercept some dangerous interfaces, which allows remote scripts to be loaded, resulting in arbitrary code execution.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a sandbox escape vulnerability where the application's PDF JavaScript sandbox fails to intercept dangerous interfaces, allowing embedded scripts to load remote JavaScript and achieve arbitrary code execution. The vulnerability stems from incomplete filtering of APIs that enable network requests or script loading from external sources.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2026-06-15CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Foxit Ai is installedSearch for Foxit Ai in standard installation directories. On Windows, check Program Files and Program Files (x86). On macOS, check /Applications. Look for folders named 'Foxit Ai' or 'Foxit' with Ai branding.Affected if Foxit Ai application is found installed on the system
-
Confirm installed versionLocate the Foxit Ai executable, right-click and select Properties to view File Version. Alternatively, open the application and navigate to Help > About Foxit Ai to view the exact version number.Affected if Version is before June 15, 2026 (any version < 2026-06-15)
-
Check if PDF JavaScript is enabledOpen Foxit Ai preferences or settings. Navigate to the JavaScript or Security section. Look for an option controlling JavaScript execution within PDF documents and determine if it is enabled.Affected if PDF JavaScript execution is enabled in the application settings
-
Determine exposure to untrusted PDFsReview recent document history or check if the application is configured to automatically open PDF attachments from email clients or web browsers.Affected if User regularly opens PDF files from untrusted or external sources such as email attachments or web downloads
System is affected if Foxit Ai version < 2026-06-15 is installed with PDF JavaScript enabled and the user processes untrusted PDF documents.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2026-06-15
Implement comprehensive interception of all dangerous JavaScript interfaces in the PDF sandbox, particularly those enabling remote script loading or network communication, and enforce strict Content Security Policy for PDF-embedded scripts.
- Consultation6.0 h
- Implementation20.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12057 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12057 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data