Safeguard
Vulnerability Analysis•

CVE-2019-25154: Critical iframe Sandbox Escape in Google Chrome

CVE-2019-25154 is an iframe sandbox escape in Chrome before 77.0.3865.75, scored 9.6 Critical by NVD, Medium by Chromium. Update to 77.0.3865.75 or later.

Safeguard Security Team
3 min read

CVE-2019-25154 is an inappropriate implementation in iframe handling in Google Chrome before 77.0.3865.75. NVD scores it 9.6 Critical, while Chromium rates it Medium. A crafted page could potentially escape the sandbox, and the record says a user must interact. Update to 77.0.3865.75 or later.

What's affected

  • Product: Google Chrome on desktop.
  • Affected: versions before 77.0.3865.75, per the NVD record.
  • Fixed: 77.0.3865.75, promoted to the Stable channel on 10 September 2019 according to the Chrome Releases post.
  • Severity: NVD 9.6 Critical (AV:N/AC:L/PR:N/UI:R/S:C). Chromium: Medium. Both ratings come from sources we read.
  • No CWE is assigned in the record.

How to check if you're exposed

  • Open chrome://settings/help to see the current version and trigger an update check.
  • For fleets, use your endpoint tooling or Chrome management reports and filter for versions below 77.0.3865.75.
  • Check Chromium based browsers and embedded browser components separately, because each vendor picks its own release schedule.
  • Confirm that automatic update is not disabled by policy on any managed machine.

What to do now

  1. Update Chrome to 77.0.3865.75 or later. Current releases are much newer.
  2. Find machines where updates are blocked or delayed by policy, for example golden images and VDI.
  3. Review other Chromium based software your teams use, and ask vendors which Chromium version each build includes.
  4. Keep a continuous inventory of browser versions so old builds stand out without a manual audit.

Why it matters

The record describes inappropriate implementation in iframe, which allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. The sandbox is the layer that limits what a compromised page can do to the machine, so a flaw there matters more than its name suggests. The scope in the vector is changed (S:C), which is what lifts the score to 9.6.

Chromium's own label is Medium. The Chrome Releases post lists the issue among medium severity fixes and credits an external reporter with a reward. The record's KEV flag is false and the release post does not describe attacks. Treat the gap between 9.6 and Medium as a reason to read both, not a reason to wait.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Why would Chrome call it Medium and NVD call it Critical?

The score of 9.6 reflects the scoring rules for a changed scope, user interaction and full impact. Chromium ranks bugs by its own severity guidelines. Neither claims it is under attack.

Does updating Chrome fix other Chromium browsers?

No. Other browsers ship their own builds. Check each vendor for the Chromium version it carries.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.