Loading vulnerability…
A vulnerability in graphql versions 16.3.0 up to but not including 16.8.1 allows an attacker to cause Denial of Service (DoS) by submitting large queries that exploit insufficient checks in the OverlappingFieldsCanBeMergedRule.ts file. The vulnerability arises from the parser's inability to efficiently handle certain complex queries, leading to excessive resource consumption.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept (PoC) exploit for CVE-2023-26144, a denial-of-service (DoS) vulnerability in GraphQL servers (notably Apollo Server with Koa integration and graphql-js). The repository contains two main code files: - `index.mjs` sets up a minimal Apollo GraphQL server using Koa, exposing a single query (`hello`) at `http://localhost:4000`. It attempts to block overly complex queries with a plugin, but the blocking logic is only triggered after the server has already spent significant time parsing the query, making it ineffective against resource exhaustion attacks. - `graphql-js.mjs` demonstrates the exploit by sending a malicious GraphQL query with 1000+ repeated `__typename` root fields, measuring and printing the time taken to process the query. This simulates an attack that can cause the server to hang or become unresponsive. The exploit demonstrates that even with a complexity-limiting plugin, the server is vulnerable to DoS via expensive query parsing. The main attack vector is network-based, targeting the GraphQL HTTP endpoint. The repository is structured as a minimal Node.js project with all necessary dependencies specified in `package.json` and `pnpm-lock.yaml`. No hardcoded credentials or external IPs are present; the default endpoint is `http://localhost:4000` for local testing.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.