Skip to content
Fencer Vulns
critical 9.8

CVE-2017-1000056 in the critical feed json

Kubernetes Privilege Escalation

published 2017-07-13 9 y ago modified 2026-06-17 4 mo ago also GHSA-2jx2-76rc-2v7v , GO-2023-1492 , EUVD-2021-0902

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.8%
EPSS 2.8% chance of exploitation in 30 days, percentile 86%
public exploits
0
none known

Summary

Kubernetes version 1.5.0-1.5.4 is vulnerable to a privilege escalation in the PodSecurityPolicy admission plugin resulting in the ability to make use of any existing PodSecurityPolicy object.

Patch / fix

  • go k8s.io/kubernetes 1.5.5
  • kubernetes Debian 14, Debian 13, Debian 12 1.5.5+dfsg-1

debian advisories DEBIAN-CVE-2017-1000056

  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250807T150727-1.1

opensuse advisories openSUSE-SU-2025:15424-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-1000056 updated cvss 7.5

kubernetes: Privilege escalation in the PodSecurityPolicy admission plugin

  • Red Hat Enterprise Linux 7 kubernetes
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Enterprise 3 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +13 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.84% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go k8s.io/kubernetes
>=1.5.0, <1.5.5
1.5.5

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.