Missing network timeouts in the Linux builds of Progressive Robot hMailServer 6.3.0 through 6.3.5 allow a remote attacker to hold server threads indefinitely and so stop outbound mail delivery (denial of service). The server set its socket timeouts in the form Windows takes, which Linux refuses, and its HTTPS clients read without a deadline, so a peer that accepts a connection and then sends nothing held the waiting thread for as long as the connection stayed open. The MTA-STS policy fetch, enabled by default, is made during outbound delivery to mta-sts.<recipient domain>, so anyone who can make the server deliver mail to a domain they control - for example as the envelope sender of a message that bounces - can hold delivery threads until outbound delivery stops. The same flaw affects the DANE TLSA query, the OAuth2 token request, the ACME client, and the ManageSieve and metrics listeners, which a silent client stops from serving anyone else. Windows builds are not affected.
Brocade SANnav versions before 3.0.0a contain an SQL Injection vulnerability in several external API inventory query parameters. This flaw allows an authenticated attacker to inject malicious data via REST API queries. The vulnerability requires authentication and has a medium severity rating. No known exploits are reported in the wild. No patch or remediation details are currently provided.
An out-of-bounds memory read vulnerability exists in the web management daemon of Brocade Fabric OS versions before 10.0.1. Unauthenticated HTTP endpoints process specific URL query parameters without validating array index boundaries or performing numerical range checks. An unauthenticated remote attacker can exploit this issue by sending a single, crafted HTTP request containing extreme numerical values in the query string. This causes an invalid memory dereference, resulting in a crash of the web management process (Denial of Service) and potential temporary management-plane disruption.
Missing authorization checks in Amazon Athena engine version 3 request handling could have allowed an authenticated user to read limited query metadata (AWS account identifiers and SQL statement text) from other AWS accounts. Query results, credentials, and Amazon S3 data were not affected. AWS remediated the issue on September 1, 2026, and has confirmed no customer metadata was accessed. No customer action is required.
An unauthenticated SQL injection vulnerability exists in the OrdaSoft Simple Membership extension for Joomla versions 1.0.0 through 7.4.0. The vulnerability occurs because the extension's site/simplemembership.php script dispatches the task=checkLoginPass without any authentication or access control. It reads a login request parameter using Joomla's generic input filter, which does not sanitize quotes or SQL syntax, and directly concatenates this input into an SQL query without escaping or parameterization.
CVE-2026-104047 is a vulnerability in SSSD on Red Hat Enterprise Linux 10 when configured to use Microsoft Entra ID. It allows a local user with low privileges to submit crafted lookup requests that manipulate directory query filters, potentially causing unauthorized disclosure of directory information. This issue requires explicit non-default configuration and does not enable code execution or privilege escalation.
CVE-2026-106033 is a DOM-based Cross-Site Scripting (XSS) vulnerability in Red Hat Ansible Automation Platform 2's UI redirect route. The vulnerability arises because the application assigns the 'next' query parameter directly to the browser's location.href without proper validation, bypassing built-in URL validation controls. An attacker can craft a malicious link that, when visited by an authenticated user, executes arbitrary JavaScript in the user's session context. Exploitation requires user interaction and authentication, limiting the impact to moderate severity.
### Impact
An attacker who has read plus create or update access to a collection can submit a request that includes a SQL injection targeting a specific field path shape and operators in Payload's SQLite and Postgres.
#### You are affected if:
- You use `@payloadcms/db-sqlite` or `@payloadcms/db-d1-sqlite`.
- You use `@payloadcms/db-postgres` or `@payloadcms/db-vercel-postgres` `< 3.73.0`.
- A readable collection has a `json` field, or a` blocks` field with `blocksAsJSON: true`.
- The attacker has read plus create or update access on it.
#### You are not affected if:
- You have no `json or `blocksAsJSON` fields. `richText` is not affected.
- You run a patched version.
### Patches
The patched version sanitizes the query input to prevent injection.
Users should upgrade Payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`.
### Impact
A user can submit a request that exploits a SQL Injection vulnerability in Payload.
You are affected if:
- You use an affected Payload version.
- Untrusted users can query readable collections using dynamic filters or joins.
You are not affected if you use MongoDB (`@payloadcms/mongodb`).
### Patches
Users should upgrade Payload packages to `>= 3.88.0` or `>= 4.0.0-canary.27`.
### Workarounds
Upgrading to a patched version is recommended. Until you can upgrade, restrict untrusted users from supplying dynamic query filters or join parameters and limit read access to affected collections.
### Impact
Under certain conditions, sorting readable records could reveal limited information about fields the requester was not permitted to read.
You are affected if untrusted users can query a collection, control its sorting, and sort by protected fields.
### Patches
Payload now applies field-level access checks to sort fields before executing queries.
Users should upgrade to `>= 3.88.0` or `>= 4.0.0-canary.27`.
### Workarounds
Upgrading is recommended. Until then, prevent untrusted users from controlling sort parameters or restrict their access to affected collections.
CVE-2026-103261 is a denial-of-service vulnerability in Tornado 6.5.8 where the HTTPServerRequest.__init__ method parses query strings without limiting the number of fields. This allows an attacker to send a GET request with thousands of query parameters, causing excessive CPU usage and stalling Tornado's single-threaded event loop. The flaw is due to missing a max_num_fields limit on query string parsing, unlike the POST body parsing which has a 1000-field cap. This leads to event-loop blocking and degraded response times for all clients sharing the same IOLoop. The issue is fixed in Tornado 4.6.4 by adding a 1000-field limit and proper error handling.
vLLM versions prior to 0.30.0 have an authorization bypass vulnerability in the /score and /rerank endpoints. The issue arises because the query_key used for scoring is derived from the user-controlled X-Request-Id header. This allows an attacker to reuse a victim's identifier in concurrent requests, causing the victim's documents to be scored against the attacker's query and potentially triggering cache-miss errors. The vulnerability is fixed in version 0.30.0.
Plane is an open-source project management tool. Prior to 1.4.0, the V2 issue-attachment PATCH endpoint accepts issue_id in the URL but omits it from the database query. A project member can use an issue_id they control in the URL while targeting another user's attachment by its pk UUID. Because the server matches only pk, workspace, and project_id, it modifies the attachment regardless of the issue_id in the URL. When the attachment is pending and has not been confirmed as uploaded, the PATCH handler sets created_by = request.user and transfers attachment ownership to the attacker. This issue is fixed in 1.4.0.
The alexpechkarev/google-maps Laravel package versions 1.0.3 through 12.16 disables TLS certificate verification by default due to the bundled configuration setting ssl_verify_peer to FALSE. This allows on-path attackers to present any certificate, intercept Google Maps web-service requests, steal API keys from query strings, and tamper with responses.
The Ivory Search – WordPress Search Plugin plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 's' parameter in all versions up to, and including, 5.5.18 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. Exploitation requires that the targeted search form has the 'Highlight Search Terms' option enabled by an administrator, and that the malicious search query returns at least one post result.
The SupportCandy – AI Customer Support Ticket System & Live Chatbot Agent plugin for WordPress is vulnerable to time-based SQL Injection via the 'sort_by' parameter in all versions up to, and including, 3.5.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with custom-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires the authenticated attacker to hold both a Subscriber-level (or higher) WordPress role and a SupportCandy Agent account with the 'Assign Agents' permission configured.
The Beaver Builder Page Builder – Drag and Drop Website Builder plugin for WordPress is vulnerable to blind SQL Injection via 'fields[][value]' Parameter in all versions up to, and including, 2.11.0.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The vulnerable get_autosuggest_values AJAX endpoint is reachable by any Contributor who owns a draft post, as the required fl_ajax_update nonce is emitted into the block editor for any user who can edit a Beaver Builder post type.
WP Statistics plugin for WordPress versions up to and including 14.16.14 is vulnerable to reflected Cross-Site Scripting (XSS) via the REQUEST_URI query-parameter key. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary scripts that execute when a user clicks a crafted link.
The W3 Total Cache WordPress plugin versions up to and including 2.10.6 contain a stored cross-site scripting (XSS) vulnerability. This flaw arises from improper input sanitization and output escaping in the handling of comment content when the 'Remove query strings from static resources' option is enabled. An unauthenticated attacker can inject malicious scripts that execute in the context of users visiting the affected pages. The vulnerability requires a specific configuration setting to be enabled to be exploitable.