<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-19T22:29:30.032955+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-61713</id>
    <title>fkie_cve-2026-61713</title>
    <updated>2026-11-19T22:29:30.036236+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Servo is a lightweight, high-performance web rendering engine for embedding web technologies in applications. Prior to 0.3.0, a sandboxed iframe can use declarative refresh to auto-navigate because RefreshRedirectDue::invoke() in components/script/dom/document/document.rs does not enforce the sandboxed automatic-features flag. The bypass occurs with sandbox="", sandbox="allow-same-origin", sandbox="allow-forms", and sandbox="allow-same-origin allow-forms". Attacker-controlled framed content can replace itself without user action, enabling framed phishing, content replacement, redirect loops, and limited denial of service, but the issue does not by itself permit script execution or parent DOM access. This issue is fixed in version 0.3.0.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-61713"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-pxh3-4qqv-58mg</id>
    <title>GHSA-pxh3-4qqv-58mg — Servo Sandbox bypass: declarative refresh can auto-navigate a sandboxed iframe</title>
    <updated>2026-11-19T22:29:30.036603+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: servo</p>
<p>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.</p>
<p>### Summary
Servo allows a sandboxed iframe to auto-navigate itself via declarative refresh in configurations that should block automatic features.</p>
<p>The issue reproduces in the must-block rows of the matrix:</p>
<p>- `sandbox=""`
- `sandbox="allow-same-origin"`
- `sandbox="allow-forms"`
- `sandbox="allow-same-origin allow-forms"`</p>
<p>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.</p>
<p>### Details
The declarative refresh path is missing sandbox enforcement:</p>
<p>- [components/script/dom/document/document.rs:239] `RefreshRedirectDue::invoke()` contains `TODO: check sandbox`
- [components/script/dom/document/document.rs:4522] the refresh scheduler contains `TODO: handle active sandboxing flag`</p>
<p>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.</p>
<p>What I observed:</p>
<p>- In Servo, the must-block rows above navigated successfully.
- In Chrome, the same rows were blocked.</p>
<p>### PoC
Serve the HTML files in this folder over HTTP.</p>
<p>Files:
- [child.html](https://github.com/user-attachments/files/27770907/child.html)
- [succe…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-pxh3-4qqv-58mg"/>
  </entry>
</feed>
