CVE-2026-96658

CRITICALPre-NVD 8.89.9
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-90921 (ENISA EUVD) · GHSA-g2wg-rx2f-4j5r (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in Foreman. This vulnerability allows an authenticated remote attacker with low-level read permissions to achieve arbitrary code execution on the underlying server. By manipulating the permitted methods list within the template rendering engine, an attacker can bypass the safemode sandbox isolation and execute unauthorized commands directly on the host system.

CVSS v3
8.8
EG Score
9.9CRITICALmedium confidence
EG Risk
45
EG Risk 45/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
54th
KEV
Not listed

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.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.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 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). 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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (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

Published

October 1, 2026

Last Modified

October 18, 2026

Advisory Details (7)

Auto-updated Oct 16, 2026
Patch available. Sources: redhat.
Web page

oss-security - CVE-2026-96658: Foreman: Safemode bypass leading to RCE (fixed in 3.19.2, 5.0.1)

http://www.openwall.com/lists/oss-security/2026/10/07/2
Red HatMentions a patch (unverified)

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

https://bugzilla.redhat.com/show_bug.cgi?id=2534185
Red HatMentions a patch (unverified)

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
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:74506
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:74505
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:74504
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:74503

Patch Availability(3)

Vendor / EcosystemFix (by version range) / 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 25× in last 7d / 210× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 246 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 146 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  2. 2026-11-01 13:47 UTCEG score recompute
  3. 2026-11-01 13:47 UTCVendor advisory
  4. 2026-11-01 13:47 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  5. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  6. 2026-10-31 11:54 UTCEG score recompute
  7. 2026-10-31 11:54 UTCVendor advisory
  8. 2026-10-31 11:54 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  9. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  10. 2026-10-30 10:01 UTCEG score recompute
  11. 2026-10-30 10:01 UTCVendor advisory
  12. 2026-10-30 10:00 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  13. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  14. 2026-10-29 08:08 UTCEG score recompute
  15. 2026-10-29 08:08 UTCVendor advisory
  16. 2026-10-29 08:07 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  17. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  18. 2026-10-28 06:12 UTCEG score recompute
  19. 2026-10-28 06:12 UTCVendor advisory
  20. 2026-10-28 06:12 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  21. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  22. 2026-10-27 04:19 UTCEG score recompute
  23. 2026-10-27 04:19 UTCVendor advisory
  24. 2026-10-27 04:18 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  25. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
Show 75 more
  1. 2026-10-25 22:01 UTCEG score recompute
  2. 2026-10-25 22:01 UTCVendor advisory
  3. 2026-10-25 22:00 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  4. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  5. 2026-10-25 13:48 UTCEG score recompute
  6. 2026-10-24 20:06 UTCEG score recompute
  7. 2026-10-24 20:06 UTCVendor advisory
  8. 2026-10-24 20:06 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  9. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  10. 2026-10-23 18:12 UTCEG score recompute
  11. 2026-10-23 18:12 UTCVendor advisory
  12. 2026-10-23 18:11 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  13. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-10-22 16:15 UTCEG score recompute
  16. 2026-10-22 16:15 UTCVendor advisory
  17. 2026-10-22 16:15 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  18. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  19. 2026-10-21 14:08 UTCEG score recompute
  20. 2026-10-21 14:08 UTCVendor advisory
  21. 2026-10-21 14:08 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  22. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  23. 2026-10-20 12:16 UTCEG score recompute
  24. 2026-10-20 12:16 UTCVendor advisory
  25. 2026-10-20 12:15 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  26. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  27. 2026-10-19 10:20 UTCEG score recompute
  28. 2026-10-19 10:20 UTCVendor advisory
  29. 2026-10-19 10:20 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  30. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  31. 2026-10-18 07:27 UTCEG score recompute
  32. 2026-10-18 07:27 UTCVendor advisory
  33. 2026-10-18 07:27 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  34. 2026-10-18 06:45 UTCEG score recompute
  35. 2026-10-18 06:45 UTCVendor advisory
  36. 2026-10-18 06:45 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  37. 2026-10-18 06:44 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  38. 2026-10-18 02:57 UTCEG score recompute
  39. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  40. 2026-10-17 15:41 UTCEG score recompute
  41. 2026-10-17 15:41 UTCVendor advisory
  42. 2026-10-17 15:41 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  43. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  44. 2026-10-16 13:46 UTCVendor advisory
  45. 2026-10-16 13:46 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  46. 2026-10-16 07:33 UTCEG score recompute
  47. 2026-10-16 07:33 UTCVendor advisory
  48. 2026-10-16 07:33 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  49. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  50. 2026-10-15 05:38 UTCEG score recompute
  51. 2026-10-15 05:38 UTCVendor advisory
  52. 2026-10-15 05:38 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  53. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  54. 2026-10-14 01:17 UTCEG score recompute
  55. 2026-10-14 01:17 UTCVendor advisory
  56. 2026-10-14 01:17 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  57. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  58. 2026-10-12 21:30 UTCEG score recompute
  59. 2026-10-12 21:30 UTCVendor advisory
  60. 2026-10-12 21:30 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  61. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  62. 2026-10-12 14:40 UTCEG score recompute
  63. 2026-10-12 01:24 UTCVendor advisory
  64. 2026-10-12 01:24 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  65. 2026-10-11 21:07 UTCVendor advisory
  66. 2026-10-11 21:07 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  67. 2026-10-11 19:11 UTCEG score recompute
  68. 2026-10-11 16:50 UTCVendor advisory
  69. 2026-10-11 16:50 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9
  70. 2026-10-11 16:27 UTCEG score recompute
  71. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  72. 2026-10-11 13:39 UTCEG score recompute
  73. 2026-10-11 12:33 UTCEG score recompute
  74. 2026-10-11 12:33 UTCVendor advisory
  75. 2026-10-11 12:32 UTCGHSA enrichmentGHSA-g2wg-rx2f-4j5r · GitHub severity CRITICAL · GitHub CVSS 9.9

Frequently asked(5)

What is CVE-2026-96658?
CVE-2026-96658 is a critical-severity vulnerability; its CVE record was published on October 1, 2026. A flaw was found in Foreman. This vulnerability allows an authenticated remote attacker with low-level read permissions to achieve arbitrary code execution on the underlying server. By manipulating the permitted methods list within the template rendering engine, an attacker can bypass the safemode…
When was CVE-2026-96658 made public?
CVE-2026-96658 was made public on October 1, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on October 1, 2026. EchelonGraph's copy of the record carries a last-modified date of October 18, 2026; the record at its source may have been updated since.
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 (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-96658?
CVE-2026-96658 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending). EchelonGraph synthesises a secondary CVSS source + FIRST EPSS + GHSA into a combined EG score of 9.9 (CRITICAL).
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.