GHSA-PXH3-4QQV-58MG
Vulnerability from github – Published: 2026-11-19 20:45 – Updated: 2026-11-19 20:45A 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.
Summary
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.
Details
The declarative refresh path is missing sandbox enforcement:
- [components/script/dom/document/document.rs:239]
RefreshRedirectDue::invoke()containsTODO: check sandbox - [components/script/dom/document/document.rs:4522] the refresh scheduler contains
TODO: handle active sandboxing flag
The 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:
- In Servo, the must-block rows above navigated successfully.
- In Chrome, the same rows were blocked.
PoC
Serve the HTML files in this folder over HTTP.
Files: - child.html - success.html - viewer.html
Steps:
- Open
viewer.htmlover HTTP. - The page shows a visible sandboxed iframe.
- In a correct browser, the iframe stays on
child.html. - In Servo, the iframe visibly turns into the
success.htmlpage.
Impact
This is a client-side sandbox-policy bypass.
Confirmed impact:
- autonomous iframe self-navigation in sandbox configurations that should block it
- framed phishing / content swap after initial render
- redirect loops / annoyance / limited DoS
{
"affected": [
{
"package": {
"ecosystem": "crates.io",
"name": "servo"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.3.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-61713"
],
"database_specific": {
"cwe_ids": [
"CWE-693"
],
"github_reviewed": true,
"github_reviewed_at": "2026-11-19T20:45:22Z",
"nvd_published_at": "2026-11-17T22:19:20Z",
"severity": "HIGH"
},
"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.\n\n### Summary\nServo allows a sandboxed iframe to auto-navigate itself via declarative refresh in configurations that should block automatic features.\n\nThe issue reproduces in the must-block rows of the matrix:\n\n- `sandbox=\"\"`\n- `sandbox=\"allow-same-origin\"`\n- `sandbox=\"allow-forms\"`\n- `sandbox=\"allow-same-origin allow-forms\"`\n\nThis 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.\n\n### Details\nThe declarative refresh path is missing sandbox enforcement:\n\n- [components/script/dom/document/document.rs:239] `RefreshRedirectDue::invoke()` contains `TODO: check sandbox`\n- [components/script/dom/document/document.rs:4522] the refresh scheduler contains `TODO: handle active sandboxing flag`\n\nThe implementation currently schedules and executes the refresh without enforcing the sandboxed automatic-features restriction described by the HTML spec comments in the same code.\n\nWhat I observed:\n\n- In Servo, the must-block rows above navigated successfully.\n- In Chrome, the same rows were blocked.\n\n### PoC\nServe the HTML files in this folder over HTTP.\n\nFiles:\n- [child.html](https://github.com/user-attachments/files/27770907/child.html)\n- [success.html](https://github.com/user-attachments/files/27770910/success.html)\n- [viewer.html](https://github.com/user-attachments/files/27770911/viewer.html)\n\nSteps:\n\n1. Open `viewer.html` over HTTP.\n2. The page shows a visible sandboxed iframe.\n3. In a correct browser, the iframe stays on `child.html`.\n4. In Servo, the iframe visibly turns into the `success.html` page.\n\n### Impact\nThis is a client-side sandbox-policy bypass.\n\nConfirmed impact:\n\n- autonomous iframe self-navigation in sandbox configurations that should block it\n- framed phishing / content swap after initial render\n- redirect loops / annoyance / limited DoS",
"id": "GHSA-pxh3-4qqv-58mg",
"modified": "2026-11-19T20:45:22Z",
"published": "2026-11-19T20:45:22Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/servo/servo/security/advisories/GHSA-pxh3-4qqv-58mg"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-61713"
},
{
"type": "WEB",
"url": "https://github.com/servo/servo/pull/45116"
},
{
"type": "WEB",
"url": "https://github.com/servo/servo/commit/70df09e72f40fab45493ffee3821e7a1a31ae4d2"
},
{
"type": "PACKAGE",
"url": "https://github.com/servo/servo"
},
{
"type": "WEB",
"url": "https://github.com/servo/servo/releases/tag/v0.3.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L",
"type": "CVSS_V3"
}
],
"summary": "Servo Sandbox bypass: declarative refresh can auto-navigate a sandboxed iframe"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.