Prevent GitHub CLI and extensions from executing arbitrary commands from compromised GitHub Enterprise Server

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2025-48938: 0.56% estimated exploitation activity in the next 30 days; percentile 46.89 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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: - 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…

Published by the source

30 May 2025, 15:30 UTC

Last modified by the source

5 Mar 2026, 07:57 UTC

Source last checked

26 Oct 2026, 15:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g9f5-x53j-h563

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-48938

Advisory: Prevent GitHub CLI and extensions from executing arbitrary commands from compromised GitHub Enterprise Server
IDs: CVE-2025-48938, GHSA-g9f5-x53j-h563
Record: https://patchnext.com/advisories/cve-2025-48938 (revision 1, source checked 26 Oct 2026, 15:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/cli/go-gh/v2 2.12.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cli/go-gh/v2: affected < 2.12.1; fixed in 2.12.1

## Suggested inspection (read-only)
- Go github.com/cli/go-gh/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/cli/go-gh/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-g9f5-x53j-h563 (GitHub-reviewed advisory GHSA-g9f5-x53j-h563 lists affected ranges: Go github.com/cli/go-gh/v2 >=0 <2.12.1)

Commands are suggestions: review each one before running it.