A security flaw has been discovered in TimBroddin astro-mcp-server up to 1.1.1. The impacted element is an unknown function of the file src/index.ts of the component MCP Tool Query Construction. Performing a manipulation of the argument request.params.arguments results in sql injection. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.
Sensitive server_token exposed via GET parameter in V2Board thru 1.7.4. In app/Http/Controllers/Server/UniProxyController.php, the server authentication token is accepted via GET parameter transmission. The token appears in URLs such as /api/v1/server/UniProxy/user?token=SECRET, causing it to be recorded in web server access logs, browser history, HTTP Referer headers, and proxy/CDN logs. An attacker who gains access to any log source can extract the token and impersonate a proxy server node, potentially intercepting all user traffic.
Chartbrew version 4.9.0 contains a missing authorization vulnerability in the POST /api/chart/:chart_id/query endpoint. This endpoint does not require authentication and only checks a team-level permission without verifying if the chart is public or if sharing policies allow access. As a result, an unauthenticated attacker who knows a chart ID can trigger data refreshes and access data from private charts. This vulnerability has been fixed in version 5.0.0.
A vulnerability in the assisted-service REST API, an optional Assisted Installer (assisted-service) component in the Multicluster Engine (MCE), allows an authenticated user with minimal namespace-scoped privileges to obtain administrative credentials for arbitrary clusters provisioned through the hub.
The credentials download endpoint (GET /v2/clusters/{cluster_id}/credentials, which returns the kubeadmin password) and the kubeconfig download endpoint are operational in AUTH_TYPE=local mode, the only authentication mode available in on-premises ACM/MCE hub deployments. The local authenticator unconditionally grants full administrative access to any request bearing a valid JWT, with no per-endpoint restrictions. A valid local JWT is embedded as a plaintext query parameter in InfraEnvStatus.ISODownloadURL and is readable by any user who has get rights on an InfraEnv object in their own namespace.
The affected components ship as part of Multicluster Engine (MCE). The Red Hat Advanced Cluster Management (ACM) deployments that include MCE are equally affected.
This issue does not affect the hosted SaaS offering (console.redhat.com), which uses a different authentication mode.
Successful exploitation gives the attacker the kubeadmin password and kubeconfig for any OpenShift cluster provisioned through the affected hub, granting unrestricted root-level administrative access to those spoke clusters.
Fiber v3 cache middleware's default key generator uses only the request path, ignoring the query string. This causes distinct requests with different query parameters to share the same cached response, leading to response mix-up. Such behavior can leak or corrupt user-specific content when responses depend on query parameters. The issue affects versions prior to 3.2.0 and has been fixed in version 3.2.0.
A vulnerability was detected in JoeCastrom mcp-chat-studio up to 1.5.0. Affected by this issue is some unknown functionality of the file server/routes/llm.js of the component LLM Models API. Performing a manipulation of the argument req.query.base_url results in server-side request forgery. Remote exploitation of the attack is possible. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.
Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in Apache Camel Camel-Coap component.
Apache Camel's camel-coap component is vulnerable to Camel message header injection, leading to remote code execution when routes forward CoAP requests to header-sensitive producers (e.g. camel-exec)
The camel-coap component maps incoming CoAP request URI query parameters directly into Camel Exchange In message headers without applying any HeaderFilterStrategy.
Specifically, CamelCoapResource.handleRequest() iterates over OptionSet.getUriQuery() and calls camelExchange.getIn().setHeader(...) for every query parameter. CoAPEndpoint extends DefaultEndpoint rather than DefaultHeaderFilterStrategyEndpoint, and CoAPComponent does not implement HeaderFilterStrategyComponent; the component contains no references to HeaderFilterStrategy at all.
As a result, an unauthenticated attacker who can send a single CoAP UDP packet to a Camel route consuming from coap:// can inject arbitrary Camel internal headers (those prefixed with Camel*) into the Exchange. When the route delivers the message to a header-sensitive producer such as camel-exec, camel-sql, camel-bean, camel-file, or template components (camel-freemarker, camel-velocity), the injected headers can alter the producer's behavior. In the case of camel-exec, the CamelExecCommandExecutable and CamelExecCommandArgs headers override the executable and arguments configured on the endpoint, resulting in arbitrary OS command execution under the privileges of the Camel process.
The producer's output is written back to the Exchange body and returned in the CoAP response payload by CamelCoapResource, giving the attacker an interactive RCE channel without any need for out-of-band exfiltration.
Exploitation prerequisites are minimal: a single unauthenticated UDP datagram to the CoAP port (default 5683). CoAP (RFC 7252) has no built-in authentication, and DTLS is optional and disabled by default. Because the protocol is UDP-based, HTTP-layer WAF/IDS controls do not apply.
This issue affects Apache Camel: from 4.14.0 through 4.14.5, from 4.18.0 before 4.18.1, 4.19.0.
Users are recommended to upgrade to version 4.18.1 or 4.19.0, fixing the issue.
CVE-2026-41328 is a critical vulnerability in dgraph-io dgraph versions prior to 25.3.3. It allows an unauthenticated attacker to gain full read access to all data in the database if Access Control Lists (ACL) are not enabled. The issue arises from improper neutralization of special elements in data query logic, enabling injection of malicious Dgraph Query Language payloads via crafted HTTP POST requests. This vulnerability is fixed in version 25.3.3.
CVE-2025-61726 is a vulnerability in the Go standard library net/url package used by Red Hat Web Terminal Operator 1.11.0. The flaw allows an attacker to send an HTTP request with a large number of unique query parameters, causing excessive memory consumption and potentially crashing the application or making it unresponsive, resulting in a denial of service. There is no impact on confidentiality or integrity. Red Hat has not identified a practical mitigation other than updating the affected package. No fix has been released yet.
STIG Manager versions 1.5.10 through 1.6.7 contain a reflected Cross-Site Scripting (XSS) vulnerability in the OIDC authentication error handling code. The vulnerability arises because the 'error' and 'error_description' query parameters are inserted into the DOM without proper HTML escaping, allowing execution of arbitrary JavaScript. This is particularly dangerous if the user has an active STIG Manager session in another tab, as the injected script can interact with the SharedWorker managing authentication tokens, enabling unauthorized API requests. The issue is fixed in version 1.6.8.
CVE-2026-41175 is a high-severity vulnerability in Statamic CMS versions prior to 5.73.20 and 6.13.0 involving unsafe reflection (CWE-470). It allows manipulation of query parameters on Control Panel and REST API endpoints or GraphQL queries to delete content, assets, and user accounts. Exploitation via the Control Panel requires authentication with minimal permissions, while REST and GraphQL API exploitation requires these APIs to be explicitly enabled without authentication. The vulnerability has been fixed in versions 5.73.20 and 6.
CVE-2026-41145 is an authentication bypass vulnerability in MinIO's object storage system affecting versions from RELEASE.2023-05-18T00-05-36Z up to but not including RELEASE.2026-04-11T03-20-12Z. The flaw allows an attacker with a valid access key but without the secret key or valid signature to write arbitrary objects to any bucket. The vulnerability arises from improper signature verification when credentials are supplied via the query string without the Authorization header. This impacts standard and multipart upload handlers. A fixed release is available, and mitigation includes upgrading or blocking specific unsigned-trailer requests at the load balancer or WAF layer.
Vendure versions prior to 2.3.4, 3.5.7, and 3.6.2 contain an unauthenticated SQL injection vulnerability in the Shop API due to unsafe interpolation of a user-controlled query string parameter. This allows attackers to execute arbitrary SQL commands on the database. The Admin API is also vulnerable but requires authentication for exploitation. Vendure has released patched versions that fix this by parameterizing queries and providing a hotfix that validates the languageCode input to block injection attempts.
NanoMQ versions prior to 0.24.11 contain a heap-based buffer overflow vulnerability in the REST API's uri_param_parse function. The flaw is due to an off-by-one error in memory allocation for query parameter keys and values, allowing a crafted HTTP request to write a null byte beyond the allocated buffer. This vulnerability is remotely triggerable without authentication. Version 0.24.11 addresses and fixes this issue.
Hot Chocolate is an open-source GraphQL server. Prior to versions 12.22.7, 13.9.16, 14.3.1, and 15.1.14, Hot Chocolate's recursive descent parser `Utf8GraphQLParser` has no recursion depth limit. A crafted GraphQL document with deeply nested selection sets, object values, list values, or list types can trigger a `StackOverflowException` on payloads as small as 40 KB. Because `StackOverflowException` is uncatchable in .NET (since .NET 2.0), the entire worker process is terminated immediately. All in-flight HTTP requests, background `IHostedService` tasks, and open WebSocket subscriptions on that worker are dropped. The orchestrator (Kubernetes, IIS, etc.) must restart the process. This occurs before any validation rules run — `MaxExecutionDepth`, complexity analyzers, persisted query allow-lists, and custom `IDocumentValidatorRule` implementations cannot intercept the crash because `Utf8GraphQLParser.Parse` is invoked before validation. The `MaxAllowedFields=2048` limit does not help because the crashing payloads contain very few fields. The fix in versions 12.22.7, 13.9.16, 14.3.1, and 15.1.14 adds a `MaxAllowedRecursionDepth` option to `ParserOptions` with a safe default, and enforces it across all recursive parser methods (`ParseSelectionSet`, `ParseValueLiteral`, `ParseObject`, `ParseList`, `ParseTypeReference`, etc.). When the limit is exceeded, a catchable `SyntaxException` is thrown instead of overflowing the stack. There is no application-level workaround. `StackOverflowException` cannot be caught in .NET. The only mitigation is to upgrade to a patched version. Operators can reduce (but not eliminate) risk by limiting HTTP request body size at the reverse proxy or load balancer layer, though the smallest crashing payload (40 KB) is well below most default body size limits and is highly compressible (~few hundred bytes via gzip).
WeGIA is a web manager for charitable institutions. Versions prior to 3.6.10 contain a SQL injection vulnerability in dao/memorando/UsuarioDAO.php. The cpf_usuario POST parameter overwrites the session-stored user identity via extract($_REQUEST) in DespachoControle::verificarDespacho(), and the attacker-controlled value is then interpolated directly into a raw SQL query, allowing any authenticated user to query the database under an arbitrary identity. Version 3.6.10 fixes the issue.
CVE-2026-6490 is a medium severity SQL injection vulnerability in the QueryMine sms product affecting an unknown function in admin/deletecourse.php via the GET request parameter 'ID'. This vulnerability allows remote attackers to manipulate the SQL query, potentially compromising the database. The exploit code has been publicly disclosed. The vendor has not responded to the disclosure and no official patch or remediation guidance is currently available. The product uses a rolling release model, so specific affected or fixed versions are not clearly identified.