CVE-2025-22870 | HTTP Proxy bypass using IPv6 Zone IDs in golang.org/x/net

Matching of hosts against proxy patterns can improperly treat an IPv6 zone ID as a hostname component. For example, when the NO_PROXY environment variable is set to "*.example.com", a request to "[::1%25.example.com]:80` will incorrectly match and not be proxied.

Published: 2025-03-12 Last update: 2026-04-16 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-22870 is rated Low Risk (21/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.03%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-22870

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-13 0.06% 0.03% -0.03%
2 2026-04-12 0.02% 0.06% +0.04%
3 2025-11-21 — 0.02% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-22870

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.4 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.8 2.5 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-22870

GitHub Security Advisory for CVE-2025-22870

GHSA-qxp5-gwg8-xv66 · Severity: medium · Ecosystem: go — HTTP Proxy bypass using IPv6 Zone IDs in golang.org/x/net

OS Trackers for CVE-2025-22870

vendor priority summary link
alpine — CVE-2025-22870: 2 source package rows (go, rclone); 5 state rows across 3 repos (3.21-community, 3.22-community, edge-community); fixed 5, open 0. https://security.alpinelinux.org/vuln/CVE-2025-22870
debian not yet assigned CVE-2025-22870 not yet assigned priority: Debian including 3 source packages (golang-1.15, golang-1.19, golang-1.24), 3 status rows across 3 suites (bookworm, bullseye, trixie): open 2, resolved 1. https://security-tracker.debian.org/tracker/CVE-2025-22870
redhat medium — https://access.redhat.com/security/cve/CVE-2025-22870
suse medium CVE-2025-22870 severity moderate: SUSE including 531 source package names (1.23.10-2.7.6:go1.23-1.23.7-150000.1.24.1, 1.23.10-2.7.6:go1.23-doc-1.23.7-150000.1.24.1, …), 1239 product×package rows across 177 product lines (Container bci/golang, Container suse/cosign, … (177 product lines)): Fixed 671, Known Not Affected 337, Known Affected 231. https://www.suse.com/security/cve/CVE-2025-22870/
ubuntu medium CVE-2025-22870 medium priority: Ubuntu including 15 source packages (golang, golang-1.10, …), 116 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 65, needs-triage 38, ignored 10, released 3. https://ubuntu.com/security/CVE-2025-22870

Affected software / configurations for CVE-2025-22870

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-22870

cvelogic Threat Intelligence