Handlebars provides the power necessary to let users build semantic templates. From 4.0.0 until 4.7.10, Handlebars.precompile() uses quotedString() in lib/handlebars/compiler/code-gen.js to emit static template text into generated JavaScript without escaping sequences that terminate an enclosing HTML script element. When an application precompiles attacker-controlled template text and embeds the generated source directly in an inline script element, a closing script delimiter can end the element and cause following attacker-controlled markup to be parsed and executed. Ordinary server-side rendering and precompiled templates served as external JavaScript files are not affected. This issue is fixed in version 4.7.10.
CVE-2026-106446 is a critical code injection vulnerability in handlebars.js versions 4.0.0 up to but not including 4.7.10. The vulnerability arises because Handlebars.compile() and Handlebars.precompile() accept pre-parsed AST objects without fully validating all node values, allowing untrusted input objects to inject arbitrary JavaScript code. This can lead to remote code execution on the server or malicious code execution in client environments where precompiled templates are used. Applications passing untrusted objects instead of strings to these functions are affected. The vulnerability has a CVSS score of 9.8, indicating critical severity.
Handlebars provides the power necessary to let users build semantic templates. From 3.0.0 until 4.7.10, Handlebars lookupProperty returns Function.prototype.constructor before applying the prototype-access deny list because constructor is an own property of Function.prototype. When an attacker can render a controlled template with allowProtoMethodsByDefault enabled and an accessible function in the template context, the template can traverse from that function through its prototype to Function.prototype and then obtain the Function constructor through the own-property bypass. This permits attacker-controlled JavaScript to execute with the server application's privileges. This issue is fixed in version 4.7.10.
Quasar Framework is a framework for building high-performance Vue.js user interfaces. Prior to @quasar/render-ssr-error 2.2.4 and @quasar/app-vite 3.3.0, renderSSRError() in utils/render-ssr-error/src/index.js used diagnostic data from utils/render-ssr-error/src/env.js to serialize process.env, request headers, and cookies into the HTTP page returned by serve.devError(), while the development server listened on all interfaces by default. Any network-adjacent client that reaches an SSR or SSG render failure through this development-only error path can obtain shell environment secrets. The renderer escaped only one exact lowercase script closing-tag spelling, so case variants and valid closing-tag delimiter variants in reflected diagnostic data could terminate the script element and inject markup; executing the injected code in a developer browser additionally requires the payload to accompany that developer's request. This issue is fixed in @quasar/render-ssr-error 2.2.4 and @quasar/app-vite 3.3.0.
CVE-2026-106104 is a high-severity vulnerability in the Quasar Framework prior to version 2.23.3. It involves inefficient regular expression complexity in the Platform.parseSSR() function, which processes the User-Agent header during server-side rendering (SSR). An attacker can craft a request with repeated version tokens causing super-linear backtracking in regex evaluation, blocking the Node.js event loop and delaying all SSR requests. This affects only SSR targets; other Quasar targets like SPA, PWA, Electron, Cordova, Capacitor, browser-extension, and static-site-generation are not impacted. The issue is fixed in version 2.23.3.
Quasar Framework is a framework for building high-performance Vue.js user interfaces. Prior to 2.22.0, the SSR-only getHead() serializer in ui/src/plugins/meta/Meta.js used getAttr() to interpolate values supplied through useMeta() into title, meta, link, and script markup without HTML text or quoted-attribute encoding. injectServerMeta() appended that output to the raw server-rendered response. An attacker who can influence dynamic page metadata, such as a post title, product name, excerpt, or display name, can terminate the intended HTML context and inject executable markup before hydration. The client-side apply() path is not affected because it uses DOM APIs that encode attributes. This issue is fixed in version 2.22.0.
Red Hat Single Sign-On 7.6.13 for RHEL 9 addresses multiple security vulnerabilities including HTTP/2 DDoS, cache poisoning, SSRF, SQL injection, denial of service, arbitrary code execution, session fixation, and improper validation issues. These vulnerabilities affect the Undertow HTTP server, cryptographic implementations, DNS validation, HTTP request handling, JSON processing, SAML and OpenID Connect flows, and other components. The update replaces version 7.6.12 and includes various bug fixes and enhancements.
JupyterLab versions 3.0.0 through 4.6.3 are vulnerable to a cross-site scripting (XSS) issue via crafted language pack pluralization headers. The vulnerability arises because JupyterLab improperly executes plural rule strings from language pack metadata using JavaScript's new Function, allowing injected code to run in the user's browser session. This affects users who have installed and selected a malicious or compromised language pack. The vulnerability enables execution of arbitrary JavaScript in the context of the authenticated user, potentially allowing access to Jupyter Server REST API and file system operations. Patches are available in JupyterLab 4.6.4 and 4.5.11. Users of JupyterLab 3.x should upgrade to supported 4.x versions. Workarounds include forcing the interface to use the English locale, which loads no language catalogues.
CVE-2026-105676 is a path traversal vulnerability in TryGhost Ghost affecting versions from 1.20.0 up to but not including 6.64.0. It allows an authenticated Administrator to read JSON files outside the active theme's directory, potentially exposing sensitive server configuration secrets. The issue is fixed in version 6.64.0.
CVE-2026-92931 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the Progress @progress/sitefinity-nextjs-sdk npm package versions 15.1.8326 through 15.4.8637. This flaw allows a remote attacker to make server-side requests to attacker-controlled hosts, which could lead to exposure of sensitive information and impact confidentiality, integrity, and availability of the affected system.
This report details the recovery of a removed npm malware file from the scoped package @goodjavascript/dotenv@1.0.0 using archival sources and CDN metadata. The recovered file contained a timer-based mechanism that collects host information and can execute JavaScript from a server response. The package itself had no installation scripts and an empty exported config function. The recovery was achieved by correlating an older Software Heritage snapshot with a surviving SHA-256 digest from jsDelivr's file manifest. A Python verifier was developed to safely retrieve and hash the file without execution. This analysis supplements an existing OSV advisory and highlights the use of archival tools for malware investigation.
WookTeam versions 1.6.6 and earlier contain a directory traversal vulnerability in the project task export endpoint. This flaw allows an attacker to download arbitrary files from the server by supplying a crafted JSON payload to the /api/project/task/export endpoint. The vulnerability arises because the file path from the JSON is concatenated without normalization or boundary checks, enabling traversal outside the intended storage directory. This can expose sensitive files readable by the web server process.
A vulnerability exists in Apache Thrift nodejs web server versions 3.0 and 4.0 where an upgraded WebSocket connection lacks an 'error' event listener. This issue is identified as CVE-2026-96294 and is cataloged by the Microsoft Security Response Center. No CVSS score or detailed impact information is provided, and no patch or remediation guidance is currently available.
A vulnerability in Apache Thrift's Node.js server.js causes the process to terminate on any per-connection error, with two specific triggers identified. This flaw affects versions 3.0 and 4.0 of the software.
A vulnerability in Apache Thrift allows a JSON member name to stall the Node server's event loop indefinitely. This issue can cause the server to become unresponsive, impacting availability. The affected versions are 3.0 and 4.0. No CVSS score or patch information is provided.
Next.js is a React framework for building full-stack web applications. From 16.0.0 until 16.3.8, the `next dev` development server exposes a Model Context Protocol endpoint without reliably restricting cross-site requests. A malicious website visited by a developer can reach the endpoint and read the project's disk location, source code snippets from error reports, route inventory, and development logs. Production deployments do not serve this endpoint. This issue is fixed in version 16.3.8.
A Server-Side Request Forgery (SSRF) vulnerability exists in Next.js versions 16.0.0 through 16.3.7 in the Image Optimization feature when using images.remotePatterns. This allows attacker-controlled DNS resolution to bypass allow-list checks and fetch images from private IP addresses. Applications not using images.remotePatterns are not affected. The issue is fixed in version 16.3.8.
Next.js is a React framework for building full-stack web applications. From 16.0.0 until 16.3.8, the next dev development server exposes a Model Context Protocol endpoint without reliably restricting cross-site requests. A malicious website visited by a developer can reach the endpoint and read the project's disk location, source code snippets from error reports, route inventory, and development logs. Production deployments do not serve this endpoint. This issue is fixed in version 16.3.8.
Memory allocation with excessive size value, Improper handling of length parameter inconsistency vulnerability in Apache Thrift
nodejs and D lang bindings.
Both bindings' WebSocket server transports read the payload length out of the frame header and allocate that many bytes immediately, without checking that the bytes have arrived. A single ~14-byte frame therefore commits as much memory as it cares to declare -- measured at 513 MiB against the Node.js server and 2 GiB against the D transport -- and in the Node.js case the connection is left open afterwards, so the frame can simply be sent again.
This issue affects Apache Thrift before 0.25.0.
Users are recommended to upgrade to version 0.25.0, which fixes the issue.