Cli
Monthly
Code injection in @tinacms/cli versions up to and including 2.7.0 lets a crafted Git branch name break out of the string literal used for the generated client's API URL and execute arbitrary JavaScript when that generated client module is imported during a preview or CI build. The flaw, rated CVSS 8.2 (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N), requires the build to actually run codegen and import the generated client, and requires an attacker able to influence the branch value read from VERCEL_GIT_COMMIT_REF, GITHUB_BRANCH, or HEAD, so exploitation is gated by meaningful preconditions rather than being trivially remote. Injected code runs with build-process privileges, allowing theft of environment credentials, tampering with deployment artifacts, and outbound network requests; no public exploit tooling identified at time of analysis, though the vendor advisory documents a working proof-of-concept branch-name payload, and there is no evidence of active exploitation (no CISA KEV listing) or EPSS data provided.
Insecure file permissions in Quasar's development TLS certificate utility (@quasar/ssl-certificate before 2.1.0, shipped via @quasar/cli before 5.0.4 and @quasar/app-vite before 3.3.0) let another local, unprivileged user on the same host read the cached combined private key and certificate PEM and then impersonate the developer's localhost HTTPS endpoint in any environment that trusts that certificate. The flaw is a local, low-privilege information-disclosure and impersonation issue (CWE-732) rather than a remotely exploitable critical condition: it only matters on multi-user, non-Windows machines (shared workstations, CI/build servers, container hosts) where at least one other local account exists and the generated dev certificate is actually trusted. Additional weaknesses compound the exposure - the generated certificate was CA-capable, carried unnecessary key usages, and encoded the IPv6 loopback address as a DNS SAN - but the practical impact remains bounded by the local-attacker prerequisite; no public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV) for this CVE. Vendor-released fixes are available in @quasar/ssl-certificate 2.1.0, @quasar/cli 5.0.4 and @quasar/app-vite 3.3.0.
Path traversal in Entire CLI 0.7.6 and earlier lets a collaborator who can push to the shared `entire/checkpoints/v1` branch overwrite arbitrary files on another user's machine: when the victim runs `entire session resume` or `entire checkpoint rewind`, a crafted SessionID in checkpoint metadata is used to build restore filesystem paths without validation, so attacker-controlled transcript data is written outside the expected session directory. Both the push access to the checkpoints branch and the victim's explicit invocation of resume/rewind are required, which keeps this a precondition-heavy, supply-chain-style issue rather than a drive-by exploit; no public exploit code or confirmed active exploitation has been identified at time of analysis, and notification is tracked as a moderate-priority this-month item. Successful abuse yields high integrity impact on other systems' components (scope change) and limited availability impact.
Capgo CLI's Android onboarding flow silently grants the Google Play service account it generates the account-wide Play Console permission CAN_MANAGE_DRAFT_APPS_GLOBAL, so anyone who obtains the resulting PLAY_CONFIG_JSON key can create, edit, and delete draft apps across the entire Google Play developer account rather than only the single confirmed package the UI claims was shared. The issue affects the npm package @capgo/cli through 7.98.2 and is present in default onboarding, but exploitation is entirely conditional on key exposure - a leaked key in a public repository, CI log, or compromised secrets store - and impact is confined to draft apps with no effect on already-published releases and no confidentiality impact. No vendor-released patch was identified at time of analysis, and no public exploit code has been identified.
Command execution via URI injection in GitHub CLI's `gh codespace jupyter` subcommand (versions 2.10.0-2.95.0) allows an attacker who controls a Codespace to redirect a connecting developer's VS Code instance into executing arbitrary protocol handler actions. The CLI passes a JupyterLab URL sourced from a process inside the Codespace directly to the OS without validating that the URL is a loopback HTTP or HTTPS address, enabling substitution with a crafted `vscode://` or `vscode-insiders://` URI. No public exploit has been identified at time of analysis and this CVE is not listed in CISA's Known Exploited Vulnerabilities catalog, but the scope-change characteristic (S:C) means local VS Code extension execution is a realistic downstream impact.
Symlink-following vulnerabilities in Capgo CLI before version 12.128.2 (npm @capgo/cli < 7.84.6) allow an attacker who controls a repository to overwrite arbitrary files on a developer's machine and expose sensitive signing credentials when the developer runs CLI login or build credential operations inside that repository. Three distinct issues are present: unsafe writeFileSync on .capgo and .capgo-credentials.json without symlink validation, and global credential files written with world-readable 664 permissions instead of the required 0600. A proof-of-concept demonstrating the .capgo clobber is publicly documented in the GitHub Security Advisory GHSA-8mpm-q7mh-8fvh. No CISA KEV listing exists at time of analysis, but exploitability is straightforward given the PoC and low attack complexity.
Terminal escape sequence injection in GitHub CLI 1.6.0 through 2.91.x allows authenticated attackers with pull request creation rights to inject malicious terminal control sequences into Actions workflow logs. When victims execute 'gh run view --log' or 'gh run view --log-failed' to inspect workflow runs, unsanitized escape sequences replay in their terminal, enabling window title manipulation, on-screen content alteration, or arbitrary command execution in vulnerable emulators like GNU screen. The attack requires low complexity and user interaction (victim must view logs), with impact limited to terminal integrity. CVSS score of 3.5 reflects low-severity integrity impact, though real-world risk varies significantly by terminal emulator capabilities. No active exploitation confirmed at time of analysis.
go-gh is a collection of Go modules to make authoring GitHub CLI extensions easier. Rated low severity (CVSS 2.6), this vulnerability is remotely exploitable, low attack complexity.
go-gh is a Go module for interacting with the `gh` utility and the GitHub API from the command line. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
The GitHub CLI version 2.6.1 and earlier are vulnerable to remote code execution through a malicious codespace SSH server when using `gh codespace ssh` or `gh codespace logs` commands. Rated critical severity (CVSS 9.6), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
Snyk CLI before 1.996.0 allows arbitrary command execution, affecting Snyk IDE plugins and the snyk npm package. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. Public exploit code available.
The CLI in Cisco IOS XR allows remote authenticated users to obtain sensitive information via unspecified commands, aka Bug IDs CSCuq42336, CSCuq76853, CSCuq76873, and CSCuq45383. Rated medium severity (CVSS 4.0), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Code injection in @tinacms/cli versions up to and including 2.7.0 lets a crafted Git branch name break out of the string literal used for the generated client's API URL and execute arbitrary JavaScript when that generated client module is imported during a preview or CI build. The flaw, rated CVSS 8.2 (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N), requires the build to actually run codegen and import the generated client, and requires an attacker able to influence the branch value read from VERCEL_GIT_COMMIT_REF, GITHUB_BRANCH, or HEAD, so exploitation is gated by meaningful preconditions rather than being trivially remote. Injected code runs with build-process privileges, allowing theft of environment credentials, tampering with deployment artifacts, and outbound network requests; no public exploit tooling identified at time of analysis, though the vendor advisory documents a working proof-of-concept branch-name payload, and there is no evidence of active exploitation (no CISA KEV listing) or EPSS data provided.
Insecure file permissions in Quasar's development TLS certificate utility (@quasar/ssl-certificate before 2.1.0, shipped via @quasar/cli before 5.0.4 and @quasar/app-vite before 3.3.0) let another local, unprivileged user on the same host read the cached combined private key and certificate PEM and then impersonate the developer's localhost HTTPS endpoint in any environment that trusts that certificate. The flaw is a local, low-privilege information-disclosure and impersonation issue (CWE-732) rather than a remotely exploitable critical condition: it only matters on multi-user, non-Windows machines (shared workstations, CI/build servers, container hosts) where at least one other local account exists and the generated dev certificate is actually trusted. Additional weaknesses compound the exposure - the generated certificate was CA-capable, carried unnecessary key usages, and encoded the IPv6 loopback address as a DNS SAN - but the practical impact remains bounded by the local-attacker prerequisite; no public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV) for this CVE. Vendor-released fixes are available in @quasar/ssl-certificate 2.1.0, @quasar/cli 5.0.4 and @quasar/app-vite 3.3.0.
Path traversal in Entire CLI 0.7.6 and earlier lets a collaborator who can push to the shared `entire/checkpoints/v1` branch overwrite arbitrary files on another user's machine: when the victim runs `entire session resume` or `entire checkpoint rewind`, a crafted SessionID in checkpoint metadata is used to build restore filesystem paths without validation, so attacker-controlled transcript data is written outside the expected session directory. Both the push access to the checkpoints branch and the victim's explicit invocation of resume/rewind are required, which keeps this a precondition-heavy, supply-chain-style issue rather than a drive-by exploit; no public exploit code or confirmed active exploitation has been identified at time of analysis, and notification is tracked as a moderate-priority this-month item. Successful abuse yields high integrity impact on other systems' components (scope change) and limited availability impact.
Capgo CLI's Android onboarding flow silently grants the Google Play service account it generates the account-wide Play Console permission CAN_MANAGE_DRAFT_APPS_GLOBAL, so anyone who obtains the resulting PLAY_CONFIG_JSON key can create, edit, and delete draft apps across the entire Google Play developer account rather than only the single confirmed package the UI claims was shared. The issue affects the npm package @capgo/cli through 7.98.2 and is present in default onboarding, but exploitation is entirely conditional on key exposure - a leaked key in a public repository, CI log, or compromised secrets store - and impact is confined to draft apps with no effect on already-published releases and no confidentiality impact. No vendor-released patch was identified at time of analysis, and no public exploit code has been identified.
Command execution via URI injection in GitHub CLI's `gh codespace jupyter` subcommand (versions 2.10.0-2.95.0) allows an attacker who controls a Codespace to redirect a connecting developer's VS Code instance into executing arbitrary protocol handler actions. The CLI passes a JupyterLab URL sourced from a process inside the Codespace directly to the OS without validating that the URL is a loopback HTTP or HTTPS address, enabling substitution with a crafted `vscode://` or `vscode-insiders://` URI. No public exploit has been identified at time of analysis and this CVE is not listed in CISA's Known Exploited Vulnerabilities catalog, but the scope-change characteristic (S:C) means local VS Code extension execution is a realistic downstream impact.
Symlink-following vulnerabilities in Capgo CLI before version 12.128.2 (npm @capgo/cli < 7.84.6) allow an attacker who controls a repository to overwrite arbitrary files on a developer's machine and expose sensitive signing credentials when the developer runs CLI login or build credential operations inside that repository. Three distinct issues are present: unsafe writeFileSync on .capgo and .capgo-credentials.json without symlink validation, and global credential files written with world-readable 664 permissions instead of the required 0600. A proof-of-concept demonstrating the .capgo clobber is publicly documented in the GitHub Security Advisory GHSA-8mpm-q7mh-8fvh. No CISA KEV listing exists at time of analysis, but exploitability is straightforward given the PoC and low attack complexity.
Terminal escape sequence injection in GitHub CLI 1.6.0 through 2.91.x allows authenticated attackers with pull request creation rights to inject malicious terminal control sequences into Actions workflow logs. When victims execute 'gh run view --log' or 'gh run view --log-failed' to inspect workflow runs, unsanitized escape sequences replay in their terminal, enabling window title manipulation, on-screen content alteration, or arbitrary command execution in vulnerable emulators like GNU screen. The attack requires low complexity and user interaction (victim must view logs), with impact limited to terminal integrity. CVSS score of 3.5 reflects low-severity integrity impact, though real-world risk varies significantly by terminal emulator capabilities. No active exploitation confirmed at time of analysis.
go-gh is a collection of Go modules to make authoring GitHub CLI extensions easier. Rated low severity (CVSS 2.6), this vulnerability is remotely exploitable, low attack complexity.
go-gh is a Go module for interacting with the `gh` utility and the GitHub API from the command line. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
The GitHub CLI version 2.6.1 and earlier are vulnerable to remote code execution through a malicious codespace SSH server when using `gh codespace ssh` or `gh codespace logs` commands. Rated critical severity (CVSS 9.6), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
Snyk CLI before 1.996.0 allows arbitrary command execution, affecting Snyk IDE plugins and the snyk npm package. Rated high severity (CVSS 7.8), this vulnerability is low attack complexity. Public exploit code available.
The CLI in Cisco IOS XR allows remote authenticated users to obtain sensitive information via unspecified commands, aka Bug IDs CSCuq42336, CSCuq76853, CSCuq76873, and CSCuq45383. Rated medium severity (CVSS 4.0), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.