CVE-2025-2783
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)
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The vulnerability involves a sandbox escape triggered by a malicious file, which requires the victim to open or run the file locally. It is not delivered via HTTP requests, so a web application firewall cannot filter it.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-2783 being exploited?
Yes. CVE-2025-2783 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-2783?
CVE-2025-2783 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-2783?
Yes. A fix has been recorded for CVE-2025-2783. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-2783 affect?
CVE-2025-2783 affects google:chrome. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected< 134.0.6998.177
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Public exploit code: 1 on Exploit-DB · 5 GitHub proofs of concept
- Microsoft Edge Renderer Process (Mojo IPC) 134.0.6998.177 - Sandbox Escape · webapps · 11 Aug 2025
- Alchemist3dot14/CVE-2025-2783 · 33 ★
- byteReaper77/CVE-2025-2783 · 8 ★
- bjrjk/CVE-2025-2783 · 1 ★
- ElianGonzi00/CVE-2025-2783 · 1 ★
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 28 Mar 2025 (SSVC 2.0.3).
timeline
- 26 Mar 2025Published
- 27 Mar 2025Added to CISA KEV (exploited in the wild) · same day later
- 28 Mar 2025CISA SSVC assessment: exploitation active · 1 day later
- 6 Apr 2025First public exploit or proof of concept · 9 days later
- 17 Apr 2025CISA remediation due date (US federal agencies) · 11 days later
- 26 Feb 2026CVE record last updated · 316 days (about 11 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
- Linkchromereleases.googleblog.com /2025/03/stable-channel-update-for-desktop_25.html
- Linkissues.chromium.org /issues/405143032
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-2783
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Exploit-DB: published exploits
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.