Puppet Core
Approved changes feed: RSS · Atom
cpe:2.3:a:perforce:puppet_core:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Perforce (b6773f0f-3a72-52f1-9555-ff325a988421) |
|---|---|
| Product | Puppet Core (603a13e0-97b7-5e3f-9632-6286c0c3b4bb) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-8804 |
vulnerable | 2026-07-29 01:09:06.285312 |
Cleartext Storage of Sensitive Information for Puppet Resource API
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.
Published: 2026-07-03T07:40:15.684Z
Updated: 2026-07-06T15:21:55.981Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.