Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_typescript allows an unauthenticated attacker to read internal application data from an HTTP 500 response body.
When a typed-controller route handler returns anything other than a %Plug.Conn{}, dispatch/3 in lib/ash_typescript/typed_controller/request_handler.ex passes the value to unexpected_return/2, which interpolates inspect(value, limit: 50) directly into the response message. The limit option bounds elements per collection rather than the term as a whole, so a handler falling through with a term such as {:error, %User{}} or a changeset serialises its full field set, including hashed passwords, tokens, and tenant identifiers, into the JSON error returned to the caller.
This contradicts the module's own posture elsewhere: the rescue clause gates Exception.message/1 behind AshTypescript.typed_controller_show_raised_errors?/0 and otherwise returns a generic message, while this path is ungated and always echoes.
This issue affects ash_typescript: from 0.15.0 before 0.18.0.
Improper Input Validation vulnerability in ash-project ash_typescript allows a remote attacker to submit argument values outside a declared allowlist or bound on typed-controller routes.
AshTypescript.TypedController.RequestHandler in lib/ash_typescript/typed_controller/request_handler.ex calls Ash.Type.cast_input/3 and treats an {:ok, cast} result as fully validated. In Ash these are separate steps: cast_input/3 only coerces the term, while every constraint declared on the argument is applied by Ash.Type.apply_constraints/3, which this path never calls. Constraints such as one_of, max_length, min and max, and match are therefore inert, so a value outside a declared allowlist is accepted and passed to the route handler. Codegen renders the same constraints into the generated TypeScript types, so an allowlist appears enforced to a TypeScript caller while any other HTTP client ignores it. Empty-string to nil normalization also lives in apply_constraints, so the allow_nil?: false check accepts "" for a required argument.
Where a constraint gates a role, a status, or a sort direction, this becomes a privilege or state-machine bypass.
This issue affects ash_typescript: from 0.15.0 before 0.18.0.
EasyAdmin is a fast and modern admin generator for Symfony applications. From 4.0.0 until 4.29.16 and 5.5.1, EasyAdmin serves all backend requests through a single dashboard route and, for custom actions (Action::linkToRoute() and MenuItem::linkToRoute()), swaps the executed controller based on the routeName query parameter on the kernel.controller event. The swap happens after Symfony's security firewall has already evaluated access_control against the original dashboard URL, and the routeName value was not validated. As a result, a path-based access_control rule protecting the target route was never evaluated, so a low-privilege backend user who can reach a single EasyAdmin URL and knows a target route's name can execute that route's controller, bypassing the path-based rule. Only path-based protections are bypassed. Routes whose controller enforces its own authorization with #[IsGranted] or denyAccessUnlessGranted() remain protected because those checks are recomputed against the swapped-in controller. This issue is fixed in versions 4.29.16 and 5.5.1.
MCPHub is a unified hub for centrally managing and dynamically orchestrating multiple MCP servers/APIs into separate endpoints with flexible routing strategies. Prior to version 1.0.31, when a bearer key with accessType: 'servers' (or 'custom') is used against a group route, isBearerKeyAllowedForRequest grants access to the entire group as long as any single server in that group appears in the key's allowedServers list — not only when every server the key is scoped to matches, and critically, without ever re-checking allowedServers again once the group-level connection is authorized. A key explicitly scoped to one specific server therefore also grants full access to every other server that happens to share a group with it, including servers the key was never authorized for. This issue has been patched in version 1.0.31.
A prototype pollution vulnerability (CVE-2026-67320) was found in axios when used with the Node.js HTTP adapter. This flaw allows request interceptors to revert hardened request configurations, enabling an attacker to manipulate the Object.prototype.proxy property. Successful exploitation could allow an attacker to route plaintext HTTP requests through a malicious proxy, potentially exposing sensitive data such as authentication headers and request bodies, and even injecting malicious responses. The issue affects OpenShift Virtualization v4.12 images as distributed by Red Hat. Red Hat has released updated images to address this vulnerability.
Rodauth before version 2.47.0 has an authentication bypass vulnerability in its jwt_refresh route. This flaw allows attackers to obtain new JWT access tokens without presenting a valid refresh token by using non-POST HTTP methods. As a result, an attacker with temporary access to a token can maintain indefinite account access.
CVE-2026-77007 is a high-severity information exposure vulnerability in the HEL Online Classroom WordPress plugin up to version 1.0.3. The plugin fails to perform authorization checks on a REST API route, allowing unauthenticated users to access stored settings, including a shared secret used for signing API requests to the connected BigBlueButton server. This exposure could allow attackers to obtain sensitive information without authentication.
Portkey AI Gateway through 1.15.2 contains a server-side request forgery vulnerability in the /v1/proxy/* route that lacks requestValidator middleware. Attackers can set the x-portkey-custom-host header to internal addresses and forward requests with Authorization headers to reach internal services and exfiltrate provider API keys.
Kubeflow Pipelines versions prior to 2.17.0 contain an unauthenticated server-side request forgery (SSRF) vulnerability in the frontend proxy middleware. This flaw allows attackers to send arbitrary HTTP or HTTPS requests to internal services without authentication, bypassing authorization controls. The vulnerability arises because the proxy route does not filter or restrict target addresses and remains accessible even when authorization is enabled. Exploitation can lead to unauthorized access to sensitive internal endpoints, including cloud metadata services and Kubernetes APIs. The issue is fixed in version 2.17.0.
A vulnerability in the Quiz and Survey Master (QSM) WordPress plugin before version 11.2.4 allows users with Contributor role or higher to access question bank entries via a REST API route without proper authorization checks. This exposure includes quiz questions, hints, and correct answer keys belonging to other users.
Volmarg Personal Management System contains a path traversal vulnerability that allows authenticated attackers to read arbitrary files by supplying absolute filesystem paths to the GET /public/get-file/{path} endpoint. The path route parameter is passed directly to file_get_contents() without canonicalization against a permitted base directory, enabling attackers to retrieve sensitive files accessible to the PHP-FPM worker process without using directory traversal sequences.
CVE-2026-80426 is a high-severity cross-site scripting (XSS) vulnerability in voxel51's FiftyOne product. The vulnerability arises because the dataset field's description is rendered as raw markup using React's dangerouslySetInnerHTML without proper sanitization. This allows an attacker to inject malicious scripts that execute in the context of the application's origin. The vulnerability affects versions prior to 1.21.0. Exploitation can lead to reading local files and accessing dataset and operator endpoints via the unauthenticated media route in the open-source server.
rclone versions before 1.75.0 have a vulnerability where the pprof debug handler is mounted as its own router route, bypassing the main handler's fail-closed authentication. This allows unauthenticated attackers to access the /debug/pprof/cmdline endpoint and retrieve the full process command line arguments, which may include backend credentials.
Winter CMS versions before 1.2.13 have a local file inclusion vulnerability in the JavascriptImporter filter. Authenticated users with cms.manage_assets permission can exploit this to disclose arbitrary server-readable files by inserting =include or =require directives in theme JavaScript assets. This allows attackers to access sensitive files like .env outside the theme directory. The combined output served through the combine route is then accessible to unauthenticated visitors, exposing sensitive information such as application keys and database credentials.
Apache Camel contains an improper input validation vulnerability in its camel-mail component's MimeMultipart data format when configured with headersInline set to true. This flaw allows untrusted MIME headers to be copied as Camel message headers without filtering, potentially enabling an attacker to inject headers in the Camel-internal namespace. Such injected headers can alter the behavior of downstream route steps, depending on the route configuration. The issue affects versions from 2.17.0 before 4.14.9, from 4.15.0 before 4.18.4, and from 4.19.0 before 4.22.0. The vulnerability is fixed in Apache Camel 4.22.0, 4.14.9, and 4.18.4. Users unable to upgrade immediately should keep headersInline disabled or strip Camel-internal headers after unmarshalling.
A vulnerability in the Linux kernel's IPv4 routing code caused incorrect size estimation for route notifications when IPv6 gateways are used, potentially leading to kernel panics if panic_on_warn is enabled. This was due to fib_nlmsg_size() not accounting properly for RTA_VIA nexthops representing IPv6 gateways, causing buffer allocation errors and subsequent kernel warnings or panics.
A vulnerability in the Linux kernel's IPv6 implementation involving incorrect validation of the Route Information option length in Router Advertisements was fixed. The flaw caused the kernel to read up to 8 bytes beyond the intended option boundary, potentially exposing kernel memory contents to userspace. This occurs due to off-by-one errors in length checks against the prefix length as defined in RFC 4191. The issue was resolved by rejecting invalid option lengths that do not conform to the RFC specification.
FORT Validator versions up to 1.6.7 have an origin validation error in their RRDP processing that allows a delegated CA under the same Trust Anchor Locator to reference another CA's RRDP URLs. This can cause FORT Validator to delete the victim CA's local snapshot and silently remove validated route-origin data, potentially enabling route hijacking or loss of reachability. Version 1.6.8 includes a patch that rejects cross-origin RRDP snapshot and delta URLs. As a workaround, administrators can disable HTTP/RRDP while keeping rsync enabled, though this may cause data unavailability or staleness where rsync is unsupported.