CVE-2025-2783

HIGH8.3

CISA KEV

Published 2025-03-26 · Updated 2026-06-17 · Source chrome-cve-admin@google.com

Summary

CVE-2025-2783 is a high-severity (CVSS 8.3) vulnerability in Google Chromium Mojo. CISA added it to the Known Exploited Vulnerabilities catalog on March 27, 2025, which means exploitation in the wild has been confirmed; US federal agencies had to remediate it by April 17, 2025. CISA does not currently list it as used in ransomware campaigns. Google has 76 vulnerabilities in the KEV catalog, 0 of them linked to ransomware.

All 76 known-exploited Google vulnerabilities →

Description

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)

CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

CISA Known-Exploited Vulnerability

Product: Google — Chromium Mojo

Name: Google Chromium Mojo Sandbox Escape Vulnerability

Date added: 2025-03-27 · Due: 2025-04-17

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

References

View on NVD

More exploited Google vulnerabilities

Most recently added to CISA KEV

CVE-2026-111497
Brotli — Google Brotli Unchecked Return Value Vulnerability
added 2026-10-27
CVE-2026-58704
Pixel — Google Pixel Improper Authorization Vulnerability
added 2026-09-16
CVE-2026-87491
Chromium V8 — Google Chromium V8 Out of Bounds Write Vulnerability
added 2026-09-09
CVE-2026-85046
Chromium V8 — Google Chromium V8 Type Confusion Vulnerability
added 2026-09-04
CVE-2026-11645
Chromium V8 — Google Chromium V8 Out-of-Bounds Read and Write Vulnerability
added 2026-06-09
CVE-2026-5281
Dawn — Google Dawn Use-After-Free Vulnerability
added 2026-04-01

View all →

Related CVEs

Same severity, most recent

CVE-2026-68933
Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to 5.2.3, public dashboard passwords were stored in plaintext, accepted through a URL query parameter, and checked without effective attempt throttling. The vulnerable surface is public password-protected dashboard storage and validation routes. An unauthenticated attacker targets a public password-protected dashboard and repeatedly submits candidate passwords or obtains password-bearing server or proxy logs. Unlimited online guesses enable brute force, while cleartext storage and URL transport expose the secret in application storage and server or proxy access logs. The target must be a public dashboard with password protection enabled. Even failed attempts reveal chart count and configuration without the password; a recovered password grants access to the protected dashboard and its chart data. This vulnerability is fixed in 5.2.3.
2026-11-06 · score 7.5
CVE-2026-50240
A flaw was found in OpenShift Pipelines-as-Code (PAC). PAC does not verify whether the creator of a Repository custom resource has permission to create PipelineRuns. A namespace user with only Repository and Secret create/delete permissions can cause PAC to execute attacker-controlled PipelineRuns as the auto-provisioned pipeline ServiceAccount, which carries ClusterRole/edit by default. This results in namespace-scoped privilege escalation, enabling Secret read, resource creation/modification/deletion, and potential supply chain injection in CI/CD namespaces.
2026-11-06 · score 8.8
CVE-2026-123791
A vulnerability was detected in OpenBMB Internet of Agents up to 9d78e88e47160eb42ee1ee8538c05e1c2c47877a. This affects the function _primary_field_query of the file common/utils/milvus_utils.py of the component Agent Registry. The manipulation of the argument key results in improper neutralization of special elements in data query logic. The attack may be launched remotely. The exploit is now public and may be used. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. The project was informed of the problem early through an issue report but has not responded yet.
2026-11-06 · score 7.3
CVE-2026-85736
Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to 5.2.3, connection creation or update stored attacker-chosen absolute SSL and SSH file paths, and later connection cleanup passed those stored paths to fs.unlink without a path restriction. The vulnerable surface is data-connection certificate and SSH-key cleanup when a connection is removed. A user with createOwn and deleteOwn permissions on their own team stores a target path in a connection and then deletes the connection to trigger cleanup; default self-signup grants teamOwner these permissions. The cleanup routine treats the stored SSL or SSH path as a managed certificate path and unlinks the referenced file; duplicateConnection provides a second advisory-identified trigger. The attacker must be able to create or update and then delete a connection on their own team. The default container runs Chartbrew as uid 0, while deployments with a less-privileged process are limited by that process's deletion permissions. The attacker can delete files such as /code/.env or application source, causing integrity loss and service disruption. This issue is fixed in version 5.2.3.
2026-11-06 · score 8.1
CVE-2026-85726
Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to 5.2.3, a date-typed MongoDB variable placed inside a quoted query placeholder was inserted as an unescaped string, unlike the safely escaped or coerced string, number, and Boolean branches. The vulnerable surface is mongoDB-backed public, shareable, or embedded charts processed by date-variable substitution. An unauthenticated user supplies a crafted URL filter to a public, shareable, or embedded MongoDB chart whose query places a date-typed variable in a quoted literal. The crafted date value breaks out of the quoted literal and changes query logic; the chart's returned row count becomes a Boolean oracle for character-by-character field extraction. The chart must be externally reachable and use the vulnerable date-in-quoted-placeholder branch. Extraction is read-only and limited to one queried collection per request, and it requires neither an account nor a known field value. The blind oracle can disclose any field in the queried collection, including secrets the chart does not display. This issue is fixed in version 5.2.3.
2026-11-06 · score 7.5