PoC Monitor
← All CVEs
CVE-2025-4609published 22 Aug 2025 21:05 UTCData: JSON · API

Google Chrome

Incorrect handle provided in unspecified circumstances in Mojo in Google Chrome on Windows prior to 136.0.7103.113 allowed a remote attacker to potentially perform a sandbox escape via a malicious file. (Chromium security severity: High)

First public PoC 1.2 yearsafter publication · 9 Nov 2026
Public PoCs44 on GitHub
CVSS9.6critical · scored by CISA ADP · CWE-732
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Google Chrome
  • >= 136.0.7103.113, < 136.0.7103.113

Fixed in 136.0.7103.113

Mitigation

Upgrade Chrome to 136.0.7103.113 or later.

Timeline

Days relative to CVE publication
t=0+60+120+180+240+300+360+420CVE published22 Aug 2025 · t = 0First public PoC9 Nov 2026 · t+1.2y

First public PoC 1.2 years after publication; not in CISA KEV. First PoC: nek-3231/cve-2025-4609-mojo-poc (created 9 Nov 2026, found by us: 14 Nov 2026).

PoC repositories

Found on GitHub.

4 PoCs

PoCs 4
RepositoryCreatedFound by usStarsAssessment
nek-3231/cve-2025-4609-mojo-poc 9 Nov 2026 +1.2 y 14 Nov 2026 0 PoC
santiagovillalobos6900-commits/cve-2025-4609-mojo-poc 12 Nov 2026 +1.2 y 14 Nov 2026 0 PoC
vobando0077/cve-2025-4609-mojo-poc 12 Nov 2026 +1.2 y 14 Nov 2026 0 PoC
vobando007/cve-2025-4609-mojo-poc 12 Nov 2026 +1.2 y 14 Nov 2026 0 PoC

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.

PoC characteristics

What to hunt for in your logs · from 4 PoC repos

Regex

Generated from PoC characteristics; not yet reviewed. Matches the request path and query.

GET /mojo_157.html
(?i)^/mojo_157\.html(?:[?#].*)?$
GET /poc.html
(?i)^/poc\.html(?:[?#].*)?$

Suricata

Template generated from PoC characteristics. Review before deploying.

GET /mojo_157.html
alert http any any -> $HOME_NET [8000] (msg:"GG PoC-Monitor CVE-2025-4609 Google Chrome exploit attempt"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/mojo_157.html"; reference:url,poc.griffinguard.io/cve/CVE-2025-4609; classtype:web-application-attack; sid:9346686; rev:1;)
GET /poc.html
alert http any any -> $HOME_NET [8000] (msg:"GG PoC-Monitor CVE-2025-4609 Google Chrome exploit attempt"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/poc.html"; reference:url,poc.griffinguard.io/cve/CVE-2025-4609; classtype:web-application-attack; sid:9697245; rev:1;)

Sigma

Template generated from PoC characteristics. Review before deploying.

GET /mojo_157.html
title: Google Chrome exploit attempt (CVE-2025-4609)
id: gg-pocmon-cve-2025-4609-9346686
status: experimental
description: Request pattern taken from public PoCs for CVE-2025-4609. Generated, not reviewed.
references:
  - https://poc.griffinguard.io/cve/CVE-2025-4609
logsource:
  category: webserver
detection:
  selection:
    cs-method: GET
    cs-uri-stem|contains|all:
      - '/mojo_157.html'
  condition: selection
falsepositives:
  - Authorized vulnerability scanning
level: critical
tags:
  - attack.initial_access
  - attack.t1190
  - cve.2025.4609
GET /poc.html
title: Google Chrome exploit attempt (CVE-2025-4609)
id: gg-pocmon-cve-2025-4609-9697245
status: experimental
description: Request pattern taken from public PoCs for CVE-2025-4609. Generated, not reviewed.
references:
  - https://poc.griffinguard.io/cve/CVE-2025-4609
logsource:
  category: webserver
detection:
  selection:
    cs-method: GET
    cs-uri-stem|contains|all:
      - '/poc.html'
  condition: selection
falsepositives:
  - Authorized vulnerability scanning
level: critical
tags:
  - attack.initial_access
  - attack.t1190
  - cve.2025.4609