NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

Kubernetes vulnerable to path traversalGHSA-2394-5535-8j88

MEDIUM

GHSA-2394-5535-8j88 is a medium-severity (CVSS 6.5) CWE-23 vulnerability in github.com/kubernetes/kubernetes. A fix is available for github.com/kubernetes/kubernetes — see the affected versions and patch details below.

Also known asCVE-2022-3162GO-2023-1628
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2394-5535-8j88.

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk
0.53%1.00%1.47%1.95%1.0%1.4%May 26Sep 26Nov 26

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
🐹github.com/kubernetes/kubernetes🐹github.com/kubernetes/kubernetes🐹github.com/kubernetes/kubernetes🐹github.com/kubernetes/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

Users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom resources of a different type in the same API group without authorization. Clusters are impacted by this vulnerability if all of the following are true: 1. There are 2+ CustomResourceDefinitions sharing the same API group 2. Users have cluster-wide list or watch authorization on one of those custom resources. 3. The same users are not authorized to read another custom resource in the same API group.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/kubernetes/kubernetes≥ 1.25.0&&< 1.25.41.25.4go get github.com/kubernetes/kubernetes@v1.25.4
🐹Gogithub.com/kubernetes/kubernetes≥ 1.24.0&&< 1.24.81.24.8go get github.com/kubernetes/kubernetes@v1.24.8
🐹Gogithub.com/kubernetes/kubernetes≥ 1.23.0&&< 1.23.141.23.14go get github.com/kubernetes/kubernetes@v1.23.14
🐹Gogithub.com/kubernetes/kubernetes≥ 1.22.0&&< 1.22.161.22.16go get github.com/kubernetes/kubernetes@v1.22.16

Affected Products

1 product · 4 configurations
Application
kuberneteskubernetes
≥ 1.25.0 && ≤ 1.25.3
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update github.com/kubernetes/kubernetes to 1.25.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2394-5535-8j88 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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 HatModerate
ProductFixed inAdvisory
Red Hat OpenShift Container Platform 4.12openshift-0:4.12.0-202301042257.p0.g77bec7a.assembly.stream.el8RHSA-2022:7398
Red Hat OpenShift Container Platform 4.12microshift-0:4.12.4-202302151633.p0.gb9fe8ac.assembly.4.12.4.el8RHSA-2023:0772

Frequently Asked Questions

Users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom resources of a different type in the same API group without authorization. Clusters are impacted by this vulnerability if all of the following are true: 1. There are 2+ CustomResourceDefinitions sharing the same API group 2. Users have cluster-wide list or watch authorization on one of those custom resources. 3. The same users are not authorized to read another custom resource in the same API group.
O3 Security · Impact-Aware SCA

Is GHSA-2394-5535-8j88 in your dependencies?

Find it across Go, including transitive dependencies.

Kubernetes vulnerable to path traversal (Medium 6.5)