CVE-2026-99070 addresses a warning removal in the Linux kernel's IPv6 route notification handling. The issue involves a race condition where concurrent changes can cause legitimate size errors during route notification processing, which previously triggered misleading warnings. The fix removes these warnings while preserving existing error handling that frees resources and reports errors to listeners.
The npm package 'log-rotate-testmetest' version 1.0.1 contains malicious code embedded in its binding.gyp file that triggers execution of an obfuscated payload during installation. This payload uses multiple layers of obfuscation including ROT cipher, AES-128-GCM decryption, and brotli decompression, ultimately executing attacker-controlled code via the Bun runtime. The package declares Bun as a runtime dependency to route execution through an alternate runtime rather than Node.js. There is no legitimate native build rationale for this behavior, indicating deliberate malicious intent.
CVE-2026-114139 is a critical vulnerability in the Sentry-Javascript SDK's webpack integration for @sentry/nextjs. Versions from 9.36.0 up to but not including 9.47.2, 10.0.0-alpha.0 up to 10.75.2, and 11.0.0-alpha.0 up to 11.0.0-rc.1 are affected. The issue arises when the configured tunnelRoute causes the webpack integration to skip application middleware for request paths under that route, allowing unauthenticated requests to reach protected routes if they collide with the tunnel path or a root dynamic segment. This can lead to unauthorized access when middleware is the sole authorization mechanism. The vulnerability is fixed in versions 9.47.2, 10.75.2, and 11.0.0-rc.1.
Nuxt versions prior to 4.6.2 have a case sensitivity mismatch between page resolution and server-side route-rule matching. This allows requests with paths differing only by letter case to bypass intended server rules such as redirects, headers, proxy settings, and SSR controls. Applications that set router.options.sensitive: true in nuxt.config are not affected. The issue is fixed in version 4.6.2.
The Swiper formatter module for Drupal provides a route to display published content entities in a dialog but does not sufficiently verify user access to these entities. However, the vulnerability is mitigated because only rendered output is returned and field-level access controls remain enforced. A patch is available for affected versions.
A vulnerability in Nuxt versions from 3.11.0 up to but not including 3.21.4 and from 4.0.0 up to but not including 4.4.4 allows percent-encoded URL segments to bypass route rule checks. This causes appMiddleware to be skipped during server-side rendering, enabling unauthenticated users to access protected pages and their server-rendered data. The issue also affects app-manifest rules such as redirect, appLayout, ssr, prerender, and payload flags. The vulnerability is fixed in Nuxt versions 3.21.4 and 4.4.4.
A cross-site scripting (XSS) vulnerability exists in Nuxt versions prior to 4.6.0. This flaw arises from an incomplete fix for a previous issue (CVE-2026-53722) where an attacker can craft a script-capable URL by prefixing attacker-controlled input with an ASCII C0 control character. The no-pages router misclassifies such input as an internal route and renders it in an anchor href, which browsers then interpret as a javascript: URL after removing the control character. Exploitation requires a victim to click the malicious link, leading to script execution within the application's origin. The vulnerability is fixed in Nuxt version 4.6.0.
CVE-2026-114476 is an authorization vulnerability in the REST administration API of Progressive Robot Ltd's hMailServer versions 6.3.4 through 6.3.6. It allows a remote authenticated user with manage_roles permission in certain domains or an account with the serveradmin role to escalate privileges to full server administrator authority by exploiting a flaw in role removal logic. Specifically, the API route for deleting role assignments does not properly verify post-removal permissions, enabling privilege escalation and unauthorized administrative access.
CVE-2026-114463 is an authorization vulnerability in Nous Research Hermes Agent affecting versions up to 2026.8.19. The issue arises because the webhook platform gateway constructs session chat IDs using a string format that includes the route name, which can contain colons. This allows an attacker who possesses the target HMAC to manipulate the route name parsing and gain access to higher-privileged toolsets than authorized.
Trigger.dev versions before 4.5.0 have a vulnerability in the dashboard run replay route where no authentication or organization check is performed. This allows an attacker who knows a victim's run friendlyId to replay the run, potentially exposing sensitive task payloads or executing tasks with the victim's secrets.
Trigger.dev versions prior to 4.5.6 have an authorization bypass vulnerability in the DeleteTaskScheduleService and SetActiveOnTaskScheduleService components. This flaw allows authenticated users to delete or disable schedules belonging to other organizations by exploiting user-controlled keys. Attackers can misuse their own project's schedule route with a victim's schedule friendlyId to manipulate and destroy other organizations' imperative cron schedules.
ApostropheCMS versions prior to 4.33.0 have a vulnerability where an unauthenticated user can access the GET /api/v1/<piece-type>/:_id/locales REST route without proper authorization checks. This allows the user to determine if a document exists and which locales it is published in, exposing sensitive metadata that should be restricted. The issue is fixed in version 4.33.0.
ApostropheCMS versions prior to 4.33.0 and its Form add-on prior to 1.5.5 have a vulnerability where the form submission route accepts unbounded multipart uploads before validation or authentication. This lack of upload size, count, and rate limits allows repeated unauthenticated submissions to consume temporary disk storage, potentially disrupting form handling and other services. The issue is fixed in ApostropheCMS 4.33.0 and Form add-on 1.5.5.
CVE-2026-113603 is an authorization bypass vulnerability in the x402 SIWX server extension within @x402/extensions, x402 PyPI, and Go module versions specified. It allows paying clients to access unpaid, more expensive routes by manipulating the PaymentPayload.resource URL, paying only for the cheapest route but accessing costly ones without additional payment. The vulnerability affects multiple versions across these packages and has a medium severity rating with a CVSS 4.0 score of 6.9.
A denial of service (DoS) vulnerability exists in @angular/router when Server-Side Rendering (SSR) is enabled on Node.js. The router fails to validate auxiliary outlet segments in URLs, allowing crafted requests with multiple empty-path outlet segments to cause excessive memory and CPU usage. This leads to Node.js process termination due to heap exhaustion. The vulnerability affects SSR configurations with empty-path or named outlet routes and can be mitigated by upgrading to patched versions or rejecting malicious URL patterns upstream.
The npm package api-anthropic impersonates Anthropic branding and redirects all Claude Code AI assistant traffic through an attacker-controlled proxy. It modifies user configuration files to route requests and pre-approves folder trust and external include prompts, enabling persistent interception of AI interactions and arbitrary file access without user consent. This results in a durable channel for exfiltrating sensitive data including prompts, code, file contents, and credentials.
SGLang through 0.5.22 with the Mooncake disaggregation backend contains an uncontrolled memory allocation vulnerability in handle_staging_rsp() that lets unauthenticated network-adjacent attackers exhaust Prefill memory. Attackers can obtain the rank address from the /route endpoint and send STAGING_RSP messages with huge chunk_idx values under fresh room IDs, causing the scheduler to be OOM-killed.
Insufficient Granularity of Access Control vulnerability in Apache Camel Platform HTTP component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
The component decided whether an endpoint ran in proxy mode by testing whether its configured path started with the string proxy, rather than by matching the path exactly. Any endpoint whose path merely begins with those characters - proxyStatus, proxy-config, proxying and so on - therefore became a proxy endpoint without the route author asking for it. A proxy endpoint forwards requests onward, so an endpoint that was intended to serve its own content instead relays traffic on behalf of whoever calls it, which is both a request forgery primitive and an exposure of whatever the forwarding path can reach.
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. Proxy mode is now selected by an exact path match rather than by prefix. For deployments that cannot upgrade immediately, rename any endpoint path that begins with proxy but is not intended to be a proxy.
Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel gRPC component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
When a route behind a gRPC consumer failed, the exception's message was placed into the gRPC status description. Unlike the status cause, which stays local to the server, the description is transmitted to the calling client, so an external caller able to provoke a failure could read the internal error message. What that discloses depends on the exception, and in practice includes class and package names, paths, host names and connection detail carried in messages. This is the gRPC member of the same unmuted-consumer-exception family as the knative, mina and CXF advisories published alongside it.
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. A muteException consumer option, defaulting to true, puts a generic description in the status instead of the route exception's message. Set muteException=false to restore the previous output. For deployments that cannot upgrade immediately, map failures onto an explicit status in an onException handler so the framework never copies the exception message into the description.