Loading vulnerability…
CVE-2026-27971 is a remote code execution vulnerability in the Qwik JavaScript framework affecting versions up to and including 1.19.0. The flaw is caused by unsafe deserialization in the server$ RPC mechanism. According to the provided content, an unauthenticated attacker can send a single crafted HTTP request that triggers deserialization of untrusted data and results in arbitrary code execution on the server. The issue affects deployments where require() is available at runtime.
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 standalone Python exploit PoC and a README. The main file, exploit_combat.py, targets CVE-2026-27971 / GHSA-p9x5-jp3h-96mm in Qwik server$ RPC deserialization. It is not part of a larger exploit framework. The script builds crafted application/qwik-json requests that abuse Qwik's unsafe resolution of unregistered QRLs through runtime require(), allowing invocation of attacker-selected module exports from node_modules without authentication. The exploit is operational rather than a simple detector: it first performs an active probe using a marker payload, can attempt OS detection by executing process.platform, and then uses a selected gadget to achieve arbitrary code execution. Built-in gadgets target common Node.js packages/modules such as cross-spawn, execa, and node-cmd, with support for argv, command, and shell invocation styles. The operator may also specify a custom <module>#<symbol> gadget. Capabilities include: active RCE confirmation, arbitrary command execution, UTF-8 text file read, UTF-8 text file write-and-verify, and reverse shell delivery. Reverse shell support includes multiple Linux one-liners (nc, busybox, bash TCP, python/python3, perl) and a Windows PowerShell TCP reverse shell. The script also supports optional outbound callback pre-checking and SSL verification control. Repository structure is minimal: Readme.md documents vulnerability details, usage, limitations, and remediation; exploit_combat.py contains the full exploit logic, CLI parsing, gadget catalog, request generation, probe logic, OS detection, and payload delivery. Fingerprintable targets/endpoints are primarily the operator-supplied target URL, the Qwik JSON content type, built-in node_modules gadget paths, callback host/port values, and temporary file paths used by payloads.
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.
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.