Loading vulnerability…
CVE-2026-9277 is a command-injection vulnerability in the shell-quote npm package's quote() function. When serializing an object token with an op property, vulnerable versions backslash-escaped the value character by character using a JavaScript regular expression that does not match line terminators. Carriage return, line feed, and Unicode line- and paragraph-separator characters could therefore be emitted unescaped. POSIX shells interpret a literal newline as a command separator, allowing content following an attacker-supplied line terminator to be executed as a separate command. The vulnerable path is reachable when an application constructs attacker-influenced object tokens directly or when parse(cmd, envFn) receives attacker-influenced object tokens from envFn.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains a single Python exploit/scanner (CVE-2026-9277.py) plus a README. The script is a standalone PoC for CVE-2026-9277, described as a structural command injection issue in legacy shell-quote versions <= 1.8.3. Its purpose is to send crafted JSON POST requests to a user-supplied target URL, recursively traverse nested objects/lists, and mutate array structures to trigger command injection in downstream shell-quote usage. Core logic centers on the AdvancedCVE2026Fuzzer class. It creates a requests session with TLS verification disabled, calculates a baseline response time using repeated POSTs, then performs recursive mutation of JSON nodes and submits modified payloads. Detection supports three modes: in-band output leakage by searching response text for command-execution artifacts (e.g., uid=, root:x:), blind/time-based detection by comparing elapsed response time against the baseline, and optional out-of-band confirmation using a user-provided webhook URL. The script prints structured evidence including the mutated request body and truncated response body when a likely exploit path is found. The exploit is operational rather than merely demonstrative because it automates target interaction, payload mutation, and verification logic. However, it is not part of a larger exploitation framework and appears intended for manual operator use from the command line. The main entry point parses --url, --body, --webhook, and --timeout arguments, loads the base JSON body, and launches fuzzing. No hardcoded victim infrastructure is present; all targets are operator-supplied. The README provides example target and webhook URLs only.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An earlier shell-quote vulnerability whose fix was incomplete with respect to line terminators in tokens following a comment token.
A shell-quote arbitrary code execution vulnerability involving command injection due to unescaped line terminators.
A command injection vulnerability caused by improper escaping of line terminator characters in the .op property during shell string serialization, allowing injected commands to be separated and executed in POSIX-compliant shells.
A critical command injection vulnerability in the npm shell-quote package caused by improper validation in the quote() function, allowing newline characters to pass through unescaped and be interpreted by POSIX shells as command separators.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.