CVE-2026-26514

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-03-04. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
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: None knownExposed: 0

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

An Argument Injection vulnerability exists in bird-lg-go before commit 6187a4e. The traceroute module uses shlex.Split to parse user input without validation, allowing remote attackers to inject arbitrary flags (e.g., -w, -q) via the q parameter. This can be exploited to cause a Denial of Service (DoS) by exhausting system resources.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

March 4, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 2, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

[安全问题？] Traceroute 模块存在参数注入漏洞，可能会导致远程拒绝服务 (DoS) · Issue #136 · xddxdd/bird-lg-go · GitHub

https://github.com/xddxdd/bird-lg-go/issues/136
github_commit

commit 6187a4e3afce (xddxdd/bird-lg-go)

Fix landed in xddxdd/bird-lg-go commit 6187a4e3afce — awaiting tagged release

https://github.com/xddxdd/bird-lg-go/commit/6187a4e3afce6d8c29568f8c72ca497d1f5a2b56

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 28× 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-09-19 12:32 UTCOSV refresh
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-17 19:30 UTCEPSS rescore
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-12 15:01 UTCEPSS rescore
  9. 2026-09-11 14:52 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-04 05:06 UTCEPSS rescore
  16. 2026-09-02 14:11 UTCEPSS rescore
  17. 2026-09-01 13:53 UTCEPSS rescore
  18. 2026-09-01 04:39 UTCEPSS rescore
  19. 2026-08-31 16:04 UTCOSV refresh
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:48 UTCEPSS rescore
Show 49 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 02:14 UTCEPSS rescore
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-14 20:57 UTCGHSA enrichment
  11. 2026-08-14 08:36 UTCEG score recompute
  12. 2026-08-14 08:36 UTCGHSA enrichment
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 00:22 UTCEG score recompute
  15. 2026-08-13 00:22 UTCGHSA enrichment
  16. 2026-08-12 13:50 UTCEPSS rescore
  17. 2026-08-11 23:18 UTCEG score recompute
  18. 2026-08-11 23:17 UTCGHSA enrichment
  19. 2026-08-11 13:42 UTCEPSS rescore
  20. 2026-08-11 05:51 UTCEG score recompute
  21. 2026-08-11 05:51 UTCGHSA enrichment
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-10 07:57 UTCGHSA enrichment
  24. 2026-08-09 19:38 UTCEG score recompute
  25. 2026-08-09 19:38 UTCGHSA enrichment
  26. 2026-08-09 13:46 UTCEPSS rescore
  27. 2026-08-09 08:14 UTCEG score recompute
  28. 2026-08-09 08:14 UTCGHSA enrichment
  29. 2026-08-08 16:37 UTCEPSS rescore
  30. 2026-08-08 07:31 UTCGHSA enrichment
  31. 2026-08-07 20:06 UTCEG score recompute
  32. 2026-08-07 20:06 UTCGHSA enrichment
  33. 2026-08-06 13:46 UTCEPSS rescore
  34. 2026-08-06 02:42 UTCEG score recompute
  35. 2026-08-06 02:42 UTCGHSA enrichment
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-04 15:10 UTCEPSS rescore
  38. 2026-08-04 02:43 UTCEG score recompute
  39. 2026-08-04 02:42 UTCGHSA enrichment
  40. 2026-08-03 10:36 UTCEPSS rescore
  41. 2026-08-02 19:00 UTCEG score recompute
  42. 2026-08-02 19:00 UTCGHSA enrichment
  43. 2026-08-02 02:26 UTCEPSS rescore
  44. 2026-08-01 04:16 UTCEPSS rescore
  45. 2026-07-30 16:27 UTCEPSS rescore
  46. 2026-07-30 01:30 UTCEPSS rescore
  47. 2026-07-28 15:36 UTCEPSS rescore
  48. 2026-07-27 13:53 UTCEG score recompute
  49. 2026-07-27 13:53 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-26514?
CVE-2026-26514 is a high vulnerability published on March 4, 2026. An Argument Injection vulnerability exists in bird-lg-go before commit 6187a4e. The traceroute module uses shlex.Split to parse user input without validation, allowing remote attackers to inject arbitrary flags (e.g., -w, -q) via the q parameter. This can be exploited to cause a Denial of Service…
When was CVE-2026-26514 disclosed?
CVE-2026-26514 was first published in the National Vulnerability Database on March 4, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-26514 actively exploited?
CVE-2026-26514 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 67.2% of all scored CVEs.
What is the CVSS score of CVE-2026-26514?
CVE-2026-26514 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-26514?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-26514, 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-26514

Explore →

Is Your Infrastructure Affected by CVE-2026-26514?

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

Start Free Scan →Browse All CVEs