{"answers":{"affected":"1 open source package ship an affected version, including webpage.","exploited":"There is no known exploitation of RUSTSEC-2026-0407 in the wild and no public exploit code.","fix":"Upgrade webpage to 2.1.0 or later.","what":"RUSTSEC-2026-0407 is a vulnerability in webpage, published on 22 Oct 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0407 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0407 is a vulnerability in webpage, published on 22 Oct 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0407 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- webpage (crates.io): affected from 0.0.0-0; fixed in 2.1.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/RUSTSEC-2026-0407/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0407/index.md)","id":"RUSTSEC-2026-0407","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0407/index.md","name":"RUSTSEC-2026-0407","record":{"aliases":["GHSA-23hp-j76v-pcwj"],"analysis":null,"analysis_generated_by":null,"assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Applications that pass attacker-controlled URLs to `webpage` versions before\n2.1.0 may be vulnerable to server-side request forgery (SSRF) or local file\ndisclosure.\n\n`HTTP::fetch` and `Webpage::from_url` passed URLs to libcurl without\nrestricting the URL scheme or validating the resolved destination IP address.\nRedirects were followed without checking whether the new destination was\ninternal. Depending on how the application uses the response, an attacker\ncould:\n\n- Read local files accessible to the application process using `file://` URLs.\n- Cause requests to internal or link-local services (e.g. cloud metadata\n  endpoints at `http://169.254.169.254`) via direct private-IP URLs or by\n  chaining HTTP redirects through an attacker-controlled server.\n\nStarting in 2.1.0, `HTTP::fetch` and `Webpage::from_url` reject non-HTTP(S)\nURL schemes and destinations that resolve to non-public IP addresses, including\nafter redirects. Applications that intentionally fetch trusted internal\nresources can opt in to the previous behavior with `HTTP::fetch_unrestricted`\nor `Webpage::from_url_unrestricted`.\n\nReported by [Aiden Mohan](https://github.com/AidenMohan).","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"SSRF and local file disclosure via unvalidated URLs","id":"RUSTSEC-2026-0407","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["2.1.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"webpage","purl":"pkg:cargo/webpage","source":"RUSTSEC-2026-0407"}],"products":null,"published":"2026-10-22","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":null,"url":"https://insights.sbomify.com/RUSTSEC-2026-0407/"}