Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2023-3676: A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able

65
This week
HIGH 8.8WATCHLISTUPGRADE

CVE-2023-3676 is a high-severity flaw (CVSS 8.8) affecting kubernetes. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if they include Windows nodes.

Why this priority

  • High severity
  • EPSS top 4%: very likely to be exploited
  • Public exploit reference
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance13.2% (top 4%)
CISA exploited listNo
WeaknessCWE-20
Published2023-10-31
Last modified2026-06-17
Publisher (CNA): Kubernetes · Vendor: kubernetes

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

kubernetes kubernetes UPGRADE
Affected: < 1.24.17 · >= 1.25.0 and < 1.25.13 · >= 1.26.0 and < 1.26.8 · >= 1.27.0 and < 1.27.5 · >= 1.28.0 and < 1.28.1
Fixed in: 1.24.17, 1.25.13, 1.26.8, 1.27.5, 1.28.1
Safe to downgrade to: a release before 1.25.0
1. Check installed version
apt-cache policy kubernetes || rpm -q kubernetes || kubernetes --version
2. UPGRADE to 1.24.17 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade kubernetes
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade kubernetes
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.25.0 (Debian / Ubuntu)
apt-cache madison kubernetes sudo apt install kubernetes=<VERSION_BEFORE_1.25.0> sudo apt-mark hold kubernetes
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list kubernetes sudo dnf downgrade kubernetes-<VERSION_BEFORE_1.25.0> sudo dnf versionlock add kubernetes
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-3676?

kubernetes: upgrade to 1.24.17, 1.25.13, 1.26.8, 1.27.5, 1.28.1. Exact commands for each OS are on this page.

Is CVE-2023-3676 being exploited?

CVE-2023-3676 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-3676 affect?

CVE-2023-3676 affects kubernetes. Severity is high (CVSS 8.8). A security issue was discovered in Kubernetes where a user that can create pods on Windows nodes may be able to escalate to admin privileges on those nodes. Kubernetes clusters are only affected if they include Windows nodes.

How urgent is CVE-2023-3676?

Priority 65/100. High severity; EPSS top 4%: very likely to be exploited; Public exploit reference; On your watchlist

Software pages

Kubernetes vulnerabilities · Windows vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.