PAN-SA-2025-0009 Chromium: Monthly Vulnerability Update (May 2025)
Exploit Maturity
UNREPORTED
Response Effort
LOW
Recovery
USER
Value Density
DIFFUSE
Attack Vector
NETWORK
Attack Complexity
LOW
Attack Requirements
NONE
Automatable
NO
User Interaction
ACTIVE
Product Confidentiality
HIGH
Product Integrity
HIGH
Product Availability
HIGH
Privileges Required
NONE
Subsequent Confidentiality
HIGH
Subsequent Integrity
HIGH
Subsequent Availability
HIGH
Description
Palo Alto Networks incorporated the following Chromium security fixes into our products:
| CVE | Summary |
|---|---|
| CVE-2025-3066 | Use after free in Site Isolation |
| CVE-2025-3067 | Inappropriate implementation in Custom Tabs |
| CVE-2025-3068 | Inappropriate implementation in Intents |
| CVE-2025-3069 | Inappropriate implementation in Extensions |
| CVE-2025-3070 | Insufficient validation of untrusted input in Extensions |
| CVE-2025-3071 | Inappropriate implementation in Navigations |
| CVE-2025-3072 | Inappropriate implementation in Custom Tabs |
| CVE-2025-3073 | Inappropriate implementation in Autofill |
| CVE-2025-3074 | Inappropriate implementation in Downloads |
| CVE-2025-3619 | Heap buffer overflow in Codecs |
| CVE-2025-3620 | Use after free in USB |
| CVE-2025-4050 | Out of bounds memory access in DevTools |
| CVE-2025-4051 | Insufficient data validation in DevTools |
| CVE-2025-4052 | Inappropriate implementation in DevTools |
| CVE-2025-4096 | Heap buffer overflow in HTML |
| CVE-2025-4372 | Use after free in WebAudio |
Product Status
| Versions | Affected | Unaffected |
|---|---|---|
| Prisma Access Browser | < 135.16.8.96 | >= 136.11.9.93 |
Required Configuration for Exposure
No special configuration is required to be affected by this issue.
Severity: HIGH, Suggested Urgency: MODERATE
CVSS-BT: 7.6 / CVSS-B: 9.4 (CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:U/AU:N/R:U/V:D/RE:L/U:Amber)
Exploitation Status
Palo Alto Networks is not aware of any malicious exploitation of this issue.
Solution
| CVE | Prisma Access Browser |
|---|---|
| CVE-2025-3066 | 135.16.8.96 |
| CVE-2025-3067 | 135.16.8.96 |
| CVE-2025-3068 | 135.16.8.96 |
| CVE-2025-3069 | 135.16.8.96 |
| CVE-2025-3070 | 135.16.8.96 |
| CVE-2025-3071 | 135.16.8.96 |
| CVE-2025-3072 | 135.16.8.96 |
| CVE-2025-3073 | 135.16.8.96 |
| CVE-2025-3074 | 135.16.8.96 |
| CVE-2025-3619 | 135.16.8.96 |
| CVE-2025-3620 | 135.16.8.96 |
| CVE-2025-4050 | 136.11.9.93 |
| CVE-2025-4051 | 136.11.9.93 |
| CVE-2025-4052 | 136.11.9.93 |
| CVE-2025-4096 | 136.11.9.93 |
| CVE-2025-4372 | 136.11.9.93 |
Workarounds and Mitigations
No workaround or mitigation is available.
Timeline
Initial publication