CVE-2026-96658

CRITICALPre-NVD 9.99.9—
EchelonGraph scoreHIGH confidence

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-01. A secondary CVSS source baseline 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in Foreman. An authenticated attacker with low-level permissions can achieve remote code execution (RCE) by bypassing the safemode sandbox within the templating engine. Due to improper handling of delegated methods, an attacker can append unauthorized functions to the allowed execution list, enabling them to run arbitrary commands on the hosting server.

CVSS v3
9.9
EG Score
9.9CRITICALhigh confidence
EG Risk
45
EG Risk 45/100CISA SSVC

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
Severity99% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 1, 2026

Last Modified

October 2, 2026

Advisory Details (6)

Auto-updated Oct 2, 2026
Patch available. Sources: redhat.
redhat Patch Available

2534185 – (CVE-2026-96658) CVE-2026-96658 foreman: Safemode Bypass leading to RCE

https://bugzilla.redhat.com/show_bug.cgi?id=2534185
redhat Patch Available

CVE-2026-96658 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-96658
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:74506
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:74505
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:74504
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:74503

Vendor Advisories for CVE-2026-96658(5)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrubygem-safemode-0:1.5.0-2.el9sat2026-10-01redhat
redhatforeman-0:3.18.0.14-1.el9sat2026-10-01redhat
redhatyggdrasil-worker-forwarder-0:0.1.0-2.1.el9sat2026-10-01redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 50× in last 7d / 50× 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-10-04 08:04 UTCVendor advisory
  2. 2026-10-04 08:04 UTCGHSA enrichment
  3. 2026-10-04 03:46 UTCVendor advisory
  4. 2026-10-04 03:46 UTCGHSA enrichment
  5. 2026-10-03 23:29 UTCVendor advisory
  6. 2026-10-03 23:29 UTCGHSA enrichment
  7. 2026-10-03 19:12 UTCVendor advisory
  8. 2026-10-03 19:12 UTCGHSA enrichment
  9. 2026-10-03 14:55 UTCEG score recompute
  10. 2026-10-03 14:55 UTCVendor advisory
  11. 2026-10-03 14:55 UTCGHSA enrichment
  12. 2026-10-03 14:26 UTCEPSS rescore
  13. 2026-10-03 10:39 UTCVendor advisory
  14. 2026-10-03 10:39 UTCGHSA enrichment
  15. 2026-10-03 06:20 UTCVendor advisory
  16. 2026-10-03 06:20 UTCGHSA enrichment
  17. 2026-10-03 02:03 UTCVendor advisory
  18. 2026-10-03 02:03 UTCGHSA enrichment
  19. 2026-10-02 21:46 UTCEG score recompute
  20. 2026-10-02 21:46 UTCVendor advisory
  21. 2026-10-02 21:46 UTCGHSA enrichment
  22. 2026-10-02 17:57 UTCEPSS rescore
  23. 2026-10-02 17:29 UTCEG score recompute
  24. 2026-10-02 17:29 UTCVendor advisory
  25. 2026-10-02 17:29 UTCGHSA enrichment
Show 25 more
  1. 2026-10-02 17:00 UTCEG score recompute
  2. 2026-10-02 17:00 UTCVendor advisory
  3. 2026-10-02 17:00 UTCGHSA enrichment
  4. 2026-10-02 13:12 UTCVendor advisory
  5. 2026-10-02 13:11 UTCGHSA enrichment
  6. 2026-10-02 08:52 UTCVendor advisory
  7. 2026-10-02 08:51 UTCGHSA enrichment
  8. 2026-10-02 04:32 UTCEG score recompute
  9. 2026-10-02 04:32 UTCVendor advisory
  10. 2026-10-02 04:31 UTCGHSA enrichment
  11. 2026-10-02 04:04 UTCEG score recompute
  12. 2026-10-02 04:04 UTCVendor advisory
  13. 2026-10-02 04:03 UTCGHSA enrichment
  14. 2026-10-02 00:25 UTCEG score recompute
  15. 2026-10-02 00:25 UTCVendor advisory
  16. 2026-10-02 00:25 UTCGHSA enrichment
  17. 2026-10-01 23:37 UTCEG score recompute
  18. 2026-10-01 23:37 UTCGHSA enrichment
  19. 2026-10-01 20:41 UTCEG score recompute
  20. 2026-10-01 20:40 UTCGHSA enrichment
  21. 2026-10-01 18:30 UTCEG score recompute
  22. 2026-10-01 17:47 UTCEG score recompute
  23. 2026-10-01 17:27 UTCEG score recompute
  24. 2026-10-01 16:27 UTCEG score recompute
  25. 2026-10-01 16:25 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-96658?
CVE-2026-96658 is a critical vulnerability published on October 1, 2026. A flaw was found in Foreman. An authenticated attacker with low-level permissions can achieve remote code execution (RCE) by bypassing the safemode sandbox within the templating engine. Due to improper handling of delegated methods, an attacker can append unauthorized functions to the allowed…
When was CVE-2026-96658 disclosed?
CVE-2026-96658 was first published on October 1, 2026, with the most recent update on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-96658 actively exploited?
CVE-2026-96658 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-96658?
CVE-2026-96658 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-96658?
A fix for CVE-2026-96658 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-96658 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-96658?

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

Book a Demo →Browse All CVEs