Privilege escalation to cluster-admin on the Rancher local cluster through Fleet's agent management controller
Severity and exploitation
KEV coverage does not rule out exploitation.
Assessment vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HSeverity
critical9.1CVSS measures technical severity, not the likelihood of an attack.
Known exploitation
Not listed in the checked CISA KEV catalog
Absence from CISA KEV does not rule out attacks.
Public exploit
Not established by this record
Missing evidence does not mean no public exploit exists.
Remediation
Fix status not established
No structured fix or guidance is available here. Check the latest publisher advisory.
What this means
SUSE Rancher Fleet versions 0.13.0 to 0.13.17, 0.14.0 to 0.14.12, 0.15.0 to 0.15.8, and 0.16.0 to 0.16.3 have a privilege escalation weakness. An ordinary user may be able to associate a Fleet cluster with administrative credentials, causing elevated privileges.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Attack conditions
No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.
Review supporting sources →Affected versions
Check the exact model, release, and any platform requirements against your installation.
SUSE · suse
Rancher
4 ranges
SUSE · suse
Rancher
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0.16.0 → before 0.16.3
semver versions
0.15.0 → before 0.15.8
semver versions
0.14.0 → before 0.14.12
semver versions
0.13.0 → before 0.13.17
semver versions
Other versions: unaffected
What to do
Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.
No structured fix or remediation guidance is available here. Check the full source description and vendor’s latest advisory for a patch or workaround; do not assume another version is safe.
cve.new guidance unless attributed to a publisher. This page does not inspect your installation.
Public exploit evidence
No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.
Original source description
Read the full publisher description
SUSE Rancher Fleet clusters reference a kubeconfig secret that the controller uses to install and manage a Fleet agent on the target cluster. The controller did not sufficiently restrict which kubeconfig secrets a Fleet Cluster object was allowed to reference. As a result, a Fleet cluster defined in a namespace an ordinary user controls could be associated with administrative credentials for the management cluster itself, causing the controller to manage the management cluster on that user's behalf and to run that user's Fleet content there with elevated privileges. This affects SUSE Rancher Fleet 0.16.0 up to 0.16.3, 0.15.0 up to 0.15.8, 0.14.0 up to 0.14.12, 0.13.0 up to 0.13.17 and possible older versions.
References
1 sourcesInside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-94290View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Environment requirements
These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.
suse · platform conditions
Any condition may hold
Any condition may hold
Vulnerable product
cpe:2.3:a:suse:rancher:*:*:*:*:*:*:*:*From (inclusive): 0.16.0
Before: 0.16.3
Vulnerable product
cpe:2.3:a:suse:rancher:*:*:*:*:*:*:*:*From (inclusive): 0.15.0
Before: 0.15.8
Vulnerable product
cpe:2.3:a:suse:rancher:*:*:*:*:*:*:*:*From (inclusive): 0.14.0
Before: 0.14.12
Vulnerable product
cpe:2.3:a:suse:rancher:*:*:*:*:*:*:*:*From (inclusive): 0.13.0
Before: 0.13.17
Applicability preview
[
{
"operator": "OR",
"nodes": [
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:a:suse:rancher:*:*:*:*:*:*:*:*",
"versionStartIncluding": "0.16.0",
"versionEndExcluding": "0.16.3"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:a:suse:rancher:*:*:*:*:*:*:*:*",
"versionStartIncluding": "0.15.0",
"versionEndExcluding": "0.15.8"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:a:suse:rancher:*:*:*:*:*:*:*:*",
"versionStartIncluding": "0.14.0",
"versionEndExcluding": "0.14.12"
},
{
"vulnerable": true,
"criteria": "cpe:2.3:a:suse:rancher:*:*:*:*:*:*:*:*",
"versionStartIncluding": "0.13.0",
"versionEndExcluding": "0.13.17"
}
]
}
]
}
]Contributing organizations · 2
Assigning organization
Additional data publisher
Timeline
All times UTCAdvisory published
Publication date supplied by the source.
Source updated
Latest modification date supplied by the source.
Last imported by cve.new
Latest catalog import, not the date we first saw this advisory.
What changed
Follow changes- CVE · CVE-2026-94290
Observed 2026-11-03T05:13:03.421Z · upstream updated 2026-11-03T04:55:52.658Z
Prioritization updated
before
[ { "source": "CISA-ADP", "type": "SSVC", "role": "CISA Coordinator", "timestamp": "2026-11-02T16:13:30.631420Z", "decisions": [ { "name": "Exploitation", "value": "none" }, { "name": "Automatable", "value": "no" }, { "name": "Technical Impact", "value": "total" } ] } ]after
[ { "source": "CISA-ADP", "type": "SSVC", "role": "CISA Coordinator", "timestamp": "2026-11-02T00:00:00+00:00", "decisions": [ { "name": "Exploitation", "value": "none" }, { "name": "Automatable", "value": "no" }, { "name": "Technical Impact", "value": "total" } ] } ] - CVE · CVE-2026-94290
Observed 2026-11-02T16:22:07.271Z · upstream updated 2026-11-02T16:13:40.826Z
Prioritization updated
before
[]
after
[ { "source": "CISA-ADP", "type": "SSVC", "role": "CISA Coordinator", "timestamp": "2026-11-02T16:13:30.631420Z", "decisions": [ { "name": "Exploitation", "value": "none" }, { "name": "Automatable", "value": "no" }, { "name": "Technical Impact", "value": "total" } ] } ]
Large field values are marked as truncated previews. Original source snapshots remain retained.
Showing up to 50 most recent observed changes.