# CVE-2026-67201: V 0.5.2 SSRF Bypass via Parser Differential in net.urllib and net.http

> Attackers can bypass host allowlists in the V language standard library to access internal network services via parser differential SSRF.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** GHSA-mvrj-5wv7-cfg9, openSUSE-SU-2026:11480-1

## What is CVE-2026-67201?

CVE-2026-67201 is a high-severity server-side request forgery vulnerability in vlang v, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

V through 0.5.2, fixed in commit 85859f0, contains a server-side request forgery (SSRF) bypass vulnerability that allows attackers to circumvent host-based allowlists by exploiting a parser differential between net.urllib and net.http. Attackers can craft a URL containing a backslash in the authority section such that net.urllib.parse() extracts the trusted host for allowlist validation while net.http.get() normalizes the backslash and connects to the internal host, enabling access to internal network services that the allowlist was intended to block.

Weakness: CWE-436 (Interpretation Conflict)

## Which versions are affected by CVE-2026-67201?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `vlang` | openSUSE:Tumbleweed | All versions | 0.5.2-2.1 |

## How do I fix CVE-2026-67201?

Apply the vendor's patch.

## Is CVE-2026-67201 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67201 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-67201 and fix it if it is affected.

What it is: CVE-2026-67201 is a high-severity server-side request forgery vulnerability in vlang v, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67201 exists.

Affected product: vlang v. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2026-67201/ (Markdown: https://insights.sbomify.com/CVE-2026-67201/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-67201
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-67201
- OSV: https://osv.dev/vulnerability/CVE-2026-67201

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