CVE-2026-88027 is a high severity query injection flaw in Laravel MongoDB, scored 7.1. The record does not name a fixed version. Check your installed version against the affected list below, then patch or restrict access until you can. The record does not flag it as exploited.
What's affected
- The MongoDB integration for Laravel (mongodb/laravel-mongodb), in its embedded-document relation handling.
- The record does not list version ranges.
Severity in the record: High (7.1), vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L. Weakness: CWE-943.
Fix: The record does not name a fixed version. Check the MongoDB Jira ticket PHPLARA-265.
How to check if you're exposed
- Check your installed version:
composer show mongodb/laravel-mongodb. - Search your code for embedded relations (embedsMany, embedsOne):
grep -rn embeds app/. - Find places where a user-supplied identifier reaches those relations.
Run these on every host, image and build that could carry the component. Dependency files in repositories and base images in registries are easy to miss.
What to do now
- Confirm the version of every affected system using the checks above.
- Read the vendor advisory linked in Sources and note the fixed version for your release line.
- Schedule the update, starting with systems that face untrusted networks or hold the most sensitive data.
- In the meantime: cast identifiers to strings or validated types before they reach embedded relation calls.
- Record the change, then recheck the version to confirm it took effect.
Why it matters
A caller-supplied embedded record identifier can be read as a query condition instead of a literal value. This is CWE-943, the NoSQL counterpart of SQL injection. An authenticated user who can influence the identifier could delete every embedded document in a targeted record or overwrite one other than the intended target.
The record's KEV flag is false, so this post makes no claim that the flaw is exploited in the wild. That can change, so recheck the CISA catalog from time to time.
Libraries like this often arrive as transitive dependencies, so the version in your lockfile may not be one you chose. Safeguard's free in-browser dependency scan can show whether the package is in a project, and reachability analysis helps separate code paths that call the weak function from those that never do.
The vector string in the record is a compact summary of how the flaw is reached and what it costs. AV is the attack vector (network, adjacent or local), PR is the privilege the attacker needs, and the C, I and A letters give the impact on confidentiality, integrity and availability. Read it against your own network layout rather than relying on the score alone.
After you patch
Patching is not the end of the job. Recheck the version on each system, because an upgrade that failed or rolled back looks the same as a success until someone looks. Keep the advisory link with your change record so the next reviewer can see why the update happened.
If you cannot patch soon, write down the reason, the compensating control you chose and a date to revisit. Exceptions without a date tend to become permanent.
Quick check
Does this need a logged-in user?
Yes. The record says an authenticated user who can influence the identifier.
Sources
-
MongoDB Jira: PHPLARA-265
-
Safeguard Gold: CVE-2026-88027
Last reviewed: 18 October 2026.
