dbcve.org
CWE-312Weakness · CWE-312

CVE-2026-8804

MEDIUM · 6.7 CVSS v4.0 Published 2026-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Puppet resource_api module fails to preserve the 'sensitive' flag on parameters defined via the resource-api, causing sensitive values like passwords to be stored in cleartext in the agent's local transaction state cache instead of being masked.

MitigationUpgrade puppet resource_api to version 1.9.2 or 2.0.1 (included in Puppet Core 8.20.0, PE 2023.8.10, or PE 2025.11.0) to restore sensitive parameter protection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify resource_api module version
    Run 'puppet module list' or check the modulepath for the resource_api gem version (e.g., in /opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/resource_api-*.gemspec)
    Affected if Version is lower than 1.9.2 or 2.0.1, or the module is present with no version visible (implying an older release)
  2. Confirm use of sensitive parameters
    Review your Puppet code for resources that use the 'sensitive' type wrapper (e.g., Sensitive($password) or type => Sensitive) on parameters defined via resource_api
    Affected if Your manifests or modules define sensitive-type parameters using the resource_api framework
  3. Locate the agent transaction state cache
    On the Puppet agent, locate the transaction store file (typically at /opt/puppetlabs/puppet/cache/state/transactionstore.yaml or within the $statedir configured in puppet.conf)
    Affected if The agent runs against a master or applies catalogs locally and stores transaction state
  4. Inspect cached data for unmasked values
    Read the transactionstore.yaml file (use 'cat' or a YAML parser) and search for parameter names you marked as sensitive; verify whether their values appear as plain text strings or as Ruby objects tagged as Sensitive
    Affected if Sensitive parameter values appear as plaintext strings rather than masked (e.g., not showing as 'REDACTED' or wrapped in a Sensitive wrapper)

You are affected if the resource_api module version is below 1.9.2 or 2.0.1 AND you use sensitive-type parameters in resources managed through resource_api, AND the transaction state cache contains unmasked plaintext values for those parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade puppet resource_api to version 1.9.2 or 2.0.1 (included in Puppet Core 8.20.0, PE 2023.8.10, or PE 2025.11.0) to restore sensitive parameter protection.

Recommended fix High confidence

Puppet Core 8.20.0 or later (includes resource_api 1.9.2); Puppet Enterprise 2023.8.10 or 2025.11.0 or later (includes resource_api 1.9.2/2.0.1)

  1. Upgrade Puppet Core to version 8.20.0 or later to get resource_api 1.9.2
  2. Alternatively, upgrade Puppet Enterprise to version 2023.8.10 or 2025.11.0 or later which include the fixed resource_api versions
  3. Verify the upgrade by checking the resource_api gem version: gem list puppet resource_api
  4. After upgrade, confirm sensitive parameters are no longer stored in cleartext in the agent's local transaction state cache

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8804 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8804 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data