How severe is CVE-2023-2431?

CVE-2023-2431 has a CVSS score of 3.4/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-2431?

CVE-2023-2431 affects the following packages: k8s.io/kubernetes (Go), k8s.io/kubernetes (Go), k8s.io/kubernetes (Go), k8s.io/kubernetes (Go). Ecosystems affected: Go.

How do I fix CVE-2023-2431?

Update k8s.io/kubernetes to 1.24.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-2431 is resolved across your whole dependency graph.

How do I detect CVE-2023-2431 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for k8s.io/kubernetes, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-2431 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2023-2431 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-2431 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-2431?

CVE-2023-2431 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-2431?

CVE-2023-2431 is classified as CWE-1287 (CWE-1287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2023-2431 published, and has it been updated?

CVE-2023-2431 was published on June 16, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

LOW severity

CVE-2023-2431 — kubernetes

LOWFix: kubernetes/kubernetes#117020

CVE-2023-2431 is a low-severity (CVSS 3.4) CWE-1287 vulnerability in k8s.io/kubernetes. A fix is available for k8s.io/kubernetes — see the affected versions and patch details below.

Bypass of seccomp profile enforcement

Also known asGHSA-xc8m-28vv-4pjcGO-2023-1864

Published

Jun 16, 2023

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-2431.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐹k8s.io/kubernetes🐹k8s.io/kubernetes🐹k8s.io/kubernetes🐹k8s.io/kubernetes

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`k8s.io/kubernetes`	all versions	1.24.14`go get k8s.io/kubernetes@v1.24.14`
🐹Go	`k8s.io/kubernetes`	≥ 1.25.0&&< 1.25.10	1.25.10`go get k8s.io/kubernetes@v1.25.10`
🐹Go	`k8s.io/kubernetes`	≥ 1.26.0&&< 1.26.5	1.26.5`go get k8s.io/kubernetes@v1.26.5`
🐹Go	`k8s.io/kubernetes`	≥ 1.27.0&&< 1.27.2	1.27.2`go get k8s.io/kubernetes@v1.27.2`

Affected Products

2 products · 5 configurations

fedorafedoraproject

1 version

Application

kuberneteskubernetes

≥ 1.27.0 && < 1.27.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for k8s.io/kubernetes, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update k8s.io/kubernetes to 1.24.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-2431 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

Product	Fixed in	Advisory
Red Hat OpenShift Container Platform 4.13	`openshift4-wincw/windows-machine-config-rhel9-operator:8.1.0-24`	RHSA-2023:6156

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2023-2431 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

3.4/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N

CWE Classification

CWE-1287CWE-1287

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

kubernetes

7.6/10

Code-Review10/10

Maintained10/10

Branch-ProtectionN/A

Assessed Oct 19, 2026

Timeline

Disclosed

Jun 16, 2023

Last updated

Oct 28, 2026

Identifiers

CVE-2023-2431

GHSA-xc8m-28vv-4pjc

GO-2023-1864

References

Advisorygithub.com · CVE 2023 2431.json Advisorynvd.nist.gov · CVE 2023 2431 Reportgithub.com Webgithub.com · kubernetes Webgroups.google.com · QHmx0HOQa10 Weblists.fedoraproject.org · 43HDSKBKPSW53OW647B5ETHRWFFNHSRQ Weblists.fedoraproject.org · XBX4RL4UOC7JHWWYB2AJCKSUM7EG5Y5G Webgithub.com Webgithub.com Webgithub.com Webgithub.com Webgithub.com Weblists.fedoraproject.org · 43HDSKBKPSW53OW647B5ETHRWFFNHSRQ Weblists.fedoraproject.org · XBX4RL4UOC7JHWWYB2AJCKSUM7EG5Y5G Webpkg.go.dev · GO 2023 1864 Packagegithub.com · kubernetes

Related vulnerabilities

This CVE is low severity; 8 of 8 other CVEs affecting kubernetes are rated as high or higher (top: high).

CVE-2025-13281CVE-2025-5187CVE-2025-4563CVE-2025-1767CVE-2024-9042CVE-2025-0426CVE-2024-10220CVE-2024-0793

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026