CVE-2019-12274
No exploitation reported by the sources we read.
- Published2019-06-06
- Fixed in2.2.4+incompatible · 2.2.4 · 1.6.27
- WeaknessCWE-668 · CWE-862
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
In Rancher 1 and 2 through 2.2.3, unprivileged users (if allowed to deploy nodes) can gain admin access to the Rancher management plane because node driver options intentionally allow posting certain data to the cloud. The problem is that a user could choose to post a sensitive file such as /root/.kube/config or /var/lib/rancher/management-state/cred/kubeconfig-system.yaml.
Timeline
dates in UTC- 2019-06-0616:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-12274?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-12274?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
OSV · NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.x | ≥ 2.0.0+incompatible, < 2.2.4+incompatible | 2.2.4+incompatible | OSV |
| 2.x | ≥ 2.0.0, < 2.2.4 | 2.2.4 | OSV |
| 1.6 | < 1.6.27 | 1.6.27 | OSV |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.x | ≥ 1.0.0, ≤ 1.6.28 | no fix published | NVD |
| 2.x | ≥ 2.0.0, ≤ 2.2.3 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update rancher/rancher to 2.2.4+incompatible · 2.2.4 · 1.6.27
Advisories and patches
- forums.rancher.comRelease Notes · Vendor Advisory
- forums.rancher.comRelease Notes · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.08.8read 2026-10-23
- NVDCVSS 2.04read 2026-10-23
- NVDweakness (CWE)CWE-668, CWE-862read 2026-10-23
- FIRST EPSSEPSS score1.1 %2026-10-22
- OSVaffected packages—
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2019-06-06
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2019-12274?
Is CVE-2019-12274 actively exploited?
What is the CVSS score for CVE-2019-12274?
Running rancher/rancher? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.