CVE-2025-2783 — Google Chromium Mojo Sandbox Escape Vulnerability

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

CISA required action CISA

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

US federal deadline: Apr 17, 2025 — passed 546 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

1. Identify exposed assets running the affected vendor/product/version combinations (Google Chrome).
2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
4. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
5. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
6. EPSS ahead of 95% of scored CVEs: prioritize it in the patch queue.
7. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 9.24%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

• Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
• Hunt retroactively in logs from before Mar 27, 2025 (KEV listing): exploitation may have started earlier.

Timeline

What happened to this CVE, newest first.

• 2026
• Affected products added · google/chrome
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• SSVC assessment updated
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• Record published
  Oct 13, 2026
• Affected products added · google/chrome
  Oct 13, 2026 · NIST National Vulnerability Database
• CVSS changed · 8.3
  Oct 13, 2026 · NIST National Vulnerability Database
• Source status changed · → Analyzed
  Oct 13, 2026 · NIST National Vulnerability Database
• Added to CISA KEV (detected)
  Oct 13, 2026 · CISA Known Exploited Vulnerabilities
• Record created in this database
  Oct 13, 2026 · CISA Known Exploited Vulnerabilities
• 2025
• Added to CISA KEV catalog
  Mar 26, 2025 · CISA
• CVE published
  Mar 26, 2025 · Chrome

Source activity

Repeated readings are counted rather than listed.

• 2× References added · Oct 13, 2026 – Oct 13, 2026
• 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

5 on the record

• www.cisa.gov/known-exploited-vulnerabilities-catalog
  US Government Resource, NIST National Vulnerability Database
• github.com/advisories/GHSA-hfqm-jfc6-rh2f
  GitHub Security Advisories
• issues.chromium.org/issues/405143032
  Permissions Required, NIST National Vulnerability Database
• nvd.nist.gov/vuln/detail/CVE-2025-2783
  GitHub Security Advisories
• chromereleases.googleblog.com/2025/03/stable-channel-update-for-desktop_25.html
  Release Notes, NIST National Vulnerability Database

Elsewhere on this site

Related CVEs (same products)

• High CVE-2026-110172 Use after free in Media in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to... 1d
• Medium CVE-2026-110170 Use after free in Bindings in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to... 1d
• High CVE-2026-110171 Use after free in Media in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to... 1d
• Critical CVE-2026-110165 Use after free in Core in Google Chrome on on Android prior to 155.0.8059.79 allowed a remote... 1d
• High CVE-2026-110163 Use after free in DOM in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to... 1d
• High CVE-2026-110164 Use after free in DOM in Google Chrome prior to 155.0.8059.79 allowed a remote attacker to... 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

• No fixed version, patch or mitigation documented.
• No CWE classification.
• No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
• No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
• No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-2783 is "Google Chromium Mojo Sandbox Escape Vulnerability", rated High. It affects Chrome (Google); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 8.3 describes technical severity. EPSS 9.24% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.