CVE-2026-27886

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 1.9% (80th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2026-30366 (ENISA EUVD) · GHSA-rjg2-95x7-8qmx (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 1.9%CVSS: 7.5Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.9%
EPSS %ILE
80th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 14, 2026

Last Modified

November 11, 2026

Advisory Details (1)

Auto-updated May 14, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Leaking sensitive data via relational filtering due to lack of query sanitization · Advisory · strapi/strapi · GitHub

https://github.com/strapi/strapi/security/advisories/GHSA-rjg2-95x7-8qmx

Vendor Advisories for CVE-2026-27886(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@strapi/strapi @ 5.37.0 (fixes >= 4.0.0, < 5.37.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@strapi/strapi—
  • 4.0.0 up to 5.37.0: fixed in 5.37.0
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 34× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 250 rows on record for this CVE, as 97 entries (3 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 150 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:51 UTCEPSS rescoreEPSS 1.9% · 80th percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 1.9% · 80th percentile
  3. 2026-11-11 20:38 UTCEchelonGraph re-scored
  4. 2026-11-11 20:38 UTCGHSA enrichmentGHSA-rjg2-95x7-8qmx · GitHub severity CRITICAL
  5. 2026-11-11 16:39 UTCEPSS rescoreEPSS 1.9% · 80th percentile
  6. 2026-11-10 16:43 UTCEPSS rescoreEPSS 1.9% · 80th percentile
  7. 2026-11-09 16:35 UTCEPSS rescoreEPSS 1.9% · 80th percentile
  8. 2026-11-08 18:34 UTCEchelonGraph re-scored
  9. 2026-11-08 18:34 UTCGHSA enrichmentGHSA-rjg2-95x7-8qmx · GitHub severity CRITICAL
  10. 2026-11-08 16:38 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  11. 2026-11-07 16:38 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  12. 2026-11-06 16:37 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  13. 2026-11-05 16:37 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  14. 2026-11-04 16:35 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  15. 2026-11-03 16:47 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  16. 2026-11-02 16:44 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  17. 2026-11-01 16:34 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  18. 2026-11-01 09:51 UTCGHSA enrichmentGHSA-rjg2-95x7-8qmx · GitHub severity CRITICAL
  19. 2026-11-01 07:56 UTCGHSA enrichmentGHSA-rjg2-95x7-8qmx · GitHub severity CRITICAL
  20. 2026-11-01 07:56 UTCEchelonGraph re-scored
  21. 2026-10-31 16:32 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  22. 2026-10-30 16:34 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  23. 2026-10-29 16:33 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  24. 2026-10-28 16:32 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  25. 2026-10-27 16:31 UTCEPSS rescoreEPSS 1.9% · 79th percentile
Show 72 more
  1. 2026-10-26 16:31 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  2. 2026-10-25 16:32 UTCEPSS rescoreEPSS 1.9% · 79th percentile
  3. 2026-10-25 14:38 UTCEchelonGraph re-scored
  4. 2026-10-25 01:08 UTCEchelonGraph re-scored
  5. 2026-10-24 16:32 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  6. 2026-10-23 16:31 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  7. 2026-10-22 16:34 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  8. 2026-10-21 16:32 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  9. 2026-10-20 16:32 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  10. 2026-10-19 16:31 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  11. 2026-10-18 16:31 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  12. 2026-10-18 03:50 UTCEchelonGraph re-scored
  13. 2026-10-17 16:33 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  14. 2026-10-17 16:23 UTCEchelonGraph re-scored
  15. 2026-10-16 16:41 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  16. 2026-10-15 16:31 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  17. 2026-10-14 16:32 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  18. 2026-10-13 16:34 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  19. 2026-10-12 16:33 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  20. 2026-10-12 16:17 UTCEchelonGraph re-scored
  21. 2026-10-11 19:59 UTCEchelonGraph re-scored
  22. 2026-10-11 17:12 UTCEchelonGraph re-scored
  23. 2026-10-11 14:43 UTCEchelonGraph re-scored
  24. 2026-10-11 13:48 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  25. 2026-10-10 20:00 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  26. 2026-10-09 20:07 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  27. 2026-10-08 17:11 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  28. 2026-10-07 23:47 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  29. 2026-10-06 15:17 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  30. 2026-10-05 17:42 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  31. 2026-10-04 23:21 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  32. 2026-10-03 14:25 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  33. 2026-10-01 19:49 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  34. 2026-09-30 15:03 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  35. 2026-09-30 04:58 UTCOSV refresh
  36. 2026-09-28 13:51 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  37. 2026-09-26 15:58 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  38. 2026-09-26 00:26 UTCEPSS rescoreEPSS 2.5% · 84th percentile
  39. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  40. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  41. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  42. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  43. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  44. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  45. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  46. 2026-09-11 07:53 UTCOSV refresh
  47. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  48. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  49. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  50. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  51. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  52. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  53. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  54. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  55. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  56. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  57. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  58. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  59. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  60. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  61. 2026-08-23 17:38 UTCEchelonGraph re-scored
  62. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  63. 2026-08-22 01:50 UTCEchelonGraph re-scored
  64. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  65. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  66. 2026-08-20 19:35 UTCEchelonGraph re-scored
  67. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  68. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  69. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  70. 2026-08-17 10:22 UTCEchelonGraph re-scored
  71. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  72. 2026-08-16 03:56 UTCEchelonGraph re-scored

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (1 GitHub PoC), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Nucleijavascript/cves/2026/CVE-2026-27886.yaml
    Published Sep 22, 2026

    Strapi <=5.36.x - Admin Credential Enumeration

    Open source ↗
  • GitHub PoCthesw0rd/CVE-2026-27886-PoC-Account-Takeover
    Published Jun 8, 2026

    Account takeover full PoC for CVE-2026-27886 in Strapi CMS

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-27886?
CVE-2026-27886 is a high-severity vulnerability; its CVE record was published on May 14, 2026. 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…
When was the CVE record for CVE-2026-27886 published?
The CVE record for CVE-2026-27886 was published on May 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 11, 2026; the record at its source may have been updated since.
Is CVE-2026-27886 actively exploited?
CVE-2026-27886 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.9% probability of exploitation in the next 30 days (80th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-27886?
CVE-2026-27886 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-27886?
A fix for CVE-2026-27886 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-27886 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-27886

Explore →

Is Your Infrastructure Affected by CVE-2026-27886?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs