# CVE-2026-92882: Redact SNMP community, SNMPv3 pass phrases, and IPMI password in host config REST API GET responses

> Authenticated users can read sensitive SNMP and IPMI credentials in clear text from REST API responses in Checkmk.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-xwvr-5xw4-qv5w

## What is CVE-2026-92882?

CVE-2026-92882 is a low-severity vulnerability in Checkmk, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Insufficiently protected credentials in the host and folder configuration endpoints of the REST API in Checkmk <2.5.0p15, <2.4.0p38, <2.3.0p51 and 2.2.0 (EOL) allows an authenticated user who may view a host's configuration to read stored SNMP community strings, SNMPv3 auth and privacy pass phrases and IPMI passwords in clear text from GET responses, although the setup GUI never displays these values.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2026-92882 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92882 is a low-severity vulnerability in Checkmk, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92882 in the wild and no public exploit code.

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

## Sources

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

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