CVE-2026-57239

HIGHNVD 7.88.2
EchelonGraph scoreHIGH confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-07-08. NVD baseline CVSS 7.8; sources differ by 0.4.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The user-controllable executable files will be directly executed by high-privilege processes, allowing low-privilege users to have the opportunity to elevate their privileges to NT AUTHORITY\SYSTEM.

CVSS v3
7.8
EG Score
8.2(high)
EG Risk
53(Track)
EG Risk 53/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
6.6%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 9, 2026

Advisory Details (1)

Auto-updated Jul 8, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-57239(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-25 14:18 UTCEPSS rescore
  2. 2026-07-25 14:18 UTCEPSS rescore
  3. 2026-07-24 14:18 UTCEPSS rescore
  4. 2026-07-24 14:18 UTCEPSS rescore
  5. 2026-07-23 14:18 UTCEPSS rescore
  6. 2026-07-23 03:20 UTCEG score recompute
  7. 2026-07-22 14:08 UTCEPSS rescore
  8. 2026-07-20 17:08 UTCEPSS rescore
  9. 2026-07-19 14:31 UTCEPSS rescore
  10. 2026-07-19 14:31 UTCEPSS rescore
  11. 2026-07-18 10:04 UTCEPSS rescore
  12. 2026-07-16 20:09 UTCGHSA enrichment
  13. 2026-07-16 17:03 UTCEPSS rescore
  14. 2026-07-16 08:50 UTCGHSA enrichment
  15. 2026-07-15 21:31 UTCGHSA enrichment
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 10:11 UTCGHSA enrichment
  19. 2026-07-15 02:00 UTCEPSS rescore
  20. 2026-07-15 02:00 UTCEPSS rescore
  21. 2026-07-14 22:51 UTCGHSA enrichment
  22. 2026-07-14 11:29 UTCGHSA enrichment
  23. 2026-07-14 00:10 UTCGHSA enrichment
  24. 2026-07-13 22:31 UTCEPSS rescore
  25. 2026-07-13 12:51 UTCGHSA enrichment
Show 20 more
  1. 2026-07-13 06:13 UTCEPSS rescore
  2. 2026-07-13 06:13 UTCEPSS rescore
  3. 2026-07-13 01:31 UTCGHSA enrichment
  4. 2026-07-12 14:12 UTCGHSA enrichment
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-12 02:53 UTCGHSA enrichment
  7. 2026-07-11 15:34 UTCGHSA enrichment
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-11 04:15 UTCGHSA enrichment
  11. 2026-07-10 16:56 UTCGHSA enrichment
  12. 2026-07-10 05:37 UTCGHSA enrichment
  13. 2026-07-09 18:16 UTCGHSA enrichment
  14. 2026-07-09 15:00 UTCNVD updateCVSS v3 → 7.8
  15. 2026-07-09 06:55 UTCGHSA enrichment
  16. 2026-07-08 19:36 UTCGHSA enrichment
  17. 2026-07-08 15:16 UTCEPSS rescore
  18. 2026-07-08 15:16 UTCEPSS rescore
  19. 2026-07-08 08:17 UTCEG score recompute
  20. 2026-07-08 08:16 UTCMITRE cvelistV5first tracked

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCParadoxis/CVE-2026-57239
    First seen Jul 8, 2026

    Proof of concept exploit for CVE-2026-3775/CVE-2026-3780 and CVE-2026-57239 which lets you obtain NT AUTHORITY\SYSTEM rights via the Foxit PDF Reader updater service.

    Open source ↗

Frequently asked(5)

What is CVE-2026-57239?
CVE-2026-57239 is a high vulnerability published on July 8, 2026. The user-controllable executable files will be directly executed by high-privilege processes, allowing low-privilege users to have the opportunity to elevate their privileges to NT AUTHORITY\SYSTEM.
When was CVE-2026-57239 disclosed?
CVE-2026-57239 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57239 actively exploited?
CVE-2026-57239 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-57239?
CVE-2026-57239 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.2.
How do I remediate CVE-2026-57239?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57239, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-57239

Explore →

Is Your Infrastructure Affected by CVE-2026-57239?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.