Google Chromium Mojo Sandbox Escape Vulnerability
Google · Chromium Mojo
Google Chromium's Mojo inter-process communication component on Windows contains a flaw in which an incorrect handle is provided under unspecified circumstances. An attacker who can get a user to open a malicious file can exploit this to escape the browser sandbox, with the attack requiring user interaction and no prior authentication.
Incorrect 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. (Chromium security severity: High)
- Exploited
- Yes, in CISA KEV
- Reports
- 0
- Tactics
- 4/15
How an attack unfolds
Based on MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. mappings. Select a step to see the evidence.Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 1 day before it was disclosed. Public exploit code (PoC-in-GitHub) appeared 11 days after disclosure.
- First seen exploitedVulnCheck KEV evidence1 day before
- Disclosedday 0
- Added to CISA KEVEU database agrees+1 day
- Public exploit codePoC-in-GitHub+11 days
CISA KEV listing is when exploitation was confirmed, not necessarily the first attack.
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
3 TechniqueOne specific attacker behaviour in MITRE ATT&CK, such as T1190 “Exploit Public-Facing Application”. IDs with a dot, like T1059.004, are sub-techniques., grouped by TacticThe attacker’s goal at a stage of an attack in MITRE ATT&CK, such as Initial Access or Persistence. Each technique belongs to one or more tactics. in kill-chain order 3ExecutionTA0002
This vulnerability allows attackers to escape Chrome’s sandbox through a Mojo IPC message crafted to trigger higher privilege. Exploitation has been reported as part of a cyber-espionage campaign.
Privilege EscalationTA0004
Stealth
Detection
0 rules for this CVE · 59 general rules for its techniquesRules for this CVE
0Sigma ruleAn open, vendor-neutral detection rule for log data. Security teams convert Sigma rules into searches for their own SIEM. that reference CVE-2025-2783 directly.CVE-specific rules are not available in this build. Search SigmaHQ ↗
General rules for this CVE’s techniques
These detect the technique in general, not this specific vulnerability.
Exploitation for Client ExecutionT120335 general rules
- Antivirus - Exploitation Framework Signaturecriticalstable
- Droppers Exploiting CVE-2017-11882criticalstable
- Audit CVE Eventcriticaltest
- CVE-2021-31979 CVE-2021-33771 Exploitscriticaltest
- CVE-2021-31979 CVE-2021-33771 Exploits by Sourgumcriticaltest
- Exploit for CVE-2017-8759criticaltest
- Antivirus - APT Malware Signaturecriticalexperimental
- Antivirus - Remote Access Tools Signaturecriticalexperimental
Abuse Elevation Control MechanismT154824 general rules
- Abused Debug Privilege by Arbitrary Parent Processeshightest
- COM Hijack via Sdclthightest
- Credential Dumping Attempt Via Svchosthightest
- Potential Privilege Escalation via Local Kerberos Relay over LDAPhightest
- Regedit as Trusted Installerhightest
- Vulnerable Netlogon Secure Channel Connection Allowedhightest
- Registry Hive File Staged Outside Standard User Profile Pathhighexperimental
- Linux Doas Conf File Creationmediumstable
Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.