Perforce Puppet Core/Puppet Enterprise up to 8.10.0/8.19.0/8.19.x cleartext storage in file
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.2 | $0-$5k | 0.77+ |
Summary
A vulnerability, which was classified as problematic, has been found in Perforce Puppet Core and Puppet Enterprise up to 8.10.0/8.19.0/8.19.x. The impacted element is an unknown function. The manipulation leads to cleartext storage in file. This vulnerability is uniquely identified as CVE-2026-8804. Local access is required to approach this attack. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Perforce Puppet Core and Puppet Enterprise up to 8.10.0/8.19.0/8.19.x and classified as problematic. This issue affects an unknown functionality. The manipulation with an unknown input leads to a cleartext storage in file vulnerability. Using CWE to declare the problem leads to CWE-313. The product stores sensitive information in cleartext in a file, or on disk. Impacted is confidentiality. The summary by CVE is:
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.
The advisory is shared at portal.perforce.com. The identification of this vulnerability is CVE-2026-8804 since 05/18/2026. The exploitation is known to be easy. An attack has to be approached locally. Additional levels of successful authentication are required for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1555 for this issue.
Upgrading to version 8.20.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 2.3VulDB Meta Temp Score: 2.2
VulDB Base Score: 2.3
VulDB Temp Score: 2.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Cleartext storage in fileCWE: CWE-313 / CWE-312 / CWE-310
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Puppet Core/Puppet Enterprise 8.20.0
Timeline
05/18/2026 CVE reserved07/03/2026 Advisory disclosed
07/03/2026 VulDB entry created
07/03/2026 VulDB entry last update
Sources
Advisory: portal.perforce.comStatus: Confirmed
CVE: CVE-2026-8804 (🔒)
GCVE (CVE): GCVE-0-2026-8804
GCVE (VulDB): GCVE-100-376097
Entry
Created: 07/03/2026 15:34Changes: 07/03/2026 15:34 (66)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.