Skip to main content
VulnerabilityPublished

CVE-2026-67201: vlang v · Interpretation Conflict

Affects vlang vSource CVE Database V5

0

Not known to be exploited · CVSS 7.7 High : upgrade to 0.5.3 soon.

Data as of 27 Oct 2026, 17:11 UTC

CVSS 4.0 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.5.3
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade vlang/v to 0.5.3.

Affected software

ProductAffectedFixed in
vlangAffected
  • <=0.5.2
Fixed in–
GitHubvlang/vpkg:github/vlang/vOther threatsAffected
  • <0.5.3
Fixed in
  • 0.5.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Vlang starting from version 0.5.3, which addresses the parsing inconsistency. Users should upgrade to version 0.5.3 or later to remediate this vulnerability. No other official remediation or temporary fixes are documented. Patch status is not explicitly confirmed beyond the fix commit, so users should verify the vendor advisory for the latest remediation guidance.

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.

References

Community reviews

Loading reviews…