CVE-2026-88027

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-10. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Improper neutralization of special elements in data query logic in the embedded-document relation handling of the MongoDB integration for Laravel can cause a caller-supplied embedded record identifier to be interpreted as a query condition rather than as a literal identifier. An authenticated user who can influence such an identifier may delete all embedded documents in a targeted record or overwrite an embedded document other than the intended target.

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

September 10, 2026

Last Modified

September 10, 2026

Advisory Details (1)

Auto-updated Sep 10, 2026
No patch confirmed yet.
generic

Loading...

https://jira.mongodb.org/browse/PHPLARA-265

Vendor Advisories for CVE-2026-88027(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 29× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 06:35 UTCEG score recompute
  2. 2026-09-19 06:35 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 19:20 UTCGHSA enrichment
  5. 2026-09-18 08:05 UTCGHSA enrichment
  6. 2026-09-17 20:51 UTCEG score recompute
  7. 2026-09-17 20:51 UTCGHSA enrichment
  8. 2026-09-17 19:32 UTCEPSS rescore
  9. 2026-09-17 09:37 UTCGHSA enrichment
  10. 2026-09-16 22:23 UTCEG score recompute
  11. 2026-09-16 22:23 UTCGHSA enrichment
  12. 2026-09-16 14:09 UTCEPSS rescore
  13. 2026-09-16 10:46 UTCEG score recompute
  14. 2026-09-16 10:46 UTCGHSA enrichment
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-15 23:32 UTCGHSA enrichment
  17. 2026-09-15 12:18 UTCEG score recompute
  18. 2026-09-15 12:18 UTCGHSA enrichment
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-15 01:04 UTCGHSA enrichment
  21. 2026-09-14 13:50 UTCGHSA enrichment
  22. 2026-09-14 02:36 UTCEG score recompute
  23. 2026-09-14 02:36 UTCGHSA enrichment
  24. 2026-09-13 16:48 UTCEPSS rescore
  25. 2026-09-13 15:22 UTCGHSA enrichment
Show 16 more
  1. 2026-09-13 04:08 UTCGHSA enrichment
  2. 2026-09-12 16:54 UTCEG score recompute
  3. 2026-09-12 16:54 UTCGHSA enrichment
  4. 2026-09-12 15:02 UTCEPSS rescore
  5. 2026-09-12 05:40 UTCGHSA enrichment
  6. 2026-09-11 18:26 UTCEG score recompute
  7. 2026-09-11 18:26 UTCGHSA enrichment
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 07:12 UTCGHSA enrichment
  11. 2026-09-10 19:58 UTCGHSA enrichment
  12. 2026-09-10 19:18 UTCEG score recompute
  13. 2026-09-10 19:18 UTCGHSA enrichment
  14. 2026-09-10 18:22 UTCEG score recompute
  15. 2026-09-10 18:00 UTCEG score recompute
  16. 2026-09-10 17:59 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-88027?
CVE-2026-88027 is a high vulnerability published on September 10, 2026. Improper neutralization of special elements in data query logic in the embedded-document relation handling of the MongoDB integration for Laravel can cause a caller-supplied embedded record identifier to be interpreted as a query condition rather than as a literal identifier. An authenticated user…
When was CVE-2026-88027 disclosed?
CVE-2026-88027 was first published in the National Vulnerability Database on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-88027 actively exploited?
CVE-2026-88027 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 86.4% of all scored CVEs.
What is the CVSS score of CVE-2026-88027?
CVE-2026-88027 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-88027?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-88027, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-88027

Explore →

Is Your Infrastructure Affected by CVE-2026-88027?

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

Start Free Scan →Browse All CVEs