# CVE-2025-10360: Insufficiently Protected Credentials in Puppet Enterprise 2025.4 and 2025.5

> Attackers can read the AI provider API key from backup files if the Infra Assistant feature is enabled, compromising external AI services.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2025
- **Updated:** 24 Sep 2025
- **Also known as:** GHSA-wjvp-gg74-m678

## What is CVE-2025-10360?

CVE-2025-10360 is a medium-severity vulnerability in Perforce Puppet Enterprise, published on 24 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2025-10360?


## How do I fix CVE-2025-10360?

No fix has been published for CVE-2025-10360 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-10360 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10360 and fix it if it is affected.

What it is: CVE-2025-10360 is a medium-severity vulnerability in Perforce Puppet Enterprise, published on 24 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10360 in the wild and no public exploit code.

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

## Sources

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

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