SSRF and local file disclosure via unvalidated URLs

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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…

Published by the source

22 Oct 2026, 12:00 UTC

Last modified by the source

26 Oct 2026, 14:00 UTC

Source last checked

27 Oct 2026, 06:25 UTC

1. Revision 1 · created · 27 Oct 2026

   Published from osv record RUSTSEC-2026-0407

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-23hp-j76v-pcwj

Advisory: SSRF and local file disclosure via unvalidated URLs
IDs: GHSA-23hp-j76v-pcwj
Record: https://patchnext.com/advisories/rustsec-2026-0407 (revision 1, source checked 27 Oct 2026, 06:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: webpage 2.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io webpage: affected >= 0.0.0-0, < 2.1.0; fixed in 2.1.0

## Suggested inspection (read-only)
- crates.io webpage: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on webpage.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/RUSTSEC-2026-0407 (OSV record RUSTSEC-2026-0407 lists affected ranges: crates.io webpage >=0.0.0-0 <2.1.0 (fixed))

Commands are suggestions: review each one before running it.