Cyber Resilience

CVE-2025-4232

Paloaltonetworks Globalprotect 6.0.0 – 6.2.8

Published
13 June 2025
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v4 8.5
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/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:N/R:U/V:D/RE:M/U:Amber
EPSS Score 0.0042 35th percentile
Risk Priority 33 floored blend · peak EPSS

Summary

CVE-2025-4232 is a high-severity Improper Neutralization of Wildcards or Matching Symbols (CWE-155) vulnerability in Paloaltonetworks Globalprotect. Its CVSS base score is 8.5 (High).

Operationally, ranked at the 35th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

An improper neutralization of wildcards vulnerability in the log collection feature of Palo Alto Networks GlobalProtect™ app on macOS allows a non administrative user to escalate their privileges to root.

CWE(s)
CWE-155

Related Threats

CVEs Like This One

CVE-2026-0250Same product: Paloaltonetworks Globalprotect
CVE-2025-0135Same product: Paloaltonetworks Globalprotect
CVE-2026-0251Same product: Paloaltonetworks Globalprotect
CVE-2025-4227Same product: Paloaltonetworks Globalprotect
CVE-2024-5921Same product: Paloaltonetworks Globalprotect
CVE-2023-0009Same product: Paloaltonetworks Globalprotect
CVE-2025-0118Same product: Paloaltonetworks Globalprotect
CVE-2026-0249Same product: Paloaltonetworks Globalprotect
CVE-2025-0120Same product: Paloaltonetworks Globalprotect
CVE-2024-5908Same product: Paloaltonetworks Globalprotect

Affected Assets

paloaltonetworks
globalprotect
6.0.0 — 6.2.8 · 6.3.0 — 6.3.3

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation partial match

Input validation directly requires checking and sanitizing special elements such as wildcards before they are passed downstream.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization to block wildcard injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect wildcard issues but does not itself implement neutralization controls.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and sanitization that directly prevents wildcard injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements include rules for neutralizing special characters before downstream processing.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles encourage safe handling of untrusted input but do not prescribe specific wildcard neutralization.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require proper escaping or neutralization of wildcard and matching symbols.

References