Skip to content
Fencer Vulns
high 8.1

CVE-2019-6287 json

Rancher Project Members Have Continued Access to Namespaces After Being Removed From Them

published 2019-04-10 7 y ago modified 2026-06-17 4 mo ago also GHSA-6r7x-4q7g-h83j , GO-2024-2764 , EUVD-2022-2856

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

Summary

In Rancher 2.0.0 through 2.1.5, project members have continued access to create, update, read, and delete namespaces in a project after they have been removed from it.

Patch / fix

  • go github.com/rancher/rancher 2.1.6, 2.1.6+incompatible

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
go github.com/rancher/rancher
>=2.0.0, <2.1.6
>=2.0.0+incompatible, <2.1.6+incompatible
2.1.6
2.1.6+incompatible

Classification

Weakness
  • CWE-269 Improper Privilege Management

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.