CVE-2026-97940 is a use-after-free vulnerability in the IPv6 routing code of the Linux kernel. It arises from improper handling of fib6 walker objects during route deletion, leading to potential use of freed memory. This flaw affects the IPv6 route iterator used by /proc/net/ipv6_route and BPF IPv6 route iterators. The vulnerability has been fixed in specific Linux kernel commits.
The Premium Packages – Sell Digital Products Securely plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'cart_items[][product_name]' Parameter in all versions up to, and including, 7.2.1 due to insufficient input sanitization and output escaping. 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 checkout REST route uses permission_callback set to __return_true and the invoice loader performs no order ownership check, meaning an unauthenticated attacker can both persist the payload and ensure it is renderable to any logged-in user who accesses the invoice.
TREK is a collaborative travel planner. Prior to 3.3.0, getSharedTripData in server/src/services/shareService.ts returns days, assignments, dayNotes, and places through GET /api/shared/:token even when the trip owner disables share_map. The client hides the map, but the public JSON response still includes the itinerary and place names, coordinates, addresses, descriptions, notes, and prices. Anyone holding the valid share token can therefore read location and route information that the owner explicitly chose not to share, although the random token remains required and the flaw does not permit modification. This issue is fixed in version 3.3.0.
Habitica is a habit tracker application that treats goals like a role-playing game. From 4.172.1 until 5.48.2, a query parameter on Habitica's /api/v3/groups/:groupId/members route is not sanitized before being interpreted as a regular expression. An authenticated caller can supply a computationally expensive regular expression that degrades application performance or halts Node.js processes. This issue is fixed in version 5.48.2.
In the Linux kernel, the following vulnerability has been resolved: greybus: audio: bound the topology section sizes against the fetched size gb_audio_gb_get_topology() fetches a topology blob of a module-supplied size, and gbaudio_tplg_parse_data() then walks it by adding the module-supplied size_dais, size_controls and size_widgets fields to form the control, widget and route section offsets. Those le32 sizes are never checked against the fetched blob, so a module reporting a small topology size but large section sizes makes the offsets point past the allocation, and parsing reads out of bounds. Reject a topology whose section sizes do not fit within the fetched size before it is parsed.
A race condition vulnerability in the Linux kernel's IPv6 routing exception handling was fixed by changing the iteration method over RCU-protected exception lists to use a safer iterator. The issue involved concurrent modification of route exception lists without proper locking, leading to a data race detected by Kernel Concurrency Sanitizer.
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1, is_authorized/2 for the /federation-links/.../restart route uses is_authorized_monitor (accepts the monitoring tag), while allowed_methods permits DELETE and delete_resource/2 triggers rabbit_federation_link_sup:restart. There is no per-method elevation check and no comment marking it intentional. A read-only monitoring user can restart any federation link , a state-changing operation that disrupts message flow. Preconditions include rabbitmq_federation + rabbitmq_federation_management plugins enabled Attacker has credentials with the monitoring tag. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1.
The Reachy Mini daemon exposes an HTTP API for managing the robot. Its app installation endpoint, POST /apps/install in src/reachy_mini/daemon/app/routers/apps.py, has no authentication. The handler's only dependency is Depends(get_app_manager), which just hands back the manager object from application state, so nothing in the chain ever checks a credential.
The endpoint takes an AppInfo body naming a Hugging Face Space. The daemon downloads that Space and installs it as a Python package through install_package in src/reachy_mini/apps/sources/local_common_venv.py, using uv or pip. Installing a Python package runs the package's own build and setup code, so whoever chooses the Space chooses what code the robot runs. Anyone can publish a public Hugging Face Space, so this is not a meaningful restriction on the attacker.
How far this reaches depends on the model. In _resolve_bind_host in src/reachy_mini/daemon/app/main.py the daemon binds 0.0.0.0 when it runs as the wireless version and 127.0.0.1 otherwise, with the vendor's own comment explaining that the robot has to be reachable on the LAN. On a wireless unit, then, any host on the same network can install and run code on the robot without credentials.
One related change has already shipped but does not fix this. Version 1.8.2 replaced the wildcard CORS policy with an allow list of localhost and Tauri origins. That closes the browser drive-by route, where a web page the victim visits silently calls the endpoint in the background. It has no effect on this issue: CORS is enforced by browsers and governs whether script may read a response, while a direct HTTP request from another machine on the network involves no browser, no preflight and no CORS check at all.
The Post Grid Gutenberg Blocks WordPress plugin before 5.0.41 does not perform an authorization or post-visibility check on a REST API route that returns the custom field keys of a given post, allowing unauthenticated users to disclose the custom field key names of arbitrary posts, including private, draft, pending, scheduled and password-protected posts.
The WP Recipe Maker WordPress plugin before 10.8.2 does not have any authorisation check in one of its REST routes, nor does it bound what that route stores, allowing unauthenticated users to write unlimited data into any user's metadata and to permanently prevent that account, including an administrator's, from loading.
Autonomy Logic OpenPLC 3 is susceptible to an improper neutralization of input during web page generation vulnerability when the web interface attempts to route the program based on a query string parameter with no encoding.
9Router is an AI router & token saver. Prior to 0.5.6, 9Router deployments that allow requests to reach Next.js without the sanitizing custom-server.js wrapper trust the client-supplied X-9r-Real-Ip header in src/dashboardGuard.js when isLocalRequest decides whether canAccessPublicLlmApi may skip API-key validation for /api/v1/* routes. A remote unauthenticated attacker can set X-9r-Real-Ip to 127.0.0.1 and be classified as a local client, including on the verified GET /api/v1/models route. This permits unauthorized use of the instance owner's configured LLM providers, consumption of paid credits, and enumeration of configured providers and models. This issue is fixed in version 0.5.6.
CVE-2026-93712 is a path traversal vulnerability in Dancer2 versions from 2.1.0 before 2.2.0 for Perl. The File route handler improperly serves files outside the configured public_dir by not collapsing relative path segments, allowing requests with path traversal sequences to access arbitrary readable files. This vulnerability is exploitable when the File handler is enabled and static_handler is disabled, potentially exposing sensitive files such as configuration files to unauthenticated users.
CVE-2026-93710 affects Dancer2 versions from 2.0.0 up to but not including 2.2.0. It involves improper cleanup when an exception is thrown in a hook during request dispatch. Specifically, if an exception handler halts the response without properly invoking the halt method or setting the is_halted flag, cleanup does not prevent the refused route from running, potentially causing unintended request processing. This vulnerability has a high severity score of 7.5 due to its impact on availability.
Joplin Server versions prior to 3.7.2 have an authorization bypass vulnerability in the GET /items/:id/content route. This flaw allows any authenticated user to access note or item content belonging to other users by supplying or guessing the internal server ID of those items. The vulnerability occurs because the server does not verify ownership or access rights before returning the content. This issue is fixed in version 3.7.2.
CVE-2026-77523 is an authorization bypass vulnerability in MaxKB, an open-source AI assistant for enterprise. In versions 2.10.3-lts and earlier, the model parameter form route authorizes access based on workspace path, but the underlying ModelSerializer.ModelParams loads and saves models by ID alone without verifying workspace ownership. This allows an authenticated user with read permission in an attacker-controlled workspace to access or modify model parameters in other workspaces by supplying a victim's model ID. No patch or fixed version is currently available.
CVE-2026-77518 is a missing authorization vulnerability in MaxKB, an open-source AI assistant for enterprise. In versions 2.10.2-lts and earlier, a normal workspace user can access hidden tools of other users within the same workspace by knowing the tool's MCP tool_id. This occurs because the tool-detail route lacks per-resource authorization checks, unlike the list route. The exposed tool details include Tool.code, which may contain sensitive MCP server configuration and headers. Additionally, an attacker who can create or edit workflows can misuse another user's MCP configuration by referencing their tool_id in a workflow node without permission verification. No fix is currently available for this issue.
Tinyauth is an authentication and authorization server. Prior to 5.1.2, Tinyauth compares forwarded hostnames case-sensitively while reverse proxies route equivalent hostnames case-insensitively, allowing an authenticated low-privilege user to bypass per-app access controls with a differently cased hostname. The lookup in internal/service/access_controls_service.go through lookupStaticACLs and GetAccessControls, and the Docker-label fallback in internal/service/docker_service.go through GetLabels, can miss the configured app and return an empty access-control object. internal/controller/proxy_controller.go proxyHandler then treats the empty user, group, OAuth, LDAP, and IP restrictions as permissive and returns an authenticated result for an app that should exclude the user. Unauthenticated users remain subject to login, and global login-time allowlists are not bypassed. This issue is fixed in version 5.1.2.