CVE & CISA-KEV Catalog

CVE-2026-55253

HIGH
7.7
CVSS v3
NVD

Description

LangChain MongoDB provides integrations between MongoDB, Atlas, LangChain, and LangGraph. Prior to langgraph-checkpoint-mongodb 0.3.0 and langgraph-store-mongodb 0.4.0, MongoDBSaver.list(), MongoDBSaver.alist(), and MongoDBStore.search() incorporate filter dictionaries into MongoDB queries without recursively rejecting keys prefixed with $. An authenticated caller who controls a filter argument through HTTP query parameters, request body fields, or agent tool arguments can inject MongoDB Query Language operators such as $regex or $where. In a multi-tenant deployment that uses the filter to enforce per-user or per-tenant isolation, injected operators can bypass intended equality filtering and expose other tenants' checkpoint or store data. Filters constructed entirely from trusted server-side values have lower practical risk. This issue is fixed in langgraph-checkpoint-mongodb 0.3.0 and langgraph-store-mongodb 0.4.0.

How to fix

No published remediation has been found for this vulnerability's affected products yet.

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeChanged

Impact

ConfidentialityHigh
IntegrityNone
AvailabilityNone

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Exploit Intelligence

0.39%probability of exploitation in 30 days
33rdpercentile

Low risk: more likely to be exploited than 33% of all known CVEs.

References

Related Vulnerabilities

Other CWE-943 vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2017-12904High8.86.4%-Fix
CVE-2020-36195Critical9.81.8%-Fix
CVE-2018-7829High8.81.7%-Fix
CVE-2022-36084Critical9.91.4%-Fix
CVE-2021-1349Medium6.51.4%-Fix
CVE-2018-19952High7.51.3%-Fix

Common questions

How do I fix CVE-2026-55253?

No published fix for CVE-2026-55253 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2026-55253 being actively exploited?

Not that we know of. CVE-2026-55253 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.39% is the estimated probability that it will be exploited in the next 30 days. That is higher than 33% of all scored CVEs.

How severe is CVE-2026-55253?

CVE-2026-55253 has a CVSS v3 base score of 7.7, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2026-55253
CVE-2026-55253 severity badge

Markdown

[![CVE-2026-55253](https://tridentstack.com/cve/badge/CVE-2026-55253.svg)](https://tridentstack.com/cve/CVE-2026-55253)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-55253"><img src="https://tridentstack.com/cve/badge/CVE-2026-55253.svg" alt="CVE-2026-55253"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

Scan your fleet freeStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-14.