CVE-2026-44940: SUSE Observability rancher-extension-stackstate · Cleartext Storage of Sensitive Information
Affects SUSE Observability rancher-extension-stackstateSource CVE Database V5
Not known to be exploited · CVSS 5.7 Medium : upgrade the SUSE Observability rancher-extension-stackstate package to 2.14.2 or 2.13.6 when convenient.
Data as of 1 Nov 2026, 08:20 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.14.2, 2.13.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.
What to do
Upgrade the SUSE Observability rancher-extension-stackstate package and stackvista/rancher-extension-stackstate to 2.14.2 or 2.13.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SUSE Observabilityrancher-extension-stackstate | Affected
| Fixed in
|
| SUSE Observabilityrancher-extension-stackstate | Affected
| Fixed in
|
GitHubstackvista/rancher-extension-stackstatepkg:github/stackvista/rancher-extension-stackstateOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
In the meantime, restrict access to configuration files and sensitive locations where tokens are stored to trusted users only to reduce risk.
Description
The rancher-extension-stackstate extension in SUSE Observability exposes service tokens in plain configuration or insecure locations rather than managing them securely. An attacker with minimal access could obtain the token to gain unauthorized access or escalate privileges within the observability environment.