@eeacms/volto-chatbot version prior to 2.0.4 contains an unauthenticated proxy vulnerability that allows attackers to invoke arbitrary Danswer API operations with server-side credentials. The middleware route '**/_v1_da/**' accepts any HTTP method and path without authentication or path restrictions, forwarding requests with attached API keys or session cookies. This enables a Confused Deputy attack where attackers can perform privileged actions on the upstream Danswer API as the configured service account.
Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the volume artifact handler for GET /artifacts/get?source=volume did not confine a caller-supplied file path to the selected volume. A caller who can reach the route and identify an existing mounted volume can use path traversal to read files outside that volume when the artifact-serving process can read them. The frontend pod serves the request when artifact proxying is disabled, while the selected namespace's artifact-service pod serves it when proxying is enabled. A deployment with authentication disabled requires no application credentials; in multi-user deployments, the caller ordinarily must be authorized for the supplied namespace. This issue is fixed in version 2.18.0.
An unauthorized relay service has been installing legitimate OpenAI Codex and Anthropic Claude Code CLI tools on enterprise systems, reconfiguring them to route requests through third-party infrastructure. This activity, active since early 2026, primarily affects organizations in mainland China, South Korea, Taiwan, and Malaysia across multiple industrial sectors. The relay disables execution sandboxes, enables network access, replaces API credentials with relay-issued tokens, and disables telemetry, granting operators full user privilege command execution and access to sensitive data. No abuse evidence is currently reported.
The Mapster WP Maps plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 2.0.5. This is due to the /wp-json/mapster-wp-maps/save-mapmaker REST route being registered with a permission_callback that unconditionally returns true (no capability check, no nonce), together with the mapster_write_config_to_acf() helper only sanitizing string config values with sanitize_text_field() — which strips HTML tags but leaves quote characters intact — and the mapster_wp_map shortcode renderer in mapster_wordpress_maps_shortcode_display() concatenating the stored loading_background_color value into a single-quoted inline style attribute without esc_attr(). This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
The Contact Form by Supsystic WordPress plugin versions before 1.11.1 lack verification of a CSRF nonce when saving mail settings. This vulnerability allows an attacker to trick a logged-in administrator into visiting a crafted page, resulting in the overwriting of the site's outbound mail configuration, including SMTP server details, credentials, and notification recipients. This can enable the attacker to route contact form notifications through infrastructure they control.
The Photo Engine (Media Organizer & Lightroom) WordPress plugin versions before 6.6.0 contain an authorization bypass vulnerability in a REST API route. Authenticated users with Author-level access or higher can modify post data, including titles, content, excerpts, and other fields, for arbitrary posts, pages, and attachments, even those owned by other users.
Echo, a Go web framework, has a reflected cross-site scripting (XSS) vulnerability in versions prior to 4.16.0 and 5.4.0. The issue arises from the Context.JSONP and Context.JSONPBlob methods, which concatenate an unvalidated callback parameter into a JavaScript response. This allows an attacker to inject executable script if the application exposes a route that accepts attacker-controlled callback input. The vulnerability is fixed in versions 4.16.0 and 5.4.0.
CVE-2026-118654 is a path traversal vulnerability in the labstack Echo Go web framework. Versions prior to 4.16.0 and between 5.0.0 and before 5.4.0 allow unauthenticated attackers to bypass route-level middleware protections by exploiting static file handlers that normalize dot segments after route matching. This enables unauthorized reading of files intended to be protected. The issue is a regression from an incomplete fix of a previous vulnerability and is resolved in versions 4.16.0 and 5.4.0.
A vulnerability in github.com/labstack/echo/v5 middleware.Static allows bypassing route/group middleware guards by using a %2F-encoded path. When middleware.Static is mounted globally, the router matches routes on the raw encoded path, skipping guards for %2F-encoded requests, while the static handler decodes the path and serves the file inside the static root. This leads to unauthorized access to files within the static root that were intended to be protected by route-level middleware. The issue is not path traversal and does not expose files outside the static root. A fix is available in versions 5.4.0 and 4.16.0.
CVE-2026-118264 is a critical HTTP request smuggling vulnerability in the labstack Echo Go web framework. It affects versions from 4.0.0 up to but not including 4.16.1, and from 5.0.0 up to but not including 5.4.1. The flaw arises in Echo's Proxy middleware, which improperly handles client WebSocket upgrade requests by selecting a raw tunnel before verifying if the upstream server accepted the upgrade. If the upstream rejects the upgrade with a keep-alive response, subsequent HTTP requests bypass Echo's router and route-specific middleware, potentially circumventing authentication or authorization controls enforced by Echo routes. This vulnerability requires a specific setup including an accessible proxy route, a cooperating rejected-upgrade response, and an upstream target lacking independent authorization. The issue is fixed in versions 4.16.1 and 5.4.1.
The OAuth login OAuth2 module for Drupal allows login via OAuth 2.0 or OpenID Connect identity providers. A vulnerability exists due to insufficient access checks on a configuration route and lack of verification that the identity provider has confirmed the email address it returns. This flaw enables an attacker to log in as any existing user if they know that user's email address. Exploitation requires the attacker to have an account with a configured identity provider and control over at least one returned attribute, such as username. The issue is fixed in version 3.1.1.
CVE-2026-116078 is a resource exhaustion vulnerability in the HTTP/2 request body reader of mtrudel bandit. An unauthenticated remote attacker can send many 1-byte DATA frames to exhaust server memory. The issue arises because each 1-byte frame is stored as a separate list element, causing excessive memory use especially when many concurrent streams are used. This affects any route behind Plug.Parsers that reads the request body. The vulnerability affects bandit versions from 0.3.1 up to but not including 1.14.1.
OpenHop versions prior to 0.3.7 contain a path traversal vulnerability in the server component that allows unauthenticated attackers to read or delete YAML files outside the intended directory. This occurs because flow route parameters are passed without an identifier allow-list and are decoded and normalized in a way that permits directory traversal. The vulnerability is exacerbated by permissive CORS settings and default Docker configurations that allow unauthenticated network access. The issue is fixed in version 0.3.7.
A vulnerability in the Linux kernel's RDS (Reliable Datagram Sockets) subsystem involving the handling of RDMA connection IDs during route failure has been resolved. The flaw allowed the RDMA connection manager to destroy an ID that RDS still owned, leading to a connection state with a freed ID until shutdown. The fix ensures that the connection ID remains owned by RDS until proper shutdown, preventing use-after-free conditions.