# CVE-2026-8804: Cleartext Storage of Sensitive Information for Puppet Resource API

> Attackers with local access can read sensitive parameters like passwords stored in cleartext in the Puppet agent's transaction state cache.

- **Severity:** Medium 6.7 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-8804, GHSA-rh7m-r3xm-v5xg, UBUNTU-CVE-2026-8804

## What is CVE-2026-8804?

CVE-2026-8804 is a medium-severity vulnerability in Perforce Puppet Core, published on 3 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Puppet resource_api (shipped in Puppet Core 8.x and Puppet Enterprise 2023.8.x and 2025.x) does not preserve the sensitive flag on parameters defined via the resource-api, causing values such as passwords to be stored in cleartext in the agent's local transaction state cache. Affected versions of the resource_api module include all versions between 1.5.0 - 1.9.1 and 2.0.0 The issue was fixed in puppet resource_api 1.9.2 and 2.0.1 released with Puppet Core 8.20.0 and PE 2023.8.10 & PE 2025.11.0.

Weakness: CWE-313 (Cleartext Storage in a File or on Disk), CWE-312 (Cleartext Storage of Sensitive Information)

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


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

Upgrade to a fixed version.

## Is CVE-2026-8804 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8804 is a medium-severity vulnerability in Perforce Puppet Core, published on 3 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-8804 in the wild and no public exploit code.

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

## Sources

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

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