CVE-2023-0118

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 1.4% (72nd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.0 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2023-09-20) is not newer than that change (2024-11-21), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2023-12208 (ENISA EUVD) · GHSA-pwc8-3cc6-gg8v (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
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: 1.4%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An arbitrary code execution flaw was found in Foreman. This flaw allows an admin user to bypass safe mode in templates and execute arbitrary code on the underlying operating system.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
42
EG Risk 42/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.4% × 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
1.4%
EPSS %ILE
72nd
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.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). 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

September 20, 2023

Last Modified

November 21, 2024

Advisory Details (6)

Auto-updated Jul 18, 2026
Patch available. Sources: redhat.
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2023:6818
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2023:5980
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2023:5979
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2023:4466
Red HatMentions a patch (unverified)

2159291 – (CVE-2023-0118) CVE-2023-0118 Foreman: Arbitrary code execution through templates

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

cve-details

https://access.redhat.com/security/cve/CVE-2023-0118

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatforeman-0:3.7.0.9-1.el8sat2023-11-08redhat
redhatforeman-0:3.1.1.27-1.el8sat2023-10-20redhat
redhatrubygem-safemode-0:1.3.8-1.el8sat2023-10-20redhat

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.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 25× in last 7d / 68× 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 229 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 129 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2023-0118?
CVE-2023-0118 is a critical-severity vulnerability; its CVE record was published on September 20, 2023. An arbitrary code execution flaw was found in Foreman. This flaw allows an admin user to bypass safe mode in templates and execute arbitrary code on the underlying operating system.
When was CVE-2023-0118 made public?
CVE-2023-0118 was made public on March 12, 2023: 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 September 20, 2023. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-0118 actively exploited?
CVE-2023-0118 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (72nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-0118?
CVE-2023-0118 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2023-0118?
A fix for CVE-2023-0118 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-0118 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-0118

Explore →

Is Your Infrastructure Affected by CVE-2023-0118?

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