ApostropheCMS is an open-source Node.js content management system, and sanitize-html provides a simple HTML sanitizer with a clear API. From version 1.9.0 until version 2.17.7, packages/sanitize-html/index.js validates an animation value attribute as one flat URL and does not recognize that attributeName selecting href or xlink:href gives the sibling values, from, to, or by attribute SVG SMIL URL semantics. In configurations that allow the animate, animateColor, animateMotion, animateTransform, or set elements, a values list can begin with a safe fragment and contain a later executable destination that survives allowedSchemesAppliedToAttributes checking. When the sanitized SVG is rendered, the browser can copy that later destination into the live link, and a victim who activates the link can execute script in the application's origin. This issue is fixed in version 2.17.7.
SVGO, short for SVG Optimizer, is a Node.js library and command-line application for optimizing SVG files. From version 1.0.0 until versions 2.8.4, 3.3.5, and 4.1.0, the opt-in removeScripts plugin, named removeScriptElement in versions 2 and 3, incompletely filters executable links in plugins/removeScripts.js and lib/svgo/tools.js. The plugin does not recognize namespace-prefixed SVG anchor elements such as svg:a with href or namespaced *:href values, and it does not remove ASCII tab, line-feed, or carriage-return characters before checking URL schemes. Browsers remove those characters before parsing a scheme, allowing an executable link to pass the plugin's check. When an application processes attacker-controlled SVG input and serves the result in an active browser context, a victim who activates the surviving link can execute script in the SVG's origin, expose data, modify content, or perform actions as the victim. This issue is fixed in versions 2.8.4, 3.3.5, and 4.1.0.
SVGO, short for SVG Optimizer, is a Node.js library and command-line application for optimizing SVG files. From version 1.0.0 until versions 2.8.4, 3.3.5, and 4.1.0, the opt-in removeScripts plugin, named removeScriptElement in versions 2 and 3 and implemented in plugins/removeScripts.js, removes SVG and XHTML script elements but does not inspect executable HTML content inside SVG foreignObject elements. Event-handler attributes such as onload and onbeforetoggle, srcdoc documents, and executable URLs in the action, data, formaction, href, and src attributes can remain in attacker-controlled SVG input. When an application uses the plugin as its only protection and serves the optimized SVG in an active browser context, the payload can execute script in the viewer's origin, expose data, modify content, or perform actions as the victim. This issue is fixed in versions 2.8.4, 3.3.5, and 4.1.0.
Red Hat has issued a security advisory for the Node.js 22 module in Red Hat Enterprise Linux 8 addressing multiple vulnerabilities. These include unauthorized filesystem access due to a permission model enforcement flaw (CVE-2026-58043), remote memory exhaustion via HTTP/2 retained header blocks (CVE-2026-56846), and a heap-use-after-free vulnerability in HTTP/2 handling that can lead to denial of service (CVE-2026-56848). The update is rated as Important by Red Hat Product Security. The advisory provides a security update to mitigate these issues.
The npm package 'bt2-api-gateway-node-js' versions 999.0.0 and 999.0.1 contains malicious code that executes during post-installation. This code collects sensitive secrets from the user's environment, including private keys and credentials from various cloud and development tools, environment variables with tokens and passwords, then exfiltrates this data encoded to a Telegram Bot API endpoint and a suspicious IP address over plain HTTP. The malicious behavior includes evasion techniques to avoid detection in CI environments and sandboxes. This package is identified as a dependency confusion lure targeting an internal package name.
A vulnerability exists in node-xmldom prior to versions 0.8.15 and 0.9.12, and in xmldom version 0.6.0 and earlier, where the DOCUMENT_TYPE_NODE branch in lib/dom.js improperly validates the DocumentType.name property. This allows injection of sibling markup by terminating the <!DOCTYPE ...> declaration early if the name contains '>' or whitespace. The issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fix is available for xmldom 0.6.0 and earlier.
The node-xmldom library versions from 0.9.0 up to 0.9.12 contain a vulnerability in the shared reg() builder in lib/grammar.js. This builder compiles the anchored QName_exact validator with the multiline flag, causing ^ and $ anchors to validate only one line instead of the entire XML name. As a result, certain XML creation functions accept malformed XML names that include line terminators, potentially injecting markup when serialized. This issue is fixed in version 0.9.12.
The Node.js xmldom library versions prior to @xmldom/xmldom 0.8.15 and 0.9.12, and xmldom 0.6.0 and earlier, contain a parsing issue where DOMParser.parseFromString() can silently accept malformed end tags, discarding trailing content without error. This flaw allows bypassing of well-formedness checks but does not inject discarded content. The issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fix exists for xmldom 0.6.0 and earlier. The vulnerability has a medium severity rating based on CVSS 4.0 metrics and does not have known exploits in the wild.
A performance issue exists in node-xmldom prior to versions 0.8.15 and 0.9.12, and in version 0.6.0 and earlier, where parsing elements with many attributes causes quadratic time complexity in attribute insertion. This can stall the Node.js event loop during XML parsing before application validation. The issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fix is available for xmldom 0.6.0 and earlier.
The Node.js xmldom library versions prior to @xmldom/xmldom 0.8.15 and 0.9.12, and xmldom versions 0.1.5 through 0.6.0, contain a vulnerability in the appendElement function in lib/sax.js. This function uses _copy to clone the current namespace map for each nested element declaring a new namespace prefix, causing quadratic growth in namespace-map storage. This can lead to heap exhaustion when parsing small, highly compressible XML documents, potentially causing denial of service. The issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fix is available for xmldom. Several specific affected package versions are identified.
The Node.js xmldom library versions from 0.9.11 up to but not including 0.9.12 contain a vulnerability in the requireWellFormed: true element and attribute name validation. This flaw allows certain newline characters to bypass strict serialization checks, potentially leading to malformed XML output. The issue is fixed in version 0.9.12.
The Node.js xmldom library versions from 0.9.10 up to but not including 0.9.12 contain a vulnerability in the requireWellFormed: true serializer. This serializer improperly validates DocumentType.publicId and DocumentType.systemId, allowing certain newline characters and breakout markup to bypass strict serialization checks. This flaw can lead to DocumentType injection despite prior mitigations. The issue is fixed in version 0.9.12.
Mirage Kitten, an APT group historically focused on the Middle East and Africa, has deployed two previously undocumented cross-platform remote access trojans: NodeRabbit (Node.js-based) and PollCat (JavaScript-based). Both malware families mark the group's first departure from native malware toward scripting languages compatible with Windows, Linux, and macOS. Operators deliver these tools through sophisticated social engineering campaigns involving fake recruiters on LinkedIn who distribute trojanized coding challenges via Amazon S3 buckets. The malicious projects contain backdoored npm packages that silently install persistent implants. NodeRabbit implements comprehensive command-and-control capabilities including file operations, process management, and proxy-aware C2 communications through Azure and Cloudflare infrastructure. PollCat provides similar RAT functionality with specialized developer persistence mechanisms targeting VS Code extensions and Git hooks. Targeted sectors include aviation, aerospa...
A flaw in the Node.js HTTP client can cause request desynchronization in Node.js-based forwarding proxies that rebuild outbound headers from visible IncomingMessage headers while reusing backend connections. This occurs because Node.js may omit headers beyond configured limits from user-visible header collections but still use those omitted headers internally for HTTP message framing, potentially hiding headers like Content-Length from userland. This affects all supported Node.js release lines including versions 22, 24, and 26. The CVSS score is 3.7, indicating medium severity.
A flaw in Node.js HTTP client can cause a request desynchronization for Node.js-based forwarding proxies that rebuild outbound headers from the visible `IncomingMessage` headers while piping the original body to a reused backend connection.
Node.js can omit headers beyond `maxHeadersCount` / `maxHeaderPairs` from `req.headers`, `req.rawHeaders`, and `req.headersDistinct`, while still using those omitted headers internally for HTTP message framing. In particular, `Content-Length` can be hidden from userland while the request body is still delivered.
This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
Payload CMS versions prior to 3.73.0 contain a blind SQL injection vulnerability in the processing of 'where' filters on JSON or RichText fields using the Drizzle database adapters. This vulnerability allows attacker-controlled JSON filter input to manipulate generated JSONPath expressions, potentially exposing sensitive data. Exploit code is publicly available demonstrating this issue on Payload CMS 3.72.0 with PostgreSQL 15.
The npm package @testrelic/appium-analytics version 1.1.1-next.88 contains malicious code that executes automatically during installation. It uses obfuscated code to reconstruct and invoke the Function constructor, enabling execution of a hidden payload with access to Node.js module and filesystem APIs. The package also performs network calls and includes install-time dropper behavior. Any system with this package installed should be considered fully compromised, and all secrets on that system should be rotated immediately.
A prototype pollution vulnerability (CVE-2026-67320) was found in axios when used with the Node.js HTTP adapter. This flaw allows request interceptors to revert hardened request configurations, enabling an attacker to manipulate the Object.prototype.proxy property. Successful exploitation could allow an attacker to route plaintext HTTP requests through a malicious proxy, potentially exposing sensitive data such as authentication headers and request bodies, and even injecting malicious responses. The issue affects OpenShift Virtualization v4.12 images as distributed by Red Hat. Red Hat has released updated images to address this vulnerability.