Monthly
Terminal escape sequence injection in Ember's interactive TUI allows unauthenticated remote attackers to smuggle ANSI/OSC/CSI control bytes into an operator's terminal by embedding them in HTTP requests sent to the monitored Caddy server. Ember's ParseLogLine restores raw control bytes from Caddy's unicode-escaped JSON access log, and the render helpers fitCellLeft and fitCellRight pass them unfiltered to os.Stdout via bubbletea's View(), enabling clipboard hijacking (OSC 52), dashboard spoofing (CSI cursor/erase), and window-title manipulation (OSC 0/2). No CISA KEV listing or confirmed public exploit exists at time of analysis; the 'RCE' tag in the intelligence metadata conflicts with the advisory's explicit statement that this is not general-case RCE and should not drive incident response decisions without independent verification.
Terminal escape sequence injection in broot, the interactive Rust-based file tree navigator by Canop, allows any local user with filesystem write access to plant control characters in a filename and have them written verbatim to the terminal of any other user who browses that directory with broot. The vulnerable code path - to_string_lossy() in src/tree/tree_line.rs and src/tree_build/builder.rs - applies no control-character filtering despite an existing doc comment implying sanitization occurs. A proof of concept embedding an OSC 52 clipboard-write sequence confirmed that raw escape bytes reach the terminal unstripped; the terminal emulator then determines the actual impact, ranging from cosmetic disruption to clipboard hijacking. No public exploit identified at time of analysis beyond the reported proof of concept; the vulnerability is not listed in CISA KEV.
Terminal escape sequence injection in powerlevel10k (all versions through 1.20.17) allows any attacker who controls a package.json file on a victim's filesystem to emit arbitrary terminal control sequences on every shell prompt render when the victim navigates into the affected directory. The `prompt_package` segment in `internal/p10k.zsh` passed the `P9K_PACKAGE_VERSION` variable to the terminal without applying Zsh's `(V)` sanitization flag, meaning raw ANSI or OSC escape bytes in the version field reach the terminal emulator unfiltered. No public exploit or CISA KEV listing is identified at time of analysis; the CVSS 4.0 score of 4.8 reflects limited integrity impact and required user interaction.
Terminal escape sequence injection in Oh My Posh prior to version 29.35.1 allows an attacker who controls a Git repository or filesystem directory name to silently execute arbitrary ANSI/OSC escape sequences in a victim's terminal on every prompt render, without any user action beyond navigating to the attacker-influenced directory. The `write(s rune)` function in `src/terminal/writer.go` emitted attacker-controlled content — including Git commit subjects, author names and emails, upstream URLs, and working directory path components — verbatim to the terminal output buffer without stripping C0/C1 control characters such as ESC (0x1b), BEL (0x07), CSI, and OSC sequences. A publicly available proof-of-concept demonstrates OSC 52 clipboard overwrite and OSC 0 window title hijacking; no public exploit identified as confirmed actively exploited per CISA KEV at time of analysis.
Terminal escape sequence injection in Bash-it's barbuk theme (versions through 3.2.0) permits a local attacker to execute arbitrary OSC and CSI terminal control sequences in the context of a victim user's terminal emulator simply by placing a crafted pyproject.toml in any directory the victim navigates into. The root cause is that the barbuk theme's __python_venv_prompt function reads the requires-python field via awk without stripping control characters, then concatenates the raw value into PS1 through __prompt-command, causing injected sequences to render on every prompt refresh. No public exploit code has been identified at time of analysis and the vulnerability is not listed in the CISA KEV catalog, though the attack is low-complexity given the vendor-confirmed fix commit.
Terminal escape sequence injection in npm-check-updates through 23.0.2 enables a supply-chain attacker who controls a malicious npm package's metadata to embed arbitrary VT100/OSC control sequences in the `homepage` or `repository` URL fields of `package.json`. When developers run `ncu --format homepage` or `--format repo`, these unfiltered sequences are written directly to the terminal, allowing output overwriting via bare carriage returns, terminal title hijacking via OSC sequences, and other display manipulation on developer workstations or CI runners. No public exploit has been identified at time of analysis and no CISA KEV listing exists, but the fix PR's test suite demonstrates the exact attack pattern using OSC title-setting sequences and CR overwrites.
Terminal escape sequence injection in GitHub CLI (gh) prior to version 2.97.0 allows an attacker who controls content on GitHub - gists, pull requests, releases, codespaces, API responses, skills, or agent-task output - to embed ANSI/VT escape sequences that are rendered verbatim by the victim's terminal when they run any of the affected display commands. Impact ranges from cosmetic screen manipulation (title bar spoofing, on-screen content overwrite) to, on certain terminal emulators that interpret shell-integration or hyperlink escape sequences, arbitrary command execution in the user's shell. This issue broadens the same CWE-150 class addressed by CVE-2026-45803, which patched only the `gh run view --log` path, to the full set of content-displaying subcommands. No public exploit or KEV listing is present at time of analysis, though the injection surface is wide and the fix is confirmed in v2.97.0.
SQL injection in syslog-ng versions before 4.12 (also fixed in Premium Edition 8.2 and Store Box 7.8) allows an attacker who controls an untrusted log source to inject SQL through log data processed by the afsql SQL destination driver, because afsql_dd_run_query omits a required sanitization call. Exploitation only affects deployments that have manually configured the SQL driver, and there is no public exploit identified at time of analysis and no CISA KEV listing. The rated impact centers on integrity of the backing database and availability of the logging pipeline (CVSS 7.1).
Terminal injection in Claude HUD through version 0.0.12 allows an attacker who controls a Git branch name or working directory path to embed arbitrary ANSI escape sequences into terminal sessions via unsanitized OSC 8 hyperlink construction. When a user runs Claude HUD in an affected terminal emulator and clicks a rendered project or branch hyperlink, injected sequences—including OSC 52 clipboard writes and forged prompts—are processed by the terminal. The vulnerability has no public exploit identified at time of analysis and is not listed in CISA KEV, but the clipboard-poisoning vector carries meaningful risk for developers routinely cloning untrusted repositories.
Local code execution in Tabby terminal emulator versions before 1.0.233 occurs when dragging and dropping files containing control characters in their paths. The terminal fails to properly escape control sequences, allowing attackers to execute arbitrary commands through crafted filenames when a user drags a malicious file into the terminal window.
Terminal escape sequence injection in Ember's interactive TUI allows unauthenticated remote attackers to smuggle ANSI/OSC/CSI control bytes into an operator's terminal by embedding them in HTTP requests sent to the monitored Caddy server. Ember's ParseLogLine restores raw control bytes from Caddy's unicode-escaped JSON access log, and the render helpers fitCellLeft and fitCellRight pass them unfiltered to os.Stdout via bubbletea's View(), enabling clipboard hijacking (OSC 52), dashboard spoofing (CSI cursor/erase), and window-title manipulation (OSC 0/2). No CISA KEV listing or confirmed public exploit exists at time of analysis; the 'RCE' tag in the intelligence metadata conflicts with the advisory's explicit statement that this is not general-case RCE and should not drive incident response decisions without independent verification.
Terminal escape sequence injection in broot, the interactive Rust-based file tree navigator by Canop, allows any local user with filesystem write access to plant control characters in a filename and have them written verbatim to the terminal of any other user who browses that directory with broot. The vulnerable code path - to_string_lossy() in src/tree/tree_line.rs and src/tree_build/builder.rs - applies no control-character filtering despite an existing doc comment implying sanitization occurs. A proof of concept embedding an OSC 52 clipboard-write sequence confirmed that raw escape bytes reach the terminal unstripped; the terminal emulator then determines the actual impact, ranging from cosmetic disruption to clipboard hijacking. No public exploit identified at time of analysis beyond the reported proof of concept; the vulnerability is not listed in CISA KEV.
Terminal escape sequence injection in powerlevel10k (all versions through 1.20.17) allows any attacker who controls a package.json file on a victim's filesystem to emit arbitrary terminal control sequences on every shell prompt render when the victim navigates into the affected directory. The `prompt_package` segment in `internal/p10k.zsh` passed the `P9K_PACKAGE_VERSION` variable to the terminal without applying Zsh's `(V)` sanitization flag, meaning raw ANSI or OSC escape bytes in the version field reach the terminal emulator unfiltered. No public exploit or CISA KEV listing is identified at time of analysis; the CVSS 4.0 score of 4.8 reflects limited integrity impact and required user interaction.
Terminal escape sequence injection in Oh My Posh prior to version 29.35.1 allows an attacker who controls a Git repository or filesystem directory name to silently execute arbitrary ANSI/OSC escape sequences in a victim's terminal on every prompt render, without any user action beyond navigating to the attacker-influenced directory. The `write(s rune)` function in `src/terminal/writer.go` emitted attacker-controlled content — including Git commit subjects, author names and emails, upstream URLs, and working directory path components — verbatim to the terminal output buffer without stripping C0/C1 control characters such as ESC (0x1b), BEL (0x07), CSI, and OSC sequences. A publicly available proof-of-concept demonstrates OSC 52 clipboard overwrite and OSC 0 window title hijacking; no public exploit identified as confirmed actively exploited per CISA KEV at time of analysis.
Terminal escape sequence injection in Bash-it's barbuk theme (versions through 3.2.0) permits a local attacker to execute arbitrary OSC and CSI terminal control sequences in the context of a victim user's terminal emulator simply by placing a crafted pyproject.toml in any directory the victim navigates into. The root cause is that the barbuk theme's __python_venv_prompt function reads the requires-python field via awk without stripping control characters, then concatenates the raw value into PS1 through __prompt-command, causing injected sequences to render on every prompt refresh. No public exploit code has been identified at time of analysis and the vulnerability is not listed in the CISA KEV catalog, though the attack is low-complexity given the vendor-confirmed fix commit.
Terminal escape sequence injection in npm-check-updates through 23.0.2 enables a supply-chain attacker who controls a malicious npm package's metadata to embed arbitrary VT100/OSC control sequences in the `homepage` or `repository` URL fields of `package.json`. When developers run `ncu --format homepage` or `--format repo`, these unfiltered sequences are written directly to the terminal, allowing output overwriting via bare carriage returns, terminal title hijacking via OSC sequences, and other display manipulation on developer workstations or CI runners. No public exploit has been identified at time of analysis and no CISA KEV listing exists, but the fix PR's test suite demonstrates the exact attack pattern using OSC title-setting sequences and CR overwrites.
Terminal escape sequence injection in GitHub CLI (gh) prior to version 2.97.0 allows an attacker who controls content on GitHub - gists, pull requests, releases, codespaces, API responses, skills, or agent-task output - to embed ANSI/VT escape sequences that are rendered verbatim by the victim's terminal when they run any of the affected display commands. Impact ranges from cosmetic screen manipulation (title bar spoofing, on-screen content overwrite) to, on certain terminal emulators that interpret shell-integration or hyperlink escape sequences, arbitrary command execution in the user's shell. This issue broadens the same CWE-150 class addressed by CVE-2026-45803, which patched only the `gh run view --log` path, to the full set of content-displaying subcommands. No public exploit or KEV listing is present at time of analysis, though the injection surface is wide and the fix is confirmed in v2.97.0.
SQL injection in syslog-ng versions before 4.12 (also fixed in Premium Edition 8.2 and Store Box 7.8) allows an attacker who controls an untrusted log source to inject SQL through log data processed by the afsql SQL destination driver, because afsql_dd_run_query omits a required sanitization call. Exploitation only affects deployments that have manually configured the SQL driver, and there is no public exploit identified at time of analysis and no CISA KEV listing. The rated impact centers on integrity of the backing database and availability of the logging pipeline (CVSS 7.1).
Terminal injection in Claude HUD through version 0.0.12 allows an attacker who controls a Git branch name or working directory path to embed arbitrary ANSI escape sequences into terminal sessions via unsanitized OSC 8 hyperlink construction. When a user runs Claude HUD in an affected terminal emulator and clicks a rendered project or branch hyperlink, injected sequences—including OSC 52 clipboard writes and forged prompts—are processed by the terminal. The vulnerability has no public exploit identified at time of analysis and is not listed in CISA KEV, but the clipboard-poisoning vector carries meaningful risk for developers routinely cloning untrusted repositories.
Local code execution in Tabby terminal emulator versions before 1.0.233 occurs when dragging and dropping files containing control characters in their paths. The terminal fails to properly escape control sequences, allowing attackers to execute arbitrary commands through crafted filenames when a user drags a malicious file into the terminal window.