CVE-2026-82247

HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
Trending — 4 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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).

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 computed
Severity75% × 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, 2026
Patch available. Sources: github.
generic

gitoxide 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-parsing
github Patch Available

gix-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-gpp8

Vendor 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.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 20:50 UTCGHSA enrichment
  3. 2026-08-29 07:55 UTCGHSA enrichment
  4. 2026-08-28 18:57 UTCGHSA enrichment
  5. 2026-08-28 16:36 UTCEG score recompute
  6. 2026-08-28 16:36 UTCGHSA enrichment
  7. 2026-08-28 15:37 UTCEG score recompute
  8. 2026-08-28 15:37 UTCGHSA enrichment
  9. 2026-08-28 12:22 UTCEG score recompute
  10. 2026-08-28 11:23 UTCEG score recompute
  11. 2026-08-28 11:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-82247?
CVE-2026-82247 is a high vulnerability published on August 28, 2026. 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 (canreuseidentity) compares the wrong host and fails open.…
When was CVE-2026-82247 disclosed?
CVE-2026-82247 was first published in the National Vulnerability Database on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82247 actively exploited?
CVE-2026-82247 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.1% of all scored CVEs.
What is the CVSS score of CVE-2026-82247?
CVE-2026-82247 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-82247?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82247, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-82247?

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