# RUSTSEC-2026-0407: SSRF and local file disclosure via unvalidated URLs


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Also known as:** GHSA-23hp-j76v-pcwj

## What is RUSTSEC-2026-0407?

RUSTSEC-2026-0407 is a vulnerability in webpage, published on 22 Oct 2026. 

### Official description

Applications that pass attacker-controlled URLs to `webpage` versions before
2.1.0 may be vulnerable to server-side request forgery (SSRF) or local file
disclosure.

`HTTP::fetch` and `Webpage::from_url` passed URLs to libcurl without
restricting the URL scheme or validating the resolved destination IP address.
Redirects were followed without checking whether the new destination was
internal. Depending on how the application uses the response, an attacker
could:

- Read local files accessible to the application process using `file://` URLs.
- Cause requests to internal or link-local services (e.g. cloud metadata
  endpoints at `http://169.254.169.254`) via direct private-IP URLs or by
  chaining HTTP redirects through an attacker-controlled server.

Starting in 2.1.0, `HTTP::fetch` and `Webpage::from_url` reject non-HTTP(S)
URL schemes and destinations that resolve to non-public IP addresses, including
after redirects. Applications that intentionally fetch trusted internal
resources can opt in to the previous behavior with `HTTP::fetch_unrestricted`
or `Webpage::from_url_unrestricted`.

Reported by [Aiden Mohan](https://github.com/AidenMohan).

## Which versions are affected by RUSTSEC-2026-0407?

1 open source package ship an affected version, including webpage.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `webpage` | crates.io | From 0.0.0-0 | 2.1.0 |

## How do I fix RUSTSEC-2026-0407?

Upgrade webpage to 2.1.0 or later.

## Is RUSTSEC-2026-0407 being exploited?

There is no known exploitation of RUSTSEC-2026-0407 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2026-0407 and fix it if it is affected.

What it is: RUSTSEC-2026-0407 is a vulnerability in webpage, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of RUSTSEC-2026-0407 in the wild and no public exploit code.

Affected packages and fixed versions:
- webpage (crates.io): affected from 0.0.0-0; fixed in 2.1.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/RUSTSEC-2026-0407/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0407/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2026-0407

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2026-0407/
Summaries are generated and may contain mistakes; the official description above is the record.