CVE Tools

Prisma Access Browser

22 CVEs tracked. 1 of them are in CISA KEV.

This hub aggregates every CVE we track for Prisma Access Browser, a product in the security products space. Use it to gauge the current risk picture and drill into individual advisories.

Prisma Access Browser CVEs per month

Oct 2024 to Sep 2026. Point at a month, or focus the strip and use the arrow keys.
Prisma Access Browser CVEs per month
MonthCVEs
2024-100
2024-110
2024-120
2025-010
2025-026
2025-0314
2025-041
2025-050
2025-061
2025-070
2025-080
2025-090
2025-100
2025-110
2025-120
2026-010
2026-020
2026-030
2026-040
2026-050
2026-060
2026-070
2026-080
2026-090

Severity

How the 22 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.

  • Critical15%
  • High1673%
  • Medium523%

Latest CVEs

The 15 most recently published vulnerabilities affecting Prisma Access Browser.

  1. CVE-2025-4233Prisma Access Browser: Inappropriate implementation in Cache8.8
  2. CVE-2025-0129Prisma Access Browser: Inappropriate control behavior in Prisma Access Browser9.8
  3. CVE-2025-2783Incorrect handle provided in unspecified circumstances in Mojo in Google Chrome on Windows prior to 134.0.6998.177 allowed a remote attacker to perform a sandbox escape via a malicious file. (Chrom...8.3
  4. CVE-2025-2476Use after free in Lens in Google Chrome prior to 134.0.6998.117 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)8.8
  5. CVE-2025-2137Out of bounds read in V8 in Google Chrome prior to 134.0.6998.88 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: Medium)8.8
  6. CVE-2025-2136Use after free in Inspector in Google Chrome prior to 134.0.6998.88 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)8.8
  7. CVE-2025-1920Type Confusion in V8 in Google Chrome prior to 134.0.6998.88 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)8.8
  8. CVE-2025-1923Inappropriate implementation in Permission Prompts in Google Chrome prior to 134.0.6998.35 allowed an attacker who convinced a user to install a malicious extension to perform UI spoofing via a cra...4.3
  9. CVE-2025-1922Inappropriate implementation in Selection in Google Chrome on Android prior to 134.0.6998.35 allowed a remote attacker who convinced a user to engage in specific UI gestures to perform UI spoofing ...4.3
  10. CVE-2025-1921Inappropriate implementation in Media Stream in Google Chrome prior to 134.0.6998.35 allowed a remote attacker to obtain information about a peripheral via a crafted HTML page. (Chromium security s...6.5
  11. CVE-2025-1916Use after free in Profiles in Google Chrome prior to 134.0.6998.35 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a crafted HTM...8.8
  12. CVE-2025-1917Inappropriate implementation in Browser UI in Google Chrome on Android prior to 134.0.6998.35 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: ...4.3
  13. CVE-2025-1919Out of bounds read in Media in Google Chrome prior to 134.0.6998.35 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page. (Chromium security severity...8.8
  14. CVE-2025-1918Out of bounds read in PDFium in Google Chrome prior to 134.0.6998.35 allowed a remote attacker to potentially perform out of bounds memory access via a crafted PDF file. (Chromium security severity...8.8
  15. CVE-2025-1914Out of bounds read in V8 in Google Chrome prior to 134.0.6998.35 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)8.8

Product grouping is registry-driven, with AI assist and human review. How it works

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store