CVE-2023-2431

LOWNVD 3.43.4—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.4 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 99% of all CVEs by exploit prediction. 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, nvd
Elevated
3.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.4Exploit: NoneExposed: 0

A fix is available — apply it.

A security issue was discovered in Kubelet that allows pods to bypass the seccomp profile enforcement. Pods that use localhost type for seccomp profile but specify an empty profile field, are affected by this issue. In this scenario, this vulnerability allows the pod to run in unconfined (seccomp disabled) mode. This bug affects Kubelet.

CVSS v3
3.4
EG Score
3.4(medium)
EPSS
17.0%
KEV
Not listed

Published

June 16, 2023

Last Modified

December 12, 2024

References (9)

Vendor Advisories for CVE-2023-2431(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift4-wincw/windows-machine-config-rhel9-operator:8.1.0-242023-10-30redhat

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 rangeFixed inDependents
k8s.io/kubernetes—1.27.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 45× 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-07-11 08:25 UTCEPSS rescore
  2. 2026-07-11 08:25 UTCEPSS rescore
  3. 2026-07-09 19:08 UTCEPSS rescore
  4. 2026-07-09 19:08 UTCEPSS rescore
  5. 2026-07-08 15:13 UTCEPSS rescore
  6. 2026-07-07 13:44 UTCEPSS rescore
  7. 2026-07-06 16:26 UTCEPSS rescore
  8. 2026-07-06 16:26 UTCEPSS rescore
  9. 2026-07-05 02:28 UTCEPSS rescore
  10. 2026-07-04 06:29 UTCEPSS rescore
  11. 2026-07-02 16:59 UTCEPSS rescore
  12. 2026-07-01 15:04 UTCEPSS rescore
  13. 2026-06-30 23:21 UTCEPSS rescore
  14. 2026-06-30 23:21 UTCEPSS rescore
  15. 2026-06-29 14:05 UTCEPSS rescore
  16. 2026-06-28 14:06 UTCEPSS rescore
  17. 2026-06-28 14:06 UTCEPSS rescore
  18. 2026-06-28 04:54 UTCEPSS rescore
  19. 2026-06-27 18:04 UTCOSV refresh
  20. 2026-06-27 03:07 UTCEPSS rescore
  21. 2026-06-25 13:48 UTCEPSS rescore
  22. 2026-06-25 13:48 UTCEPSS rescore
  23. 2026-06-24 14:03 UTCEPSS rescore
  24. 2026-06-24 14:03 UTCEPSS rescore
  25. 2026-06-23 21:31 UTCEPSS rescore
Show 49 more
  1. 2026-06-23 21:31 UTCEPSS rescore
  2. 2026-06-22 14:24 UTCEPSS rescore
  3. 2026-06-22 14:24 UTCEPSS rescore
  4. 2026-06-21 14:55 UTCEPSS rescore
  5. 2026-06-21 14:55 UTCEPSS rescore
  6. 2026-06-21 01:58 UTCEPSS rescore
  7. 2026-06-21 01:58 UTCEPSS rescore
  8. 2026-06-19 19:24 UTCEPSS rescore
  9. 2026-06-19 19:24 UTCEPSS rescore
  10. 2026-06-18 17:51 UTCEPSS rescore
  11. 2026-06-18 17:51 UTCEPSS rescore
  12. 2026-06-17 17:51 UTCEPSS rescore
  13. 2026-06-17 17:51 UTCEPSS rescore
  14. 2026-06-16 17:51 UTCEPSS rescore
  15. 2026-06-16 17:51 UTCEPSS rescore
  16. 2026-06-15 17:47 UTCEPSS rescore
  17. 2026-06-14 23:16 UTCEPSS rescore
  18. 2026-06-13 22:59 UTCEPSS rescore
  19. 2026-06-13 22:59 UTCEPSS rescore
  20. 2026-06-12 23:10 UTCEPSS rescore
  21. 2026-06-11 13:59 UTCEPSS rescore
  22. 2026-06-10 22:17 UTCEPSS rescore
  23. 2026-06-10 13:21 UTCEPSS rescore
  24. 2026-06-10 13:21 UTCEPSS rescore
  25. 2026-06-10 05:17 UTCOSV refresh
  26. 2026-06-08 14:15 UTCEPSS rescore
  27. 2026-06-08 14:15 UTCEPSS rescore
  28. 2026-06-07 15:23 UTCEPSS rescore
  29. 2026-06-07 15:23 UTCEPSS rescore
  30. 2026-06-05 22:46 UTCEPSS rescore
  31. 2026-06-05 22:46 UTCEPSS rescore
  32. 2026-06-04 13:11 UTCEPSS rescore
  33. 2026-06-04 13:11 UTCEPSS rescore
  34. 2026-06-02 20:12 UTCEPSS rescore
  35. 2026-06-02 20:12 UTCEPSS rescore
  36. 2026-06-02 20:12 UTCEPSS rescore
  37. 2026-06-01 13:51 UTCEPSS rescore
  38. 2026-05-29 13:43 UTCEPSS rescore
  39. 2026-05-28 13:43 UTCEPSS rescore
  40. 2026-05-28 13:43 UTCEPSS rescore
  41. 2026-05-27 13:39 UTCEPSS rescore
  42. 2026-05-27 13:39 UTCEPSS rescore
  43. 2026-05-26 13:43 UTCEPSS rescore
  44. 2026-05-26 13:43 UTCEPSS rescore
  45. 2026-05-26 07:18 UTCEPSS rescore
  46. 2026-05-26 07:18 UTCEPSS rescore
  47. 2026-05-26 07:17 UTCEPSS rescore
  48. 2026-05-24 23:19 UTCEG score recompute
  49. 2026-05-24 23:19 UTCVendor advisory

Frequently asked(5)

What is CVE-2023-2431?
CVE-2023-2431 is a low vulnerability published on June 16, 2023. A security issue was discovered in Kubelet that allows pods to bypass the seccomp profile enforcement. Pods that use localhost type for seccomp profile but specify an empty profile field, are affected by this issue. In this scenario, this vulnerability allows the pod to run in unconfined (seccomp…
When was CVE-2023-2431 disclosed?
CVE-2023-2431 was first published in the National Vulnerability Database on June 16, 2023, with the most recent update on December 12, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-2431 actively exploited?
CVE-2023-2431 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-2431?
CVE-2023-2431 has a CVSS v3 base score of 3.4 (NVD).
How do I remediate CVE-2023-2431?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-2431, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-2431

Explore →

Is Your Infrastructure Affected by CVE-2023-2431?

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

Start Free Scan →Browse All CVEs