Skip to content
Fencer Intel
high 7.5

CVE-2018-18264 in the critical feed json

Kubernetes Dashboard before 1.10.1 allows attackers to bypass authentication and use Dashboard's Service Account for reading secrets within…

published 7y ago modified 4mo ago also EUVD-2018-9999

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
70.4%
EPSS 70.4% chance of exploitation in 30 days, percentile 99.3%
public exploits
0
none known, plus a Nuclei check

Summary

Kubernetes Dashboard before 1.10.1 allows attackers to bypass authentication and use Dashboard's Service Account for reading secrets within the cluster.

Patch / fix

  • kubernetes dashboard 1.10.1

Is CVE-2018-18264 in your stack? 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-2018-18264 updated cvss 6.5

dashboard: Authentication bypass resulting in information exposure

  • Red Hat Storage 3 heketi, heketi-client, python-heketi
    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

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

Exploits and checks

  • Nuclei template Kubernetes Dashboard <1.10.1 - Authentication Bypass nuclei detection template
  • sysdig.com https://sysdig.com/blog/privilege-escalation-kubernetes-dashboard/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-306 Missing Authentication for Critical Functionality

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.