dbcve.org
Insufficiently Protected CredentialsWeakness · CWE-522

CVE-2025-10360

MEDIUM · 6.9 CVSS v4.0 Published 2025-09-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
Remotely reachable Zero-click

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

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

In Puppet Enterprise 2025.4.0 and 2025.5, the encryption key used to protect AI provider API keys in the Infra Assistant database was not excluded from files gathered during Puppet backup operations. This key is only present on systems with a Puppet Enterprise Advanced license that have enabled the Infra Assistant feature. The exposed key could allow decryption of the stored AI provider API credentials.

MitigationUpgrade to Puppet Enterprise 2025.6 or later. Users unable to upgrade should consult the 2025.6 release notes for remediation steps, which likely include rotating the exposed encryption key and reviewing backup configurations.

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
Network
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

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/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. Verify Puppet Enterprise version
    Run `puppet --version` or check the PE installer version to confirm whether you are running 2025.4.0 or 2025.5.
    Affected if Version is 2025.4.0 or 2025.5 (any earlier or later version is not affected)
  2. Confirm Advanced license is active
    Check the license type via the Puppet Enterprise console under License settings or by running `puppet enterprise support` command if available.
    Affected if The system has a Puppet Enterprise Advanced license (Standard license holders are not affected)
  3. Determine if Infra Assistant is enabled
    Check the Infra Assistant configuration in the Puppet Enterprise console or examine if the Infra Assistant service/database is provisioned on the system.
    Affected if Infra Assistant feature is enabled and operational
  4. Inspect recent backup archives
    Locate and examine backup files created by Puppet backup operations. Search within those archives for the Infra Assistant database file or any file containing an encryption key used for the Infra Assistant.
    Affected if Backup archives contain the Infra Assistant database or its encryption key (files that should have been excluded but were not)
  5. Review AI provider API credentials
    If backups have been performed and Infra Assistant was enabled, verify whether AI provider API keys were stored in the Infra Assistant and assess if backups may have been exfiltrated or accessed by unauthorized parties.
    Affected if AI provider credentials were stored and backups containing the encryption key exist or could have been accessed

You are affected if running PE 2025.4.0 or 2025.5 with an Advanced license and Infra Assistant enabled, and backup operations captured the Infra Assistant encryption key that should have been excluded.

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 to Puppet Enterprise 2025.6 or later. Users unable to upgrade should consult the 2025.6 release notes for remediation steps, which likely include rotating the exposed encryption key and reviewing backup configurations.

Recommended fix Moderate confidence

Puppet Enterprise 2025.6

  1. Upgrade Puppet Enterprise to version 2025.6
  2. If immediate upgrade is not possible, consult the Puppet Enterprise 2025.6 release notes for specific remediation steps for affected versions
  3. If backup files containing the encryption key were created, consider rotating the Infra Assistant encryption key and updating the AI provider API key stored in the database

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10360 — 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-2025-10360 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