Categories
CVE-2026-27886 high CVSS 7.5

Path Traversal in @strapi/strapi (CVE-2026-27886)

Summary

Path traversal in @strapi/strapi (CVE-2026-27886). Confidential information can be exposed externally. Exploitable via POST /admin/reset-password. Mitigation: upgrade to 5.37.0 or later.

Original description

The description as published by the source.

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: `stri…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-27886 has been found in @strapi/strapi.
Attackers can target a specific entry point like POST /admin/reset-password over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade @strapi/strapi to 5.37.0 or later.
If unsure, ask your IT team or search "@strapi/strapi CVE-2026-27886" on the vendor's site.

CVE-2026-27886 (@strapi/strapi) — CWE-22 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /admin/reset-password / where / updatedBy / admin_users
Patched: 5.37.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in @strapi/strapi. Attackers reach the vulnerable code path via POST /admin/reset-password without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @strapi/strapi. Attack surface: POST /admin/reset-password / where / updatedBy / admin_users.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 5.37.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /admin/reset-password requests with malformed payloads or SQL meta-characters. Run grep -r '@strapi/strapi' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r '@strapi/strapi' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @strapi/strapi を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect
    grep 'POST /admin/reset-password' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /admin/reset-password への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch
    Upgrade @strapi/strapi to 5.37.0

    ステージング環境で 5.37.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify
    Replay attack against POST /admin/reset-password on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm @strapi/strapi
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.37.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details