CVE-2025-4673 | Sensitive headers not cleared on cross-origin redirect in net/http

Proxy-Authorization and Proxy-Authenticate headers persisted on cross-origin redirects potentially leaking sensitive information.

Published: 2025-06-11 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-4673 is rated Moderate Risk (42.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.56%). Review affected assets and schedule remediation.

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-4673

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-06-15 0.07% 0.56% +0.49%
2 2026-04-07 0.01% 0.07% +0.06%
3 2025-11-21 — 0.01% —

Full EPSS history (5 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.8 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 4.0 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-4673

OS Trackers for CVE-2025-4673

vendor priority summary link
alpine medium CVE-2025-4673: 1 source package rows (go); 2 state rows across 2 repos (3.22-community, edge-community); fixed 2, open 0. https://security.alpinelinux.org/vuln/CVE-2025-4673
debian not yet assigned CVE-2025-4673 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-4673
redhat medium — https://access.redhat.com/security/cve/CVE-2025-4673
suse medium CVE-2025-4673 severity moderate: SUSE including 124 source package names (1.23.10-2.7.6:go1.23-1.23.10-150000.1.34.1, 1.23.10-2.7.6:go1.23-doc-1.23.10-150000.1.34.1, …), 435 product×package rows across 36 product lines (Container bci/golang, Container suse/sl-micro/6.0/baremetal-os-container, … (36 product lines)): Fixed 401, Known Not Affected 34. https://www.suse.com/security/cve/CVE-2025-4673/
ubuntu medium CVE-2025-4673 medium priority: Ubuntu including 15 source packages (golang, golang-1.10, …), 108 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 57, needs-triage 45, ignored 3, released 3. https://ubuntu.com/security/CVE-2025-4673

Affected software / configurations for CVE-2025-4673

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-4673

cvelogic Threat Intelligence