CVE-2026-123039

CRITICALPre-NVD 7.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than the CVSS score beside it.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-11-13), indicating real-world exploitation has been confirmed by US federal agencies. A secondary CVSS source baseline 7.8 retained for reference (NVD's own analysis pending). The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 7.8 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — KEV-added in the last 14 daysExploited in the wild

Also known asEUVD-2026-124481 (ENISA EUVD) · GHSA-m95q-vgfj-2v8g (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 1.3%CVSS: 7.8Exploit: No code on recordExposed services: Not assessed

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

The Gaia OS DynamicCLI daemon runs as root and listens on a world-writable local socket (/tmp/dynamic_socket) without authenticating connecting processes. An authenticated local user can send a command to the socket and have it executed as root.

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
1.3%
EPSS %ILE
70th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 7.8 HIGH.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-13). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: this CVE is in CISA's KEV catalog, and CISA's required action for it, quoted below, applies whether or not a fix is released.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: this CVE is in CISA's KEV catalog, and CISA's required action for it, quoted below, applies whether or not a fix is released.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://support.checkpoint.com/results/sk/sk1000362 · https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk · https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk · https://nvd.nist.gov/vuln/detail/CVE-2026-123039

Published

November 12, 2026

Last Modified

November 13, 2026

References (2)

Vendor Advisories for CVE-2026-123039(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 12× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 20:29 UTCEchelonGraph re-scored
  2. 2026-11-13 20:29 UTCGHSA enrichmentGHSA-m95q-vgfj-2v8g · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-11-13 19:21 UTCEchelonGraph re-scored
  4. 2026-11-13 19:21 UTCGHSA enrichmentGHSA-m95q-vgfj-2v8g · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-11-13 18:44 UTCEchelonGraph re-scored
  6. 2026-11-13 18:44 UTCGHSA enrichmentGHSA-m95q-vgfj-2v8g · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-11-13 18:02 UTCGHSA enrichmentGHSA-m95q-vgfj-2v8g · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-11-13 17:58 UTCEchelonGraph re-scored▲ 1.20
  9. 2026-11-13 17:58 UTCCISA KEV update
  10. 2026-11-13 17:29 UTCEchelonGraph re-scored
  11. 2026-11-13 17:29 UTCGHSA enrichmentGHSA-m95q-vgfj-2v8g · GitHub severity HIGH · GitHub CVSS 7.8
  12. 2026-11-13 16:50 UTCEPSS rescoreEPSS 1.3% · 70th percentile
  13. 2026-11-13 16:37 UTCEchelonGraph re-scored
  14. 2026-11-13 16:37 UTCGHSA enrichmentGHSA-m95q-vgfj-2v8g · GitHub severity HIGH · GitHub CVSS 7.8
  15. 2026-11-12 20:08 UTCGHSA enrichmentGHSA-m95q-vgfj-2v8g · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-11-12 15:47 UTCEchelonGraph re-scored
  17. 2026-11-12 15:47 UTCGHSA enrichmentGHSA-m95q-vgfj-2v8g · GitHub severity HIGH · GitHub CVSS 7.8
  18. 2026-11-12 15:01 UTCENISA EUVD ID recordedEUVD-2026-124481 · Source: ENISA EUVD
  19. 2026-11-12 14:17 UTCEchelonGraph re-scoredFirst assessed: 7.8 HIGH
  20. 2026-11-12 14:16 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2026-123039?
CVE-2026-123039 is a critical-severity vulnerability; its CVE record was published on November 12, 2026. The Gaia OS DynamicCLI daemon runs as root and listens on a world-writable local socket (/tmp/dynamic_socket) without authenticating connecting processes. An authenticated local user can send a command to the socket and have it executed as root.
When was the CVE record for CVE-2026-123039 published?
The CVE record for CVE-2026-123039 was published on November 12, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 13, 2026; the record at its source may have been updated since.
Is CVE-2026-123039 actively exploited?
Yes. CISA added CVE-2026-123039 to the Known Exploited Vulnerabilities catalog on November 13, 2026, affecting Check Point Multiple Products. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation.
What is the CVSS score of CVE-2026-123039?
CVE-2026-123039 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending). EchelonGraph synthesises a secondary CVSS source + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2026-123039?
CVE-2026-123039 affects Check Point Multiple Products.
How do I remediate CVE-2026-123039?
No fix for CVE-2026-123039 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-123039 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-123039?

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

Book a Demo →Browse All CVEs