Skip to content
Fencer Intel
low 3.1

CVE-2015-7561 json

Kubernetes in OpenShift3 Access Control Misconfiguration

published 9y ago modified last mo. also GHSA-2h9c-34v6-3qmr , GO-2023-1985 , EUVD-2022-1990

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

Summary

Kubernetes in OpenShift3 allows remote authenticated users to use the private images of other users should they know the name of said image.

Patch / fix

  • go k8s.io/kubernetes 1.2.0-alpha.6
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250807T150727-1.1

opensuse advisories openSUSE-SU-2025:15424-1

Is CVE-2015-7561 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2015-7561 updated cvss 3.5

OpenShift3: Private Docker images can be used by any user, once they are pulled to a node

  • Red Hat OpenShift Enterprise 3 openshift, openshift-node, openshift-master, openshift-clients, openshift-sdn-ovs, tuned-profiles-openshift-node
    affected: no fix available

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

1.42% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
go k8s.io/kubernetes
<1.2.0-alpha.6
1.2.0-alpha.6

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
Technology feeds

References

Sources

Fencer Intel 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.