# CVE-2026-44934: Exposed tokens in SUSE Rancher AI Agent logs

> Local attackers can read exposed API keys and sensitive data from logs when debug mode is enabled in SUSE Rancher AI Agent.

- **Severity:** High 7.0 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-5r2r-h824-fr5v

## What is CVE-2026-44934?

CVE-2026-44934 is a high-severity vulnerability in SUSE Rancher, published on 6 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A information disclosure when DEBUG loglevel is set in SUSE Rancher AI Agent 1.0 before 1.0.2 could leak API keys or LLM response text with potential sensitive data into logfiles, allowing local attackers to misuse respective gained data or credentials.

Weakness: CWE-215 (Insertion of Sensitive Information Into Debugging Code)

## Which versions are affected by CVE-2026-44934?


## How do I fix CVE-2026-44934?

No fix has been published for CVE-2026-44934 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44934 being exploited?

There is no known exploitation of CVE-2026-44934 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44934 and fix it if it is affected.

What it is: CVE-2026-44934 is a high-severity vulnerability in SUSE Rancher, published on 6 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44934 in the wild and no public exploit code.

Affected product: SUSE Rancher. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44934/ (Markdown: https://insights.sbomify.com/CVE-2026-44934/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44934
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44934
- OSV: https://osv.dev/vulnerability/CVE-2026-44934

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44934/
Summaries are generated and may contain mistakes; the official description above is the record.