gitoxide's gix-url crate (<= 0.32.0, fixed in 0.37.1) uses a hand-rolled URL parser that does not treat '?' or '#' as terminating the authority component, contrary to RFC 3986. As a consequence, gix-transport's HTTP redirect identity guard (can_reuse_identity) compares the wrong host and fails open. An attacker controlling a redirect response can craft a Location header of the form ?@ so that gitoxide sends the caller's HTTP Basic Authorization credentials to an unintended host. gix-transport is affected in versions <= 0.49.0 (fixed in 0.58.1).
CVE-2026-82247
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 22%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (2)
Auto-updated Aug 28, 2026gitoxide before 0.37.1 HTTP Basic credential leak via URL parsing | Advisories | VulnCheck
https://www.vulncheck.com/advisories/gitoxide-before-0.37.1-http-basic-credential-leak-via-url-parsinggix-url authority is not terminated by '?'/'#', causing the gix-transport redirect identity guard to fail open and leak HTTP Basic credentials · Advisory · GitoxideLabs/gitoxide · GitHub
https://github.com/GitoxideLabs/gitoxide/security/advisories/GHSA-jrcm-326h-gpp8Vendor Advisories for CVE-2026-82247(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 11× in last 7d / 11× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 20:50 UTCGHSA enrichment
- 2026-08-29 07:55 UTCGHSA enrichment
- 2026-08-28 18:57 UTCGHSA enrichment
- 2026-08-28 16:36 UTCEG score recompute
- 2026-08-28 16:36 UTCGHSA enrichment
- 2026-08-28 15:37 UTCEG score recompute
- 2026-08-28 15:37 UTCGHSA enrichment
- 2026-08-28 12:22 UTCEG score recompute
- 2026-08-28 11:23 UTCEG score recompute
- 2026-08-28 11:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-522
- CVE-2013-7055EG 9.8EPSS p94CRITICAL
- CVE-2013-7052EG 9.8EPSS p98CRITICAL
- CVE-2014-3445EG 9.8EPSS p92CRITICAL
- CVE-2014-5381EG 9.8EPSS p94CRITICAL
- CVE-2014-5093EG 9.8CRITICAL
- CVE-2016-4401EG 9.8CRITICAL
- CVE-2017-16714EG 9.8CRITICAL
- CVE-2017-11510EG 9.8CRITICAL
- CVE-2017-17106EG 9.8EPSS p96CRITICAL
- CVE-2017-3192EG 9.8EPSS p98CRITICAL
Frequently asked(5)
What is CVE-2026-82247?
When was CVE-2026-82247 disclosed?
Is CVE-2026-82247 actively exploited?
What is the CVSS score of CVE-2026-82247?
How do I remediate CVE-2026-82247?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82247
Is Your Infrastructure Affected by CVE-2026-82247?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.