dbcve.org
Cortex XsiamApplication · Paloaltonetworks

CVE-2026-0234

CRITICAL · 9.1 CVSS v3.1 Published 2026-04-13
Fix available
A fix is available. Upgrade to 1.5.52 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 improper verification of cryptographic signature vulnerability exists in Cortex XSOAR and Cortex XSIAM platforms during integration of Microsoft Teams that enables an unauthenticated user to access and modify protected resources.

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

This vulnerability in Cortex XSOAR and Cortex XSIAM platforms allows unauthenticated users to access and modify protected resources due to improper verification of cryptographic signatures during Microsoft Teams integration. An attacker could exploit this flaw to bypass authentication and tamper with data or functionality within the affected platforms.

MitigationApply vendor-supplied patches or updates for Cortex XSOAR and Cortex XSIAM that address the cryptographic signature verification flaw in the Microsoft Teams integration. Until patched, disable the Microsoft Teams integration if possible and monitor for 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
Cortex XsiamApplication
Affected:>= 1.5.0, < 1.5.52
Cortex XsoarApplication
Affected:>= 1.5.0, < 1.5.52

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 installed Cortex product and version
    Access the platform settings or about page. In Cortex XSOAR, go to Settings > About. In Cortex XSIAM, go to Settings > Configurations > About. Record the exact version number displayed.
    Affected if The version shown is >= 1.5.0 and < 1.5.52 for either Cortex XSOAR or Cortex XSIAM.
  2. Verify Microsoft Teams integration status
    Navigate to Settings > Integrations > Microsoft Teams (or search for 'Teams' in the integrations list). Check if the integration instance exists and shows as 'Enabled' or 'Connected'.
    Affected if A Microsoft Teams integration instance is enabled and configured in the platform.
  3. Inspect Microsoft Teams integration configuration
    Open the Microsoft Teams integration settings. Review the configured parameters including incoming webhook URLs, authentication settings, and any custom bot configurations.
    Affected if The integration uses custom or non-default webhook configurations, or shows signs of modification.
  4. Review integration audit logs for Teams activity
    Go to Settings > Audit or Logs > Audit. Filter for events involving Microsoft Teams integration, particularly authentication events or configuration changes.
    Affected if There are unexpected authentication attempts, unauthorized configuration changes, or unusual Teams-related events from unexpected sources.

You are affected if your Cortex XSOAR or XSIAM version is between 1.5.0 and 1.5.52 inclusive and you have the Microsoft Teams integration enabled.

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 1.5.52 or later
Fixed in 1.5.52
Interim mitigation

Apply vendor-supplied patches or updates for Cortex XSOAR and Cortex XSIAM that address the cryptographic signature verification flaw in the Microsoft Teams integration. Until patched, disable the Microsoft Teams integration if possible and monitor for unauthorized access.

Recommended fix High confidence

Cortex XSOAR/XSIAM version 1.5.52 or later

  1. 1. Identify current Cortex XSOAR or Cortex XSIAM version by checking the system settings or using the CLI command `pan-python` or admin console
  2. 2. Verify if Microsoft Teams integration is deployed by reviewing installed content packs and integrations
  3. 3. Plan for upgrade to version 1.5.52 or later - review Palo Alto Networks upgrade documentation for prerequisites
  4. 4. Perform a backup of current configuration and content
  5. 5. Execute the upgrade to version 1.5.52 or later following standard Palo Alto Networks upgrade procedures
  6. 6. After upgrade, verify the Microsoft Teams integration is functioning correctly
  7. 7. Confirm the system is running the fixed version by checking the version number in the admin console

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

Fix this in Cortex Xsiam Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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