Skip to main content
CVE-2025-10360VulnerabilityPublished

CVE-2025-10360: Perforce Puppet Enterprise · Insufficiently Protected Credentials

Affects Perforce Puppet EnterpriseSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium · fixed in 2025.6 : update Perforce Puppet Enterprise when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2025.6
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Perforce Puppet EnterpriseAffected
  • =2025.4
Fixed in–

AI-suggested

1. Immediate Upgrade: Organizations should prioritize upgrading Puppet Enterprise to version 2025.6 or later, which removes the encryption key from backup files. 2. Backup File Access Controls: Restrict access to Puppet backup files to only trusted administrators and secure backup storage locations with strong access controls and encryption at rest. 3. Audit and Monitor: Implement auditing and monitoring of backup file access and privilege escalations to detect any unauthorized attempts to access sensitive backup data. 4. Rotate API Keys: Rotate the AI provider API keys used by the Infra Assistant feature to invalidate any potentially exposed credentials. 5. Follow Vendor Remediation: For organizations unable to upgrade immediately, carefully follow the remediation steps provided in the 2025.6 release notes to mitigate exposure risk. 6. Harden Privileged Access: Enforce strict privilege management and use just-in-time access controls to minimize the risk of privileged account compromise. 7. Backup Encryption: Ensure backups are encrypted independently of Puppet’s internal encryption mechanisms to add an additional layer of protection. 8. Incident Response Preparedness: Prepare incident response plans to address potential credential compromise scenarios involving AI provider accounts.

Description

In Puppet Enterprise versions 2025.4.0 and 2025.5, the encryption key used for encrypting content in the Infra Assistant database was not excluded from the files gathered by Puppet backup. The key is only present on the system if the user has a Puppet Enterprise Advanced license and has enabled the Infra Assistant feature. The key is used for encrypting one particular bit of data in the Infra Assistant database: the API key for their AI provider account. This has been fixed in Puppet Enterprise version 2025.6, and release notes for 2025.6 have remediation steps for users of affected versions who can't update to the latest version.

References

Community reviews

Loading reviews…