These pages are published after PatchSiren validates generated defensive summaries against stored public CVE and source evidence.
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-toke [truncated]
CVE-2026-59831 is a medium-severity vulnerability in GitHub CLI (gh) versions 2.10.0 through 2.95.0. The issue allows command execution when connecting to a malicious Codespace with 'gh codespace jupyter' due to improper validation of JupyterLab URLs supplied by a process inside the Codespace. This could potentially allow a crafted vscode:// or vscode-insiders:// URL to be handed to VS Code. The vulnerabi [truncated]
GitHub CLI (gh) versions prior to 2.93.0 incorrectly transmit authorization tokens to external hosts during attestation and release verification operations. The vulnerability stems from flawed host normalization logic in the CLI's shared HTTP client authentication layer, which collapses any *.github.com subdomain to github.com. This causes requests to tuf-repo.github.com—a GitHub Pages site hosting TUF me [truncated]
CVE-2026-45803 is a low-severity GitHub CLI issue in which workflow log content can be rendered to a terminal without sanitizing control sequences. If an attacker can influence Actions log output, viewing a run with gh run view --log or gh run view --log-failed can cause terminal escape sequence injection in the user’s session. The issue is fixed in GitHub CLI 2.92.0.