CVE-2024-5042

MEDIUMPre-NVD 6.66.6—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in the Submariner project. Due to unnecessary role-based access control permissions, a privileged attacker can run a malicious container on a node that may allow them to steal service account tokens and further compromise other nodes and potentially the entire cluster.

CVSS v3
6.6
EG Score
6.6MEDIUMmedium confidence
EG Risk
30
EG Risk 30/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
Severity66% × 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.5%
EPSS %ILE
41st
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

May 17, 2024

Last Modified

September 17, 2026

Advisory Details (5)

Auto-updated Jul 18, 2026
Patch available. Sources: redhat, github.
githubMentions a patch (unverified)

Submariner Operator sets unnecessary RBAC permissions · CVE-2024-5042 · GitHub Advisory Database · GitHub

https://github.com/advisories/GHSA-2rhx-qhxp-5jpw
redhatMentions a patch (unverified)

2280921 – (CVE-2024-5042) CVE-2024-5042 submariner-operator: RBAC permissions can allow for the spread of node compromises

https://bugzilla.redhat.com/show_bug.cgi?id=2280921
redhatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2024-5042
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2024:4591
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:6503

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatodf4/rook-ceph-rhel9-operator:17745421012026-04-02redhat
redhatodf4/odf-multicluster-rhel9-operator:v4.16.0-192024-07-17redhat

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.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/submariner-io/submariner-operator—
  • 0.16.0-m0 up to 0.16.4: fixed in 0.16.4
  • 0.17.0-m0 up to 0.17.2: fixed in 0.17.2
  • every version up to 0.15.4: fixed in 0.15.4
  • 0.18.0-m0 up to 0.18.0-rc0: fixed in 0.18.0-rc0
  • every version up to 0.16.4: fixed in 0.16.4
  • 0.17.0 on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 35× 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.

Showing the most recent 100 of 221 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2024-5042?
CVE-2024-5042 is a medium vulnerability published on May 17, 2024. A flaw was found in the Submariner project. Due to unnecessary role-based access control permissions, a privileged attacker can run a malicious container on a node that may allow them to steal service account tokens and further compromise other nodes and potentially the entire cluster.
When was CVE-2024-5042 disclosed?
CVE-2024-5042 was first published on May 17, 2024, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-5042 actively exploited?
CVE-2024-5042 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-5042?
CVE-2024-5042 has a CVSS base score of 6.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2024-5042?
A fix for CVE-2024-5042 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-5042 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-5042

Explore →

Is Your Infrastructure Affected by CVE-2024-5042?

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