Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report

Your agent Now with CVE context

Find published vulnerabilities, affected versions, and available fixes.
Bring the source evidence into your coding agent to investigate what affects your project.

MoxsoSponsored by MoxsoBuild security habits with adaptive training and phishing simulations.Opens in a new tab
ORIGINAL EVIDENCE. READY FOR YOUR WORKFLOW.CVE / OSV / CISA KEV

Find vulnerabilities that affect you.

Explore advisories by severity, ecosystem, and known exploitation. Take the evidence into your next agent session.

Recent security developments
Severity
Clear filters
16 matching advisories · 16 shown
Explore packages Subscribe to these results
Follow substantive record changes →
SEVERITYVULNERABILITY / AFFECTED PACKAGESPUBLISHED
low2.3
CVE-2026-125125

compose-lint: A symlink in a pull request can issue workflow commands through the compose-lint Action's SARIF-directory error message

compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. From version 0.30.0 until 0.32.0, the compose-lint GitHub Action prints the resolved directory from a failed sarif-file subdirectory creation without effective command suppression. Version 0.30.0 has no stop-commands window, while version 0.31.0 prints this error outside its stop-commands window. A pull request can place a committed symlink on that path to a directory whose name contains a newline followed by a workflow command, causing the SARIF-directory error to issue commands in the job log. Only the Action with sarif-file pointing into a subdirectory is affected; a workspace-root SARIF file, the compose-lint package, the pre-commit hook, and the Docker image do not expose this message. This issue is fixed in version 0.32.0.

No structured fix or guidance is available here. Check the latest publisher advisory.

Exploitation not established

tmatens · compose-lint
low2.3
CVE-2026-125124

compose-lint: Text in a pull request can reach Azure Pipelines as logging commands through compose-lint 0.31.0's output

compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. In version 0.31.0, compose-lint does not neutralize the Azure Pipelines ##vso[ logging-command opener on any output path. A pull request can place that opener in a Compose value or file name, allowing output from the package, pre-commit hook, or Docker image to issue logging commands when printed to an Azure Pipelines job log. The maintainer did not reproduce the behavior on an Azure Pipelines agent. The GitHub Action is not affected because it runs only on GitHub Actions, and releases before 0.31.0 are outside this advisory because they did not claim Azure Pipelines coverage. This issue is fixed in version 0.32.0.

No structured fix or guidance is available here. Check the latest publisher advisory.

Exploitation not established

tmatens · compose-lint
low2.3
CVE-2026-125123Package fixes recorded

compose-lint: File paths embedded in pull requests can inject CI workflow commands through command-line error messages

0.31.0 fixed GHSA-6f4g-xm8v-pgv6, where text from a Compose file became GitHub Actions workflow commands in compose-lint's output. The fix escapes the command openers in compose-lint's own output, but not in the argument parser's error messages. When a repository path reaches compose-lint's arguments without a -- before it, the argument parser prints it raw in its error message. That includes a carriage return, which the runner treats as a line break, so a command can also start a new line there.

Recorded fixes — compose-lint: 0.32.0. Check your release branch.

Exploitation not established

PyPI / compose-lint
low2.3
CVE-2026-125122Package fixes recorded

compose-lint: Text in a pull request can issue CI workflow commands through JSON and SARIF output on stdout

0.31.0 fixed GHSA-6f4g-xm8v-pgv6, where text from a Compose file became GitHub Actions workflow commands in compose-lint's output. --format json and --format sarif output never passed through that fix, so ##[ inside a service name or other value reaches the log intact when the output is printed to stdout rather than written to a file. The runner acts on ##[ in the middle of a line, so the JSON layout does not prevent it.

Recorded fixes — compose-lint: 0.32.0. Check your release branch.

Exploitation not established

PyPI / compose-lint
medium5.3
CVE-2026-125121Package fixes recorded

compose-lint: Text in a pull request can still issue CI workflow commands through compose-lint 0.31.0's output

0.31.0 fixed GHSA-6f4g-xm8v-pgv6, where text from a Compose file became GitHub Actions workflow commands in compose-lint's output. The fix escapes the command openers in everything compose-lint prints, and the 0.31.0 changelog says the report "escapes both openers (also covering Azure Pipelines)". Five paths were left open:

Recorded fixes — compose-lint: 0.32.0. Check your release branch.

Exploitation not established

PyPI / compose-lint
medium4.8
CVE-2026-124992

nushell Data Conversion ser.rs escape_bytes control sequence

A vulnerability was identified in nushell up to 0.116.1. Impacted is the function escape_bytes of the file crates/nu-json/src/ser.rs of the component Data Conversion Handler. The manipulation leads to improper neutralization of escape, meta, or control sequences. The attack must be carried out locally. The pull request to fix this issue awaits acceptance.

No structured fix or guidance is available here. Check the latest publisher advisory.

Exploitation not established

n/a · nushell
medium5.3
CVE-2026-123369Package fixes recorded

compose-lint: Compose file text can issue GitHub Actions workflow commands through the compose-lint Action

The GitHub Actions runner treats certain text in a step's output as commands. The legacy form, ##[command], is recognized anywhere in a line. compose-lint's text report prints service names, environment keys and lines of the Compose file, and it does not neutralize ##[. Inside the compose-lint Action, a Compose file from a pull request can therefore:

Recorded fixes — tmatens/compose-lint: 0.31.0 or a6a7a76736de1c72abfa96c41ff8af556ffdc55f; compose-lint: 0.31.0. Check your release branch.

Exploitation not established

GitHub Actions / tmatens/compose-lintPyPI / compose-lint
low2.2
CVE-2026-121547

dysk before 3.8.2 Terminal Escape Sequence Injection via Mount Metadata

Canop dysk before 3.8.2 contains a terminal escape sequence injection vulnerability that allows local users to inject control sequences by crafting mount metadata rendered unsanitized in table and CSV output. Attackers can create FUSE mounts with ESC/OSC sequences in mount-point names or fsname, causing spoofed or hidden output and window-title changes when another user runs dysk.

No structured fix or guidance is available here. Check the latest publisher advisory.

Exploitation not established

Canop · dysk
medium4.7
CVE-2026-54162

Ember: Unneutralised terminal escape/control sequences from Caddy logs injected into the operator's TUI

Ember is a real-time terminal dashboard for Caddy servers with FrankenPHP support. Prior to 1.4.2, interactive TUI row formatters pass Caddy access-log fields, particularly the request URI, through the fitCellLeft render helper without neutralizing terminal escape or control sequences. An unauthenticated remote client can place ANSI, OSC, or CSI control bytes in an ordinary HTTP request target. Caddy JSON-escapes those bytes, ParseLogLine decodes them back into raw controls, and the formatters concatenate them into View() output reaching os.Stdout. When the operator views the default Logs tab, the terminal interprets these sequences, allowing monitoring-dashboard spoofing, clipboard hijacking through OSC 52, and window-title spoofing through OSC 0/2. This works even with a loopback-only log listener because the input arrives through normal Caddy access logs. Certificates and Routes share secondary unneutralized render sinks. The --json, --once, and daemon --expose modes are unaffected because they do not render an interactive terminal. Consequences depend on the terminal emulator and usually require further operator action to escalate; this is not general-purpose remote code execution. This issue is fixed in version 1.4.2.

No structured fix or guidance is available here. Check the latest publisher advisory.

Exploitation not established

alexandre-daubois · ember
low2.3
CVE-2026-81856

Terminal escape sequence injection in Hex via unneutralized server-supplied output

Improper Neutralization of Escape, Meta, or Control Sequences vulnerability in hexpm hex allows a malicious package publisher or a hostile repository server to inject terminal control sequences into the output of Mix tasks.

Review the recorded instructions. Guidance may be a workaround rather than a fixed version.

Exploitation not established

hexpm · hex / hexpm · hex
medium4.6
CVE-2026-73036

Bash-it barbuk Theme 3.2.0 Terminal Escape Sequence Injection via pyproject.toml

Bash-it 3.2.0 contains a terminal escape sequence injection vulnerability in the barbuk theme's Python virtualenv prompt segment that allows local attackers to inject arbitrary terminal control sequences by embedding escape sequences in the requires-python field of a pyproject.toml file. When a user navigates into a directory containing a maliciously crafted pyproject.toml, the unfiltered field value is read via awk and concatenated directly into PS1 through __prompt-command without stripping control characters, causing injected OSC or CSI sequences to be written to and interpreted by the terminal emulator on every prompt render.

No structured fix or guidance is available here. Check the latest publisher advisory.

Exploitation not established

Bash-it · Bash-it
medium5.3
CVE-2026-73035

npm-check-updates 23.0.2 Terminal Injection via Unsanitized Escape Sequences

npm-check-updates through 23.0.2, fixed in commit b554b84, contains a terminal escape sequence injection vulnerability that allows an attacker to embed arbitrary terminal control characters in a dependency's package.json homepage or repository URL fields. When a developer runs ncu with the --format homepage or --format repo option, unfiltered escape sequences are written directly to the terminal, enabling malicious output manipulation or other terminal-dependent effects.

No structured fix or guidance is available here. Check the latest publisher advisory.

Exploitation not established

raineorshine · npm-check-updates
medium4.6
CVE-2026-47090

Claude HUD 0.0.12 Terminal Injection via OSC 8 Hyperlinks

Claude HUD through 0.0.12, patched in commit 234d9aa, constructs OSC 8 terminal hyperlink escape sequences using raw cwd and branchUrl values without stripping control characters or encoding embedded values, allowing attackers to inject arbitrary ANSI codes into terminal sessions. Attackers can embed ESC+backslash sequences in the current working directory or branch URL to execute malicious ANSI codes including text color changes, forged prompts, and OSC 52 clipboard writes, or trigger outbound HTTP requests to attacker-controlled remotes when hyperlinks are clicked.

No structured fix or guidance is available here. Check the latest publisher advisory.

Exploitation not established

jarrodwatts · claude-hud
low2.1
CVE-2026-6019

BaseCookie.js_output() does not neutralize embedded characters

http.cookies.Morsel.js_output() returns an inline <script> snippet and only escapes " for JavaScript string context. It does not neutralize the HTML parser-sensitive sequence </script> inside the generated script element. Mitigation base64-encodes the cookie value to disallow escaping using cookie value.

No structured fix or guidance is available here. Check the latest publisher advisory.

Exploitation not established

Python Software Foundation · CPython / Siemens · SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0)
medium4.8
CVE-2026-40505

MuPDF < 1.27 mutool ANSI Injection via Metadata

MuPDF before 1.27 contains an ANSI injection vulnerability in mutool that allows attackers to inject arbitrary ANSI escape sequences through crafted PDF metadata fields. Attackers can embed malicious ANSI escape codes in PDF metadata that are passed unsanitized to terminal output when running mutool info, enabling them to manipulate terminal display for social engineering attacks such as presenting fake prompts or spoofed commands.

No structured fix or guidance is available here. Check the latest publisher advisory.

Exploitation not established

Artifex Software Inc. · MuPDF