No access to your tenant or devices. Every item links to its source. What this means
go-gh is a collection of Go modules to make authoring GitHub CLI extensions easier. A security vulnerability has been identified in versions prior to 2.12.1 where an attacker-controlled GitHub Enterprise Server could result in executing arbitrary commands on a user's machine by replacing HTTP URLs provided by GitHub with local file paths for browsing. In `2.12.1`, `Browser.Browse()` has been enhanced to allow and disallow a variety of scenarios to avoid opening or executing files on the filesystem without unduly impacting HTTP URLs. No known workarounds are available other than upgrading.
Read the publisher's advisorygo-gh is a collection of Go modules to make authoring GitHub CLI extensions easier. A security vulnerability has been identified in versions prior to 2.12.1 where an attacker-controlled GitHub Enterprise Server could result in executing arbitrary commands on a user's machine by replacing HTTP URLs provided by GitHub with local file paths for browsing. In `2.12.1`, `Browser.Browse()` has been enhanced to allow and disallow a variety of scenarios to avoid opening or executing files on the filesystem without unduly impacting HTTP URLs. No known workarounds are available other than upgrading.
Read the publisher's advisorygo-gh is a collection of Go modules to make authoring GitHub CLI extensions easier. A security vulnerability has been identified in versions prior to 2.12.1 where an attacker-controlled GitHub Enterprise Server could result in executing arbitrary commands on a user's machine by replacing HTTP URLs provided by GitHub with local file paths for browsing. In `2.12.1`, `Browser.Browse()` has been enhanced to allow and disallow a variety of scenarios to avoid opening or executing files on the filesystem without unduly impacting HTTP URLs. No known workarounds are available other than upgrading.
Read the publisher's advisory### Summary A security vulnerability has been identified in `go-gh` where an attacker-controlled GitHub Enterprise Server could result in executing arbitrary commands on a user's machine by replacing HTTP URLs provided by GitHub with local file paths for browsing. ### Details The GitHub CLI and CLI extensions allow users to transition from their terminal for a variety of use cases through the [`Browser` capability in `github.com/cli/go-gh/v2/pkg/browser`](https://github.com/cli/go-gh/blob/61bf393cf4aeea6d00a6251390f5f67f5b67e727/pkg/browser/browser.go): - Using the `-w, --web` flag, GitHub CLI users can view GitHub repositories, issues, pull requests, and more using their web browser - Using the `gh codespace` command set, GitHub CLI users can transition to Visual Studio Code to work with GitHub Codespaces This is done by using URLs provided through API responses from authenticated GitHub hosts when users execute `gh` commands. Prior to `2.12.1`, `Browser.Browse()` would attempt to open the provided URL using a variety of OS-specific approaches regardless of the scheme. An attacker-controlled GitHub Enterprise Server could modify API responses to use a specially tailored local executable path instead of HTTP URLs to resources. This could allow the attacker to execute arbitrary executables on the user's machine. In `2.12.1`, `Browser.Browse()` has been enhanced to allow and disallow a variety of scenarios to avoid opening or executing files on the filesystem without unduly impacting HTTP URLs: 1. URLs with `http://`, `https://`, `vscode://`, `vscode-insiders://` protocols are supported 1. URLs with `file://` protocol are unsupported 1. URLs matching files or directories on the filesystem are unsupported 1. URLs matching executables in the user's path are unsupported URLs without protocols will be browsable if none of these other conditions apply. As we have more information about use cases, maintainers can expand these capabilities for an improved user experience that allows configuring allowed URL schemes and/or prompt the user for an unexpected user case and confirming whether to continue. ### Impact Successful exploitation could cause users of the attacker-controlled GitHub Enterprise Server to execute arbitrary commands. ### Remediation and Mitigation 1. Upgrade `go-gh` to `2.12.1`
Read the publisher's advisoryGitHub CLI and extensions can execute arbitrary commands on compromised GitHub Enterprise Server in github.com/cli/go-gh
Read the publisher's advisoryVendor product
Shown as published. These rules are not interpreted as NuGet package version ranges.
{
"vendor": "cli",
"product": "go-gh",
"versions": [
{
"version": "< 2.12.1",
"status": "affected"
}
]
}Original source record · Cite this exact observation · Complete original publisher JSON
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
datePublished: May 30, 2025, 6:45:59 PM
dateUpdated: May 30, 2025, 8:38:51 PM
openSUSE-SU-2025:15225-1: govulncheck-vulndb-0.0.20250612T141001-1.1 on GA media
CVE-2020-36846 · CVE-2022-31022 · CVE-2023-42818 · CVE-2025-0913 · CVE-2025-1792 · CVE-2025-22874 · CVE-2025-25207 · CVE-2025-25208 · CVE-2025-2571 · CVE-2025-29785 · CVE-2025-3230 · CVE-2025-3260 · CVE-2025-3454 · CVE-2025-3611 · CVE-2025-3913 · CVE-2025-4128 · CVE-2025-4573 · CVE-2025-4673 · CVE-2025-47950 · CVE-2025-48494 · CVE-2025-48495 · CVE-2025-48710 · CVE-2025-48865 · CVE-2025-48938 · CVE-2025-48948 · CVE-2025-48949 · CVE-2025-49011 · CVE-2025-49136 · CVE-2025-49140
msrc_CVE-2025-48938: Prevent GitHub CLI and extensions from executing arbitrary commands from compromised GitHub Enterprise Server
CVE-2025-48938
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-501
published: 2025-05-30T19:15:29.980
lastModified: 2026-08-17T12:05:03.540
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON
Go
SEMVER · introduced 0 → fixed 2.12.1
Original source record · Cite this exact observation · Complete original publisher JSON
Go
SEMVER · introduced 0 → fixed 2.12.1
Original source record · Cite this exact observation · Complete original publisher JSON