ubuntu-cve-2026-64652
Vulnerability from osv_ubuntu
GitHub CLI (gh) is GitHub's official command line tool. Prior to version 2.97.0, gh auth status masked only the characters after the last underscore in certain fine-grained personal access tokens and GitHub App tokens. As a result, part of an affected token could appear in terminal or CI output that is captured or shared. Authenticated users are affected if they ran gh auth status (without the --show-token flag) with a token type whose format contains an underscore after the prefix. This includes fine-grained personal access tokens (github_pat_) and GitHub App installation and user access tokens (ghs_, ghu_; for example, ghs_), as well as the Actions GITHUB_TOKEN. Classic tokens such as gho and ghp_* have an underscore-free body and are not affected. This issue is fixed in version 2.97.0.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "gh",
"binary_version": "2.4.0+dfsg1-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "gh",
"purl": "pkg:deb/ubuntu/gh@2.4.0+dfsg1-2?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.4.0+dfsg1-1",
"2.4.0+dfsg1-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "gh",
"binary_version": "2.45.0-1ubuntu0.3+esm3"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:24.04:LTS",
"name": "gh",
"purl": "pkg:deb/ubuntu/gh@2.45.0-1ubuntu0.3+esm3?arch=source\u0026distro=esm-apps/noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.27.0+dfsg1-1build1",
"2.30.0-2",
"2.35.0-1",
"2.40.1+dfsg1-1",
"2.42.1-1",
"2.43.1-1",
"2.44.1-1",
"2.44.1-2",
"2.45.0-1",
"2.45.0-1build1",
"2.45.0-1ubuntu0.1",
"2.45.0-1ubuntu0.2",
"2.45.0-1ubuntu0.2+esm1",
"2.45.0-1ubuntu0.2+esm2",
"2.45.0-1ubuntu0.3",
"2.45.0-1ubuntu0.3+esm1",
"2.45.0-1ubuntu0.3+esm2",
"2.45.0-1ubuntu0.3+esm3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "gh",
"binary_version": "2.46.0-4ubuntu0.26.04.1~esm1"
}
]
},
"package": {
"ecosystem": "Ubuntu:Pro:26.04:LTS",
"name": "gh",
"purl": "pkg:deb/ubuntu/gh@2.46.0-4ubuntu0.26.04.1~esm1?arch=source\u0026distro=esm-apps/resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.46.0-3",
"2.46.0-4",
"2.46.0-4ubuntu0.26.04.1~esm1"
]
}
],
"aliases": [],
"details": "GitHub CLI (gh) is GitHub\u0027s official command line tool. Prior to version 2.97.0, gh auth status masked only the characters after the last underscore in certain fine-grained personal access tokens and GitHub App tokens. As a result, part of an affected token could appear in terminal or CI output that is captured or shared. Authenticated users are affected if they ran gh auth status (without the --show-token flag) with a token type whose format contains an underscore after the prefix. This includes fine-grained personal access tokens (github_pat_*) and GitHub App installation and user access tokens (ghs_*, ghu_*; for example, ghs_\u003cAPPID\u003e_\u003cJWT\u003e), as well as the Actions GITHUB_TOKEN. Classic tokens such as gho_* and ghp_* have an underscore-free body and are not affected. This issue is fixed in version 2.97.0.",
"id": "UBUNTU-CVE-2026-64652",
"modified": "2026-08-07T00:00:00Z",
"published": "2026-08-07T00:00:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-64652"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-64652"
},
{
"type": "REPORT",
"url": "https://github.com/cli/cli/commit/3f6a16a9f8c7fe9676aa8d8f47b399310dd231c3"
},
{
"type": "REPORT",
"url": "https://github.com/cli/cli/releases/tag/v2.97.0"
},
{
"type": "REPORT",
"url": "https://github.com/cli/cli/security/advisories/GHSA-cg6r-mpgc-h9mm"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-64652"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.