CVE-2026-67201

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2026-07-29. A secondary CVSS source baseline 8.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
8.6EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.6Exploit: Elevated riskExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

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.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
70
EG Risk 70/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity86% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 29, 2026

Last Modified

July 30, 2026

Advisory Details (4)

Auto-updated Jul 29, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
generic

V 0.5.2 SSRF Bypass via Parser Differential in net.urllib and net.http | Advisories | VulnCheck

https://www.vulncheck.com/advisories/v-ssrf-bypass-via-parser-differential-in-net-urllib-and-net-http
github_commit

commit 85859f0f3498 (vlang/v)

Fix landed in vlang/v commit 85859f0f3498 — awaiting tagged release

https://github.com/vlang/v/commit/85859f0f3498d4091b38009c45ed390a97eeedc2
github_pr

net.urllib: reject backslashes in URL authorities

Fix merged in vlang/v PR #27947 on 2026-07-26 — awaiting tagged release

https://github.com/vlang/v/pull/27947
generic

Security: SSRF in net.urllib due to backslash (\) parsing · Issue #27945 · vlang/v · GitHub

https://github.com/vlang/v/issues/27945

Vendor Advisories for CVE-2026-67201(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 73× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 221 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:13 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-07 00:00 UTCEG score recompute
  5. 2026-10-07 00:00 UTCGHSA enrichment
  6. 2026-10-06 15:18 UTCEPSS rescore
  7. 2026-10-05 20:51 UTCEG score recompute
  8. 2026-10-05 20:51 UTCGHSA enrichment
  9. 2026-10-05 17:43 UTCEPSS rescore
  10. 2026-10-05 02:36 UTCEG score recompute
  11. 2026-10-05 02:36 UTCGHSA enrichment
  12. 2026-10-04 23:22 UTCEPSS rescore
  13. 2026-10-04 07:00 UTCEG score recompute
  14. 2026-10-04 07:00 UTCGHSA enrichment
  15. 2026-10-03 14:26 UTCEPSS rescore
  16. 2026-10-02 17:57 UTCEG score recompute
  17. 2026-10-02 17:57 UTCGHSA enrichment
  18. 2026-10-02 17:56 UTCEPSS rescore
  19. 2026-10-01 19:50 UTCEPSS rescore
  20. 2026-10-01 15:06 UTCGHSA enrichment
  21. 2026-10-01 03:33 UTCEG score recompute
  22. 2026-10-01 03:33 UTCGHSA enrichment
  23. 2026-09-30 15:03 UTCEPSS rescore
  24. 2026-09-29 07:35 UTCEG score recompute
  25. 2026-09-29 07:35 UTCGHSA enrichment
Show 75 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 07:13 UTCGHSA enrichment
  3. 2026-09-27 19:36 UTCEG score recompute
  4. 2026-09-27 19:36 UTCGHSA enrichment
  5. 2026-09-27 13:48 UTCEPSS rescore
  6. 2026-09-26 15:59 UTCEPSS rescore
  7. 2026-09-25 05:37 UTCEG score recompute
  8. 2026-09-25 05:37 UTCGHSA enrichment
  9. 2026-09-24 09:21 UTCGHSA enrichment
  10. 2026-09-23 21:48 UTCEG score recompute
  11. 2026-09-23 21:48 UTCGHSA enrichment
  12. 2026-09-23 17:54 UTCEPSS rescore
  13. 2026-09-23 03:21 UTCEG score recompute
  14. 2026-09-23 03:21 UTCGHSA enrichment
  15. 2026-09-22 15:48 UTCEG score recompute
  16. 2026-09-22 15:48 UTCGHSA enrichment
  17. 2026-09-20 20:16 UTCEPSS rescore
  18. 2026-09-20 00:22 UTCEG score recompute
  19. 2026-09-20 00:22 UTCGHSA enrichment
  20. 2026-09-19 04:53 UTCEG score recompute
  21. 2026-09-19 04:52 UTCGHSA enrichment
  22. 2026-09-18 19:28 UTCEPSS rescore
  23. 2026-09-18 15:16 UTCGHSA enrichment
  24. 2026-09-18 01:39 UTCEG score recompute
  25. 2026-09-18 01:39 UTCGHSA enrichment
  26. 2026-09-17 01:35 UTCEG score recompute
  27. 2026-09-17 01:35 UTCGHSA enrichment
  28. 2026-09-16 14:08 UTCEPSS rescore
  29. 2026-09-16 05:47 UTCEG score recompute
  30. 2026-09-16 05:47 UTCGHSA enrichment
  31. 2026-09-16 05:15 UTCEPSS rescore
  32. 2026-09-15 07:50 UTCEG score recompute
  33. 2026-09-15 07:50 UTCGHSA enrichment
  34. 2026-09-14 16:42 UTCGHSA enrichment
  35. 2026-09-14 05:08 UTCGHSA enrichment
  36. 2026-09-13 17:35 UTCEG score recompute
  37. 2026-09-13 17:35 UTCGHSA enrichment
  38. 2026-09-13 06:01 UTCGHSA enrichment
  39. 2026-09-12 18:28 UTCEG score recompute
  40. 2026-09-12 18:28 UTCGHSA enrichment
  41. 2026-09-12 06:55 UTCGHSA enrichment
  42. 2026-09-11 19:22 UTCEG score recompute
  43. 2026-09-11 19:22 UTCGHSA enrichment
  44. 2026-09-11 14:53 UTCEPSS rescore
  45. 2026-09-11 09:37 UTCEPSS rescore
  46. 2026-09-11 07:23 UTCGHSA enrichment
  47. 2026-09-10 19:50 UTCEG score recompute
  48. 2026-09-10 19:50 UTCGHSA enrichment
  49. 2026-09-10 04:31 UTCGHSA enrichment
  50. 2026-09-09 07:47 UTCEG score recompute
  51. 2026-09-09 07:47 UTCGHSA enrichment
  52. 2026-09-08 22:01 UTCEPSS rescore
  53. 2026-09-07 20:46 UTCEG score recompute
  54. 2026-09-07 20:46 UTCGHSA enrichment
  55. 2026-09-07 16:01 UTCEPSS rescore
  56. 2026-09-06 18:23 UTCEG score recompute
  57. 2026-09-06 18:23 UTCGHSA enrichment
  58. 2026-09-06 13:47 UTCEPSS rescore
  59. 2026-09-06 06:49 UTCGHSA enrichment
  60. 2026-09-05 19:04 UTCEG score recompute
  61. 2026-09-05 19:04 UTCGHSA enrichment
  62. 2026-09-05 15:31 UTCEPSS rescore
  63. 2026-09-05 05:10 UTCEG score recompute
  64. 2026-09-05 05:10 UTCGHSA enrichment
  65. 2026-09-04 11:54 UTCEG score recompute
  66. 2026-09-04 11:54 UTCGHSA enrichment
  67. 2026-09-04 05:07 UTCEPSS rescore
  68. 2026-09-02 14:12 UTCEPSS rescore
  69. 2026-09-01 22:46 UTCEG score recompute
  70. 2026-09-01 22:46 UTCGHSA enrichment
  71. 2026-09-01 13:54 UTCEPSS rescore
  72. 2026-09-01 04:40 UTCEPSS rescore
  73. 2026-08-31 23:55 UTCGHSA enrichment
  74. 2026-08-30 22:27 UTCEG score recompute
  75. 2026-08-30 22:27 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-67201?
CVE-2026-67201 is a high vulnerability published on July 29, 2026. 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…
When was CVE-2026-67201 disclosed?
CVE-2026-67201 was first published on July 29, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67201 actively exploited?
CVE-2026-67201 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67201?
CVE-2026-67201 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-67201?
An upstream fix for CVE-2026-67201 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-67201 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-67201

Explore →

Is Your Infrastructure Affected by CVE-2026-67201?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs