CVE-2026-82250

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

gitoxide gix-packetline versions before 0.21.5 contain a panic vulnerability in the TextRef implementation that occurs when processing side-band packet lines with empty payloads. A malicious Git server can send a crafted side-band packet to trigger an index out of bounds panic, aborting the client process during fetch operations without authentication.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
44
EG Risk 44/100

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 (value × EchelonGraph’s weight)
Severity65% × 45%
The EG Score, 6.5 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 28, 2026

Last Modified

August 28, 2026

Advisory Details (2)

Auto-updated Aug 28, 2026
Patch available. Sources: github.
Web page

gitoxide gix-packetline before 0.21.5 Denial of Service | Advisories | VulnCheck

https://www.vulncheck.com/advisories/gitoxide-gix-packetline-before-0.21.5-denial-of-service
GitHub advisoryMentions a patch (unverified)

gix-packetline: reachable panic on empty side-band packet (pre-auth network DoS) · Advisory · GitoxideLabs/gitoxide · GitHub

https://github.com/GitoxideLabs/gitoxide/security/advisories/GHSA-2vh6-hw4j-32ww

Vendor Advisories for CVE-2026-82250(2)

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

Affected Packages

(3 across 3 ecosystems)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
gix-packetline—
  • every version up to 0.21.5: fixed in 0.21.5
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rust-gix-packetline0.18.2-1 ... 0.22.2-1 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rust-gix-packetline0.18.2-1, 0.18.2-2, 0.19.1-1, 0.21.3-1
  • every version up to 0.22.0-1: fixed in 0.22.0-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 109× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 165 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 65 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-82250?
CVE-2026-82250 is a medium-severity vulnerability; its CVE record was published on August 28, 2026. gitoxide gix-packetline versions before 0.21.5 contain a panic vulnerability in the TextRef implementation that occurs when processing side-band packet lines with empty payloads. A malicious Git server can send a crafted side-band packet to trigger an index out of bounds panic, aborting the client…
When was CVE-2026-82250 made public?
CVE-2026-82250 was made public on June 16, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 28, 2026. EchelonGraph's copy of the record carries a last-modified date of August 28, 2026; the record at its source may have been updated since.
Is CVE-2026-82250 actively exploited?
CVE-2026-82250 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82250?
CVE-2026-82250 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82250?
A fix for CVE-2026-82250 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-82250 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-82250

Explore →

Is Your Infrastructure Affected by CVE-2026-82250?

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