RUSTSEC-2026-0592: Stack overflow in `Url::origin()` on nested `blob:` URLs
Unknown
- OSV id
- RUSTSEC-2026-0592
- Also known as
- GHSA-hrj5-67jp-wqp9
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| url Cargo |
>= 0.0.0-0, < 2.5.9 | 2.5.9 |
How to fix it
Upgrade url to 2.5.9 or later.
cargo update -p url --precise 2.5.9
- If it is an indirect dependency, `cargo update -p` still works; if a parent crate pins an older version, upgrade that crate.
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
Not sure whether your project uses an affected version? Check your lockfile below for free.
Details
In url 2.5.8 and earlier, Url::origin() handled a blob: URL by parsing its path as another URL and calling itself on the result. It did so regardless of the inner URL's scheme, blob included. Each blob: prefix cost one stack frame, with no limit on nesting depth. Url::parse() accepts a URL with 10,000 blob: prefixes followed by https://example.com/ (50,020 bytes in total); calling Url::origin() on it overflowed the default 2 MiB stack of a spawned thread.
A stack overflow aborts the whole process, and catch_unwind() does not catch it. One such URL crashes any program that calls Url::origin() on untrusted input. url::quirks::origin() also calls Url::origin(). For example, Servo's URL.origin DOM getter calls url::quirks::origin(), so a script on a page can trigger the overflow.
url 2.5.9 follows the URL Standard: Url::origin() takes the origin of the inner URL only when its scheme is http, https, or file, returns an opaque origin otherwise, and never calls itself. A blob: URL with another inner scheme that previously produced a tuple origin, such as blob:ws://... or blob:blob:https://..., now returns an opaque origin.
References
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: RustSec Advisory Database via OSV.dev (CC0 1.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.