How severe is GHSA-rjg2-95x7-8qmx?

No CVSS score has been assigned to GHSA-rjg2-95x7-8qmx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rjg2-95x7-8qmx?

GHSA-rjg2-95x7-8qmx affects the following packages: @strapi/strapi (npm). Ecosystems affected: npm.

How do I fix GHSA-rjg2-95x7-8qmx?

Update @strapi/strapi to 5.37.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rjg2-95x7-8qmx is resolved across your whole dependency graph.

How do I detect GHSA-rjg2-95x7-8qmx in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @strapi/strapi. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-rjg2-95x7-8qmx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-rjg2-95x7-8qmx?

O3 pinpoints whether GHSA-rjg2-95x7-8qmx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-rjg2-95x7-8qmx actively exploited in the wild?

No public exploit code has been indexed for GHSA-rjg2-95x7-8qmx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-rjg2-95x7-8qmx published, and has it been updated?

GHSA-rjg2-95x7-8qmx was published on May 14, 2026 and was last updated on May 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-rjg2-95x7-8qmx

GHSA-rjg2-95x7-8qmx is a security vulnerability in @strapi/strapi. O3 Security confirms whether GHSA-rjg2-95x7-8qmx is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Strapi may leak sensitive data via relational filtering due to lack of query sanitization

Also known asCVE-2026-27886

Published

May 14, 2026

Updated

May 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of May 16, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

@strapi/strapinpm

180Kdownloads / week

Description

Summary of CVE-2026-27886 Vulnerability Details

CVE: CVE-2026-27886
CVSS v3.1 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 (9.3 — Critical)
Affected Versions: @strapi/strapi <=5.36.1
How to Patch: Immediately update your Strapi to >=5.37.0

Description of CVE-2026-27886

Strapi versions 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 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.

IoC's for CVE-2026-27886

Indicators that an instance running an unpatched version may have been exploited:

Server access logs containing query strings traversing into admin-relation private fields. Regex: \?(.*&)?where\[(updatedBy|createdBy|publishedBy)\]\[(email|password|resetPasswordToken|confirmationToken|firstname|lastname|preferedLanguage)\]\[\$(startsWith|contains|eq|gt|lt|ge|le|in|notIn|notNull|null)\]=
High volume of public Content API requests from a single IP iterating through a hex alphabet (0-9, a-f) on the same content-type endpoint with progressively-longer filter values
Subsequent POST /admin/reset-password calls using a reset token that the legitimate admin did not request
Successful admin password change immediately following a burst of public Content API requests with where[updatedBy] query parameters
Sustained burst of identical-shape requests with only the trailing character of the filter value varying

Credit

Discovered by: James Doll - WildWest CyberSecurity Contact: [email protected] Website: https://wildwestcyber.com LinkedIn: https://www.linkedin.com/in/james-doll-273a61243

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@strapi/strapi`	≥ 4.0.0&&< 5.37.0	5.37.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @strapi/strapi. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @strapi/strapi to 5.37.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rjg2-95x7-8qmx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-rjg2-95x7-8qmx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-rjg2-95x7-8qmx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary of CVE-2026-27886 Vulnerability Details - CVE: CVE-2026-27886 - CVSS v3.1 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` (9.3 — Critical) - Affected Versions: `@strapi/strapi` <=5.36.1 - How to Patch: Immediately update your Strapi to >=5.37.0 ### Description of CVE-2026-27886 Strapi versions 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) fie

O3 Security · Impact-Aware SCA

Is GHSA-rjg2-95x7-8qmx in your dependencies?

O3 detects GHSA-rjg2-95x7-8qmx across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works