CVE-2026-23735
Auth context mix-up in GraphQL Modules during parallel requests.
Is CVE-2026-23735 being exploited?
Not confirmed. CVE-2026-23735 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.57% probability of exploitation in the next 30 days.
How severe is CVE-2026-23735?
CVE-2026-23735 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-23735?
Yes. A fix has been recorded for CVE-2026-23735. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-23735 affect?
CVE-2026-23735 affects GraphQL Modules (Node.js) v2.2.1–v2.4.0, GraphQL Modules (Node.js) v3.0.0–v3.1.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-23735?
Upgrade to 2.4.1 or 3.1.1
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Token mix-up between parallel requests may bypass auth and expose other users' data.
Patch when possible
- affected>= 2.2.1 and < 2.4.1
- affected>= 3.0.0 and < 3.1.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.