CVE-2026-64655

LOWPre-NVD 2.12.1—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (25th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
2.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 2.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

GitHub CLI (gh) is GitHub’s official command line tool. Prior to 2.97.0, gh attestation verify  builds the certificate Subject Alternative Name matcher from the --signer-repo and --signer-workflow  flag values without escaping regex metacharacters, so a user-supplied repository or workflow name is treated as a regular expression rather than a literal string. Because GitHub permits characters such as  .  in organization, repository, and workflow path names and  .  is a regex wildcard, an attacker can register a lookalike name (for example github/artifact.attestations-workflows) that satisfies a matcher intended for a different trusted signer (github/artifact-attestations-workflows), bypassing the intended Sigstore attestation verification. Exploitation requires the attacker to create a plausible lookalike repository and produce valid attestations from it, which could undermine supply chain verification for CI/CD pipelines or policy gates that pin trust to a specific signing workflow. This issue is fixed in version 2.97.0.

CVSS v3
2.1
EG Score
2.1LOWmedium confidence
EG Risk
25
EG Risk 25/100CISA SSVC

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
Severity21% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
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.3%
EPSS %ILE
25th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 6, 2026

Last Modified

September 10, 2026

References (3)

Vendor Advisories for CVE-2026-64655(1)

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

Affected Packages

(2 across 2 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
gh2.23.0+dfsg1-1 ... 2.46.0-4 (16 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
gh2.46.0-3, 2.46.0-4
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-64655?
CVE-2026-64655 is a low vulnerability published on August 6, 2026. GitHub CLI (gh) is GitHub’s official command line tool. Prior to 2.97.0, gh attestation verify builds the certificate Subject Alternative Name matcher from the --signer-repo and --signer-workflow flag values without escaping regex metacharacters, so a user-supplied repository or workflow name is…
When was CVE-2026-64655 disclosed?
CVE-2026-64655 was first published on August 6, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64655 actively exploited?
CVE-2026-64655 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64655?
CVE-2026-64655 has a CVSS base score of 2.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-64655?
A fix for CVE-2026-64655 is available — its CVE record says: "This issue is fixed in version 2.97.0." The vendor advisories EchelonGraph has for CVE-2026-64655 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-64655

Explore →

Is Your Infrastructure Affected by CVE-2026-64655?

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

Book a Demo →Browse All CVEs