dbcve.org
Trust Protection FoundationApplication · Paloaltonetworks

CVE-2026-0240

HIGH · 8.7 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 24.1.13 / 24.3.6 or later.
See remediation →
89/100
Remediation priority · High
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
An information disclosure vulnerability in Trust Protection Foundation enables an authenticated attacker to obtain sensitive information from the server's vault. Successful exploitation of this issue allows the attacker to impersonate any user within the environment and arbitrarily modify configuration settings.

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 · moderate confidence

An information disclosure vulnerability in Trust Protection Foundation allows authenticated attackers to retrieve sensitive data from the server's vault, enabling user impersonation across the environment and arbitrary modification of configuration settings.

MitigationApply vendor-provided patches for Trust Protection Foundation; review and rotate compromised credentials; audit user access logs and vault contents for signs of unauthorized access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Trust Protection FoundationApplication
Affected:>= 24.1.0, < 24.1.13>= 24.3.0, < 24.3.6>= 25.1.0, < 25.1.8>= 25.3.0, < 25.3.3

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

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. Identify Trust Protection Foundation version
    Run 'ProductVersion' or check the Trust Protection Foundation administrative console for the installed version number. Typically found in Help > About or via PowerShell commandlet if available.
    Affected if The installed version falls within 24.1.0 to 24.1.12, 24.3.0 to 24.3.5, 25.1.0 to 25.1.7, or 25.3.0 to 25.3.2.
  2. Verify authentication is required for vault access
    Review the Trust Protection Foundation authentication settings in the admin console under Security or Authentication settings. Check whether local authentication, LDAP, or SAML is properly enforced for vault operations.
    Affected if Authentication is configured but the vault permits authenticated users to access sensitive data beyond their assigned permissions.
  3. Check vault access control policies
    Inspect the vault access control list (ACL) or policy settings in the Trust Protection Foundation console. Look for entries that grant broad access to vault secrets or sensitive objects.
    Affected if Vault policies allow authenticated users to extract sensitive vault data or impersonate other users.

You are affected if your Trust Protection Foundation version is within the listed ranges AND authentication is enabled, allowing unauthorized vault data extraction and user impersonation.

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
Upgrade available Upgrade to 24.1.13 / 24.3.6 / 25.1.8 or later
Fixed in 24.1.1324.3.625.1.8
Interim mitigation

Apply vendor-provided patches for Trust Protection Foundation; review and rotate compromised credentials; audit user access logs and vault contents for signs of unauthorized access.

Recommended fix High confidence

Upgrade to 25.3.3 (or latest available release in your supported major version line)

  1. 1. Verify current Trust Protection Foundation version by checking the system information or running the version command
  2. 2. Review the release notes for versions 24.1.13, 24.3.6, 25.1.8, and 25.3.3 to understand changes and any prerequisites
  3. 3. Schedule a maintenance window for the upgrade
  4. 4. Back up the current configuration and vault data
  5. 5. Download the appropriate installer for the target version from the Palo Alto Networks support portal
  6. 6. Run the installer following the standard upgrade procedure for Trust Protection Foundation
  7. 7. After upgrade, verify the system is operational and the vulnerability is resolved
  8. 8. Confirm that the Trust Protection Foundation version matches the fixed release
Caveat Review release notes for any configuration or behavioral changes between your current version and the target fixed version; test in non-production environment first

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

Fix this in Trust Protection Foundation Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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