cve.bz

CVE-2026-0234 paloaltonetworks

7.2 highEPSS 0.2%Fix available

High (7.2) in paloaltonetworks. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

7.2 high
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/AU:N/R:U/V:D/RE:M/U:Red

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 15th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-04-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Under analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-0234 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-0234?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-0234?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-0234 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-0234

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-0234](https://cve.bz/cve/badge/CVE-2026-0234.svg)](https://cve.bz/cve/CVE-2026-0234)

HTML:

<a href="https://cve.bz/cve/CVE-2026-0234"><img src="https://cve.bz/cve/badge/CVE-2026-0234.svg" alt="CVE-2026-0234"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Palo Alto Networks Cortex XSOAR Microsoft Teams Marketplacefrom 1.5.0 before 1.5.52
Palo Alto Networks Cortex XSIAM Microsoft Teams Marketplacefrom 1.5.0 before 1.5.52

Fixed in

ProductFixed in
Palo Alto Networks Cortex XSOAR Microsoft Teams Marketplace1.5.52
Palo Alto Networks Cortex XSIAM Microsoft Teams Marketplace1.5.52

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON