Threats / Google / CVE-2025-2783
CVE-2025-2783
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Google Chromium Mojo vulnerability
Google Chromium Mojo contains a sandbox escape vulnerability on Windows caused by a logic error with incorrect handle provision, affecting multiple browsers including Chrome, Edge, and Opera.
Verdict
Today item — known-exploited.
A sandbox escape in Chromium Mojo allows attackers to break out of the browser sandbox through a logic error. Active exploitation in the wild increases risk for users of affected browsers, though no CVSS score is available.
CISA KEV Yes · 2025-03-274EPSS 0.08404 (verify live)5Exploit Public PoC6CVSS 8.3 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
20 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-03-27).
Probability (EPSS)
EPSS 0.08404 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.3 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H) · Affected: Google, Chromium Mojo. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1 day after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I deliver malicious content to a user's browser, triggering the Mojo logic error to escape the sandbox.
Business
User systems face direct compromise when browser isolation fails, enabling malware installation and data theft.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the sandbox escape to gain OS-level code execution on the victim's Windows machine.
Business
Enterprise endpoints lose containment; attackers pivot to internal networks and sensitive systems.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05