# CVE-2026-22061: CVE-2026-22061 Debug Log Information Disclosure Vulnerability in Trident

> An authenticated attacker with debug log access can view sensitive LUKS passphrases or SMB credentials in NetApp Trident.

- **Severity:** High 8.2 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 12 Oct 2026
- **Also known as:** GHSA-h9gv-qj3w-x5ff

## What is CVE-2026-22061?

CVE-2026-22061 is a high-severity vulnerability in NetApp Trident, published on 9 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Trident versions v25.02.1 through v26.06.1 are susceptible to a vulnerability that could allow an authenticated attacker with access to debug logs to view LUKS passphrases or SMB Active Directory credentials.

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

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


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

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

## Is CVE-2026-22061 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22061 is a high-severity vulnerability in NetApp Trident, published on 9 Oct 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-22061 in the wild and no public exploit code.

Affected product: NetApp Trident. 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-22061/ (Markdown: https://insights.sbomify.com/CVE-2026-22061/index.md)
```

## Sources

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

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