
Loading

Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
A GitHub-reviewed security advisory, not necessarily under active exploitation the way our CISA KEV advisories are, but a real, disclosed vulnerability in an open-source dependency.
Affected packages
Vulnerable: < 0.3.0
Patched in 0.3.0
Details
A sandboxed iframe can auto-navigate itself via declarative refresh even when automatic features should be blocked. This allows attacker-controlled embedded content to redirect itself without user action.
Servo allows a sandboxed iframe to auto-navigate itself via declarative refresh in configurations that should block automatic features.
The issue reproduces in the must-block rows of the matrix:
sandbox=""sandbox="allow-same-origin"sandbox="allow-forms"sandbox="allow-same-origin allow-forms"This is a client-side sandbox-policy bypass. It does not by itself prove script execution or parent DOM access, but it does let attacker-controlled sandboxed content redirect itself without user action.
The declarative refresh path is missing sandbox enforcement:
RefreshRedirectDue::invoke() contains TODO: check sandboxTODO: handle active sandboxing flagThe implementation currently schedules and executes the refresh without enforcing the sandboxed automatic-features restriction described by the HTML spec comments in the same code.
What I observed:
Serve the HTML files in this folder over HTTP.
Files:
Steps:
viewer.html over HTTP.child.html.success.html page.This is a client-side sandbox-policy bypass.
Confirmed impact:
EPSS, exploit probability
Low0.54%
estimated chance of real-world exploitation in the next 30 days, higher than 46.1% of every CVE FIRST.org scores
Refreshed 11/19/2026, via FIRST.org's EPSS model, not CVSS, this measures likelihood of exploitation, not how severe it would be.
More rust advisories
Talk to us about this
Find out whether this dependency (or others like it) is actually reachable in your codebase.
Get help patching, or building dependency-scanning into your pipeline going forward.
A secure code review or supply chain review finds this before an advisory does.