ApostropheCMS versions prior to 3.7.0 in the import-export module contain an improper access control vulnerability. Authenticated users with import access can manipulate update-key values to match existing documents they have generic edit permissions on, potentially modifying unintended content. The vulnerability is mitigated by existing permission filters, preventing unauthorized overwrites of protected content. This issue is resolved in version 3.7.0.
Tandoor Recipes versions prior to 2.6.10 contain a vulnerability where unvalidated user input is passed into Django ORM order_by() calls, allowing authenticated users to supply foreign-key traversal paths in ordering parameters. This improper neutralization of special elements in data query logic can lead to leakage of sensitive related user data such as password hashes, email addresses, and administrator status. The issue is fixed in version 2.6.10.
Plane, an open-source project management tool, has a vulnerability prior to version 1.4.0 where multiple issue-listing endpoints improperly handle the user-controlled order_by parameter. This allows attackers to use double-underscore relationship traversal to access arbitrary related model fields, potentially revealing database schema details and some field values. The issue is fixed in version 1.4.0.
CVE-2026-106119 is a vulnerability in langchainjs's MongoDBChatMessageHistory component where session identifiers are not properly validated at runtime. This allows specially crafted session identifiers to be interpreted as MongoDB query conditions instead of literal strings. An attacker able to invoke chat-history operations could potentially read, modify, or delete other users' conversation histories if multiple users' data share the same collection. The issue is fixed in @langchain/mongodb version 1.3.1 and later.
LangChain is a framework for building LLM-powered applications. Prior to 1.1.1, @langchain/redis does not escape attacker-controlled values in structured RediSearch TAG filters and structured RediSearch TEXT filters, allowing injected RediSearch syntax to alter or broaden the generated search query. When an application uses an attacker-influenceable filter as a tenant or document-access boundary, the modified query can expose indexed documents outside the attacker's intended scope. This issue is fixed in version 1.1.1.
A vulnerability in Ghost, a Node.js content management system, allowed unauthorized access to comments due to improper input validation. This issue affected versions from 5.9.0 up to but not including 6.44.1 and was fixed in version 6.44.1.
A vulnerability in TryGhost Ghost versions 4.39.0 up to 6.64.0 allowed staff users with permission to view staff invites to discover secret tokens of pending invites, including those for roles with higher privileges. This could enable privilege escalation by accepting such invites. The issue is fixed in version 6.64.0.
CVE-2026-105652 is a low-severity vulnerability in TryGhost Ghost versions from 0.7.2 up to but not including 6.64.0. It allows any staff-level user to observe the relative ordering of other staff users' hashed passwords. This information disclosure does not reveal the actual password hashes nor does it provide a practical method to recover passwords. The issue is fixed in version 6.64.0.
CVE-2026-104956 is a medium severity vulnerability in the open-source project management tool Plane prior to version 1.4.0. The unauthenticated public issues endpoint improperly handles the group_by and sub_group_by query parameters by passing them without validation to ORM field operations. This allows an anonymous attacker to trigger unhandled errors causing HTTP 500 responses or perform blind ORM relational path traversals. The vulnerability does not disclose data directly and is fixed in Plane version 1.4.0.
djehuty is a research data repository system developed by 4TU.ResearchData. Prior to version 26.3.2, An unauthenticated attacker can inject SPARQL into the search/listing queries through three separate parameters. Because the affected queries are read (SELECT) queries, this does not write to the store, but it allows: Cross-graph data exfiltration — e.g. UNION-ing in triples from graphs the request was never scoped to (drafts/private/internal data held in the RDF store); denial of service — expensive or malformed queries that tie up the SPARQL backend / web workers. No account or user interaction is required. This issue has been patched in version 26.3.2.
CVE-2026-73975 is a high-severity vulnerability in the 4TUResearchData djehuty research data repository system. Before version 26.3.2, authenticated depositors can inject arbitrary SPARQL commands into state-modifying queries by manipulating the session name. This allows them to write or delete arbitrary triples anywhere in the shared RDF store, compromising the integrity of the entire repository metadata. The vulnerability requires a logged-in account, but self-registration via ORCID or SAML lowers the barrier to exploitation. The issue has been fixed in version 26.3.2.
CVE-2026-81914 is a medium severity vulnerability in the Apache Airflow Google provider where Google Drive search queries improperly handle special characters in file and folder names. Specifically, names containing apostrophes are not escaped, allowing an attacker controlling these names to inject additional clauses into the query. This can cause the system to select attacker-controlled files or folders during upload or download operations, potentially redirecting data flows. The issue affects versions prior to 22.6.0. Upgrading to version 22.6.0 or later mitigates the vulnerability by properly escaping special characters in queries.
Parse Server is an open source backend server. In versions prior to 8.6.90 and in versions from 9.0.0 prior to 9.10.1-alpha.9, the device token deduplication logic for installation records does not validate the type of client-supplied installation fields before using them to build database queries. An unauthenticated remote attacker who knows only the public application ID can submit non-string values in these fields to inject query operators, causing the deduplication cleanup — which runs with elevated privileges before class-level permissions are evaluated — to delete every device registration in the application or an attacker-chosen subset of them. No account, session token, master key, or user interaction is required. Deleted registrations cannot be recovered on the server, so push notifications cannot be delivered until every client re-registers. Any deployment that exposes the REST API to clients and uses push notifications is affected in its default configuration. Versions 8.6.90 and 9.10.1-alpha.9 fix the issue by rejecting non-string values with a client error and by scoping the deduplication cleanup to the calling application. No workaround other than upgrading is available.
Rapid7 Bulk Export MCP versions 0.2.5 through 0.6.1 suffer from a GraphQL query injection issue in the export-status component (`get_export_status` in `src/export_manager.py`), whereby the `export_id` value — an unvalidated MCP tool argument reaching the function via the `check_rapid7_export_status` and `download_rapid7_export` tools — is interpolated directly into the GraphQL query string. A crafted `export_id` containing quote and brace characters can terminate the intended `export(id: "...")` selection early and append attacker-controlled root-level selections (for example, schema introspection), producing a single well-formed GraphQL document that is then sent to the Rapid7 export API under the operator's own API key.
Notably, this issue does not grant an existing actor any access they do not already have: every injected query executes within the operator's own already-authenticated API scope, using the operator's own valid API key, and cannot cross a tenant or account boundary. A directly-malicious operator gains nothing they could not already do by calling the API directly; the realistic exposure is limited to a compromised or careless upstream MCP client, or indirect prompt injection forwarding an unvalidated identifier. This is fixed in version 0.6.2, which passes `export_id` as a parameterized GraphQL variable (`$exportId: ID!`).
Improper neutralization of special elements in data query logic in the cache lock implementation of the MongoDB integration for Laravel can cause a caller-supplied lock owner value to be evaluated as an aggregation expression rather than as a literal value. An authenticated user who can influence the owner value an application uses when acquiring or restoring a lock may take over or prematurely expire a lock held by another process, which can lead to duplicated or conflicting operations.
Mongoid does not restrict which query operators may come from caller-supplied filter data when an application hands that data to its query-building methods. In an application that forwards externally supplied filter parameters in this way, a party with no credentials may influence how the database evaluates the query. This may result in unintended disclosure of stored field values and in reduced database performance.
LangChain MongoDB provides integrations between MongoDB, Atlas, LangChain, and LangGraph. Prior to langgraph-checkpoint-mongodb 0.3.0 and langgraph-store-mongodb 0.4.0, MongoDBSaver.list(), MongoDBSaver.alist(), and MongoDBStore.search() incorporate filter dictionaries into MongoDB queries without recursively rejecting keys prefixed with $. An authenticated caller who controls a filter argument through HTTP query parameters, request body fields, or agent tool arguments can inject MongoDB Query Language operators such as $regex or $where. In a multi-tenant deployment that uses the filter to enforce per-user or per-tenant isolation, injected operators can bypass intended equality filtering and expose other tenants' checkpoint or store data. Filters constructed entirely from trusted server-side values have lower practical risk. This issue is fixed in langgraph-checkpoint-mongodb 0.3.0 and langgraph-store-mongodb 0.4.0.
CVE-2026-88036 is a vulnerability in the GridFS component of the MongoDB C Driver where improper neutralization of special elements in data query logic allows an authenticated user to manipulate a structured file identifier. This can lead to unauthorized access to stored file content beyond the intended target or deletion of all GridFS file chunks in the affected bucket, making stored files unreadable. The issue affects specific versions of the MongoDB C Driver and has a medium severity rating with a CVSS score of 6.1.
CVE-2026-88033 is a vulnerability in the GridFS component of the MongoDB Java Driver where improper neutralization of special elements in data query logic allows an attacker to manipulate file identifiers. An authenticated user who can influence the identifier may access unintended stored file content, cause deletion of all GridFS file chunks in a bucket, or rename files other than the intended target. This affects versions from 3.3.0 up to but not including 5.11.1. The vulnerability has a medium severity with a CVSS score of 6.1.
A vulnerability in the MongoDB integration for Laravel allows improper neutralization of special elements in polymorphic relation handling. This flaw can cause a caller-supplied relation identifier to be treated as a query condition instead of a literal identifier. An authenticated user able to influence a stored relation identifier may cause the application to return unintended documents. The vulnerability has a CVSS score of 6.5, indicating high severity.