Ghost from 1.20.0 before 6.64.0 contains a path traversal vulnerability in theme translation file loading that allows authenticated administrators to read JSON files outside the active theme directory. Attackers can manipulate the locale setting to load JSON files elsewhere on the server, exposing server configuration secrets.
CVE-2026-75899 is a vulnerability in the fast-uri Node.js library used by Red Hat products such as Red Hat Satellite's Lightspeed component. The flaw involves double decoding of percent escapes in hostnames during URI parsing, which can allow an attacker to manipulate URIs to redirect requests to unintended network destinations, including internal services. This can lead to Server-Side Request Forgery (SSRF) and bypass of host-based security policies. No fix is currently available that meets Red Hat's criteria for deployment and stability. The vulnerability is rated as high severity by Red Hat.
The AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 3.8.0 This is due to a chain of missing input neutralization and output escaping across the /mwai-ui/v1/chats/submit REST endpoint, the PHP error-log parser (MeowKit_MWAI_Helpers::php_error_logs), the Advisor task (Meow_MWAI_Modules_Advisor::run_advisor), and the Advisor dashboard widget (advisor_metabox): the server-parameter denylist in chat_submit strips only exact key names such as 'model' while convert_keys() later canonicalizes 'model_' back to 'model', allowing an unauthenticated caller to place an attacker-controlled string (including CR/LF) into $query->model; final_checks() throws an Exception whose message embeds that raw string, and the non-streaming, non-admin catch branch writes it to the PHP error log unmodified — creating a forged log line that the plugin's own parser subsequently returns as recent PHP-error content; run_advisor() then appends that content verbatim to the AI prompt (indirect prompt injection — CWE-1427), the returned JSON is stored in the mwai_advisor_data option with no schema validation or HTML sanitization, and advisor_metabox() concatenates the resulting 'title' and 'description' values directly into the WordPress dashboard widget without esc_html(), wp_kses(), or equivalent escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever an administrator accesses the WordPress dashboard.
A vulnerability was detected in decolua 9Router up to 0.5.55. The affected element is the function fetch of the file src/shared/utils/ssrfGuard.js of the component Search Endpoint. Performing a manipulation of the argument provider_options.baseUrl results in server-side request forgery. The attack can be initiated remotely. Applying a patch is the recommended action to fix this issue.
CVE-2026-73570 is an unauthenticated OS command injection vulnerability in the SNMP notification path of Zimbra Collaboration Suite mail servers. It was actively exploited between July and August 2026. Attackers used this flaw to deploy JSP webshells and reverse shells without authentication, escalate privileges via PAM configuration abuse, and maintain persistence through systemd services. Post-exploitation activities included lateral movement across clusters using Zimbra SSH keys, theft of authentication secrets and mailbox data, and attempts to exfiltrate data using cloud storage tools. Multiple organizations across various regions and industries were targeted through automated and manual attacks on internet-facing Zimbra mail servers.
CVE-2026-102984 is a high-severity vulnerability in the Astro web framework prior to version 11.1.3. The @astrojs/node adapter improperly builds request URLs from the Host header, and a malformed port can cause an invalid URL. This leads to an uncaught TypeError exception before routing begins. In the default configuration, this results in an HTTP 500 response while the server continues running. However, if staticHeaders is enabled, the uncaught exception causes the Node.js process to terminate, impacting availability. The vulnerability does not expose data or allow code execution. The issue is fixed in version 11.1.3.
The npm package com.epi.e2e_test version 1.2.2 contains malicious code that executes automatically during installation. A preinstall script runs an index.js file which collects host-specific identifiers such as the home directory, hostname, username, DNS servers, current working directory, and the package.json contents. This data is then sent via HTTPS to a hardcoded external server (meta.brs.cx) without user consent. This behavior is indicative of reconnaissance activity commonly associated with dependency confusion or internal name attacks.
A denial of service (DoS) vulnerability exists in the brace-expansion library used in Red Hat Hardened Images, including Node.js 22 runtime environments. The flaw allows remote attackers to cause a server crash by supplying deeply nested brace patterns that trigger uncontrolled recursion and exhaust the call stack. This vulnerability does not affect confidentiality or integrity but can disrupt availability of affected services. Exploitation requires processing of untrusted input without input depth validation. No effective mitigation is currently available that meets Red Hat's criteria for ease of use and stability.
PyJWT versions prior to 2.14.0 contain a vulnerability where deeply nested JSON arrays in the JWT header cause a RecursionError during decoding. This error is not caught by the library's usual exception handling, resulting in an unhandled exception that leads to HTTP 500 server errors and full tracebacks logged. The issue allows an unauthenticated attacker to cause a denial of service on JWT validation endpoints by sending crafted tokens with excessively nested headers. The flaw is fixed in PyJWT 2.14.0 by catching RecursionError and converting it to a DecodeError.
PyJWT versions up to 2.13.0 have a denial-of-service vulnerability where unauthenticated requests with unknown 'kid' values cause repeated JWKS endpoint fetches without rate limiting or caching of negative results. This leads to excessive outbound HTTP requests and JSON parsing on the victim server, potentially exhausting resources and causing authentication outages. The issue was fixed in PyJWT 2.14.0 by adding a cooldown period to limit forced JWKS refreshes on unknown kids.
A security update for Red Hat Hardened Images RPMs addresses CVE-2026-93981, a moderate severity cross-site scripting (XSS) vulnerability in hono/jsx. The flaw arises from improper escaping of plain strings during server-side rendering, allowing remote attackers to inject malicious code via crafted input. Exploitation requires specific application rendering contexts and user interaction, limiting exposure. The update includes patched versions of grafana13.1 RPMs. No direct mitigation is currently available, and the vulnerability is embedded within containerized services and developer tooling.
A denial of service (DoS) vulnerability exists in jackson-databind used by Red Hat Lightspeed (formerly Insights) for Runtimes on RHEL 9. The flaw allows unauthenticated attackers to cause high CPU usage by submitting specially crafted JSON with unbounded numeric values during deserialization of certain XML-related data types. This can saturate server worker threads and make the service unavailable. Red Hat has released an update to address this issue.
Nodemailer versions up to 10.0.1 improperly handle deeply nested recipient arrays in fields like to, cc, and bcc. This flaw causes a stack exhaustion denial-of-service (DoS) when processing such inputs, leading to a RangeError and potential termination of the Node.js process. The vulnerability arises because only the outermost array is flattened before passing nested arrays to a parser that converts them to strings recursively, exhausting the V8 call stack. No SMTP server or successful email delivery is required to trigger this. The issue is fixed in version 10.0.2.
CVE-2026-44486 is an information disclosure vulnerability in Axios's Node.js HTTP adapter used in Red Hat OpenShift Virtualization v4.12 images. When Axios is configured to use an authenticated proxy and follows an HTTP redirect, it may inadvertently send the Proxy-Authorization header containing sensitive proxy credentials to the redirected target, potentially exposing these credentials to an untrusted remote server. This issue affects Red Hat products using Axios in Node.js environments with authenticated proxies and automatic redirects enabled. No patch or effective mitigation meeting Red Hat's criteria is currently available.
In affected versions of Octopus Server, an authenticated user with permissions to edit an Environment or Project can set specifically crafted JSON content for the object. Insecure deserialization of this content allows the user to execute arbitrary code in the Octopus Server process.
Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.
A vulnerability in Node.js TLS server occurs when SSL_set_SSL_CTX() is called to switch a SSL_CTX during a handshake and the new context has more provider signature algorithms than the original. This can cause out-of-bounds memory access leading to a denial of service. The issue affects only non-default configurations where SSL_CTX is switched mid-handshake with differing signature algorithms. FIPS modules are not impacted. The severity is low due to limited exploitation scope and the need for specific application behavior.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (a8e49b1abd7c566b17104c5a2823251df2ca253a0fa509d7c19db1c1942ad13d)
On require, index.js invokes initializeDaemon() at top level, which uses spawn('node', [lib/check-items.js], { detached: true, stdio: 'ignore' }) followed by child.unref() to launch a persistent background process independent of the parent. The daemon HTTP-GETs a JSON payload from the hardcoded endpoint https://game.spawnrealm.com/api/item-realtime?key=abcdef123456 and passes payload.code to `new Function('require', 'module', payload.code)`, executing server-supplied JavaScript inside the installer's Node process with full `require` access. An RSA signature check is performed against a public key bundled in the package (crypto-config.js), so the author controls both the signing key and the verifier and the check provides no independent integrity guarantee. Anyone controlling game.spawnrealm.com — including via DNS or TLS — can run arbitrary code as the installing user for the lifetime of the host process. The package is advertised as a validator library, and this remote-code-loader behavior is undisclosed and unrelated to the stated purpose.
A denial of service (DoS) vulnerability exists in the Angular Server-Side Rendering (SSR) package @angular/platform-server due to a flaw in the domino HTML parser. When processing untrusted input containing an incomplete DOCTYPE declaration ending with whitespace before EOF, the parser enters an infinite synchronous loop that consumes 100% CPU and freezes the Node.js server process. This affects applications that bind untrusted user input to [innerHTML] or manipulate DOM on the server. The vulnerability is exploitable remotely without authentication. Workarounds include avoiding direct binding of untrusted input to [innerHTML] or sanitizing input to reject incomplete DOCTYPE strings. A patch is available for affected versions.
Nest is a framework for building scalable Node.js server-side applications. Prior to 11.2.4 and 12.0.2, a single message with a deeply nested object in its pattern can terminate a NestJS microservice using the TCP or RabbitMQ transport. ServerTCP#handleMessage and ServerRMQ#handleMessage pass a client-controlled non-string pattern to JSON.stringify to derive the handler lookup key; sufficiently deep nesting throws RangeError: Maximum call stack size exceeded, and the unhandled promise rejection terminates Node.js under its default behavior. An attacker who can reach the TCP port or publish to the consumed RabbitMQ queue or exchange can crash the service on demand; other transports are not affected because their patterns arrive as strings. This issue is fixed in versions 11.2.4 and 12.0.2.