Quick answers
- Is CVE-2026-27886 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-27886 being exploited in the wild.
- How severe is CVE-2026-27886?
- Critical severity, with a CVSS score of 7.5, published 14 May 2026.
- Which products and versions are affected?
- @strapi/strapi (npm) >= 4.0.0, < 5.37.0, SEMVER:introduced=4.0.0,fixed=5.37.0.
- Is there a fix for CVE-2026-27886?
- Yes. @strapi/strapi (npm): upgrade to 5.37.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-27886 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-27886?
- Check whether you run @strapi/strapi (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @strapi/strapi (npm): upgrade to 5.37.0 or later
npm install @strapi/strapi@5.37.0
Technical details
A vulnerability exists in Strapi's query parameter sanitization layer when filtering content via relational fields. An unauthenticated attacker can use the `where` query parameter on public Content API endpoints to traverse into the `admin_users` table via relations like `updatedBy`. By using operator chains (e.g., `$startsWith`), the attacker can perform a boolean-oracle attack based on the response count to extract sensitive fields such as `resetPasswordToken`. This allows for the reconstruction of a valid admin reset token and subsequent full account takeover. The issue is resolved in version 5.37.0 by implementing stricter query-parameter sanitization using new primitives that block unauthorized schema traversal.
Affected products
- Strapi Strapi 4.0.0 to 5.36.1
Identifiers
- CVE-2026-27886
- GHSA-rjg2-95x7-8qmx
Timeline
- 2026-05-13: advisory: GitHub advisory GHSA-rjg2-95x7-8qmx published
- 2026-05-14: disclosed: CVE-2026-27886 published to NVD
- 2026-05-14: patched: Fixed in version 5.37.0