CVE-2026-48121
MEDIUMDescription
@langchain/langgraph-checkpoint-mongodb provides a LangGraph.js CheckpointSaver implementation that uses MongoDB for storage. Versions 1.3.0 and below are vulnerable to NoSQL injection: checkpoint identifiers (thread_id, checkpoint_ns, checkpoint_id) from config.configurable are passed into MongoDB find() queries in MongoDBSaver.getTuple() without type enforcement. If an attacker supplies an object payload (such as MongoDB operators $gt or $ne) instead of a string, it can be interpreted as a query operator, bypassing thread scoping and leaking checkpoints, including pending writes, across tenants. Applications are at risk if they forward untrusted input into config.configurable without coercing it to strings or validating it against a schema, particularly in multi-tenant or user-isolated setups. Apps that only use server-issued, string-typed identifiers with schema validation rejecting non-string fields are not affected. This issue has been fixed in version 1.3.1.
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
Impact
CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 14% of all known CVEs.
References
Related Vulnerabilities
Other CWE-943 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2017-12904 | High | 8.8 | 6.4% | - | Fix |
| CVE-2020-36195 | Critical | 9.8 | 1.8% | - | Fix |
| CVE-2018-7829 | High | 8.8 | 1.7% | - | Fix |
| CVE-2021-1349 | Medium | 6.5 | 1.4% | - | Fix |
| CVE-2018-19952 | High | 7.5 | 1.3% | - | Fix |
| CVE-2022-36084 | Critical | 9.9 | 1.2% | - | Fix |
Common questions
How do I fix CVE-2026-48121?
No published fix for CVE-2026-48121 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-48121 being actively exploited?
Not that we know of. CVE-2026-48121 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.23% is the estimated probability that it will be exploited in the next 30 days. That is higher than 14% of all scored CVEs.
How severe is CVE-2026-48121?
CVE-2026-48121 has a CVSS v3 base score of 6.7, rated medium. 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-48121
Markdown
[](https://tridentstack.com/cve/CVE-2026-48121)HTML
<a href="https://tridentstack.com/cve/CVE-2026-48121"><img src="https://tridentstack.com/cve/badge/CVE-2026-48121.svg" alt="CVE-2026-48121"></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.
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-08-04.