CVE-2026-48121

MEDIUMPre-NVD 6.76.7—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 86% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

@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.

CVSS v3
6.7
EG Score
6.7MEDIUMmedium confidence
EG Risk
30
EG Risk 30/100

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
Severity67% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
27th
KEV
Not listed

Published

June 12, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 4, 2026
Patch available. Sources: github, github_commit.
github_commit Patch Available

commit 284226c7ca16 (langchain-ai/langgraphjs)

Patch available: langchain-ai/langgraphjs @langchain/[email protected] (contains commit 284226c7ca16)

https://github.com/langchain-ai/langgraphjs/commit/284226c7ca164b3c81fe2d9e32b10f1fc6b99a3c
generic

Security: NoSQL injection in MongoDBSaver.getTuple permits cross-tenant checkpoint disclosure · Issue #2351 · langchain-ai/langgraphjs · GitHub

https://github.com/langchain-ai/langgraphjs/issues/2351
githubMentions a patch (unverified)

NoSQL parameter injection in MongoDBSaver allows cross-tenant state access · Advisory · langchain-ai/langgraphjs · GitHub

https://github.com/langchain-ai/langgraphjs/security/advisories/GHSA-98xf-r82g-9mhx

Vendor Advisories for CVE-2026-48121(1)

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@langchain/langgraph-checkpoint-mongodb—
  • every version up to 1.3.1: fixed in 1.3.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 23× 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-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-03 08:39 UTCOSV refresh
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-27 13:48 UTCEPSS rescore
  13. 2026-09-26 15:59 UTCEPSS rescore
  14. 2026-09-26 00:27 UTCEPSS rescore
  15. 2026-09-23 17:53 UTCEPSS rescore
  16. 2026-09-20 20:16 UTCEPSS rescore
  17. 2026-09-18 19:28 UTCEPSS rescore
  18. 2026-09-16 14:08 UTCEPSS rescore
  19. 2026-09-16 05:15 UTCEPSS rescore
  20. 2026-09-14 04:04 UTCEG score recompute
  21. 2026-09-13 16:47 UTCEPSS rescore
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-10 09:35 UTCEPSS rescore
  24. 2026-09-09 22:59 UTCEG score recompute
  25. 2026-09-08 22:01 UTCEPSS rescore
Show 55 more
  1. 2026-09-07 16:01 UTCEPSS rescore
  2. 2026-09-06 13:47 UTCEPSS rescore
  3. 2026-09-04 05:06 UTCEPSS rescore
  4. 2026-09-02 14:12 UTCEPSS rescore
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-08-30 23:45 UTCEG score recompute
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 01:22 UTCEPSS rescore
  9. 2026-08-28 21:41 UTCEPSS rescore
  10. 2026-08-27 14:25 UTCEPSS rescore
  11. 2026-08-26 14:46 UTCEPSS rescore
  12. 2026-08-25 13:49 UTCEPSS rescore
  13. 2026-08-24 23:51 UTCEG score recompute
  14. 2026-08-23 10:30 UTCEG score recompute
  15. 2026-08-23 00:19 UTCEPSS rescore
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-21 09:55 UTCEG score recompute
  18. 2026-08-20 22:55 UTCEPSS rescore
  19. 2026-08-20 11:29 UTCEG score recompute
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-19 13:45 UTCEG score recompute
  22. 2026-08-18 13:48 UTCEPSS rescore
  23. 2026-08-17 14:29 UTCEG score recompute
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-16 16:44 UTCEG score recompute
  26. 2026-08-16 14:56 UTCEPSS rescore
  27. 2026-08-16 02:14 UTCEPSS rescore
  28. 2026-08-15 18:53 UTCEG score recompute
  29. 2026-08-15 01:30 UTCEPSS rescore
  30. 2026-08-13 23:27 UTCEG score recompute
  31. 2026-08-13 22:00 UTCEPSS rescore
  32. 2026-08-13 01:43 UTCEG score recompute
  33. 2026-08-12 13:51 UTCEPSS rescore
  34. 2026-08-12 04:00 UTCEG score recompute
  35. 2026-08-11 06:16 UTCEG score recompute
  36. 2026-08-11 00:00 UTCEPSS rescore
  37. 2026-08-10 08:33 UTCEG score recompute
  38. 2026-08-09 13:46 UTCEPSS rescore
  39. 2026-08-09 10:50 UTCEG score recompute
  40. 2026-08-08 16:37 UTCEPSS rescore
  41. 2026-08-08 13:06 UTCEG score recompute
  42. 2026-08-06 17:39 UTCEG score recompute
  43. 2026-08-06 13:47 UTCEPSS rescore
  44. 2026-08-05 19:56 UTCEG score recompute
  45. 2026-08-05 19:17 UTCEPSS rescore
  46. 2026-08-04 20:35 UTCEG score recompute
  47. 2026-08-04 20:07 UTCEG score recompute
  48. 2026-08-04 17:24 UTCEG score recompute
  49. 2026-07-30 09:27 UTCEG score recompute
  50. 2026-07-26 20:43 UTCEG score recompute
  51. 2026-07-23 03:18 UTCEG score recompute
  52. 2026-06-14 23:18 UTCEPSS rescore
  53. 2026-06-13 23:00 UTCEPSS rescore
  54. 2026-06-12 23:12 UTCEPSS rescore
  55. 2026-06-12 15:11 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-48121?
CVE-2026-48121 is a medium vulnerability published on June 12, 2026. @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 (threadid, checkpointns, checkpoint_id) from config.configurable are passed into MongoDB…
When was CVE-2026-48121 disclosed?
CVE-2026-48121 was first published on June 12, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48121 actively exploited?
CVE-2026-48121 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48121?
CVE-2026-48121 has a CVSS base score of 6.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48121?
A fix for CVE-2026-48121 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48121 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-48121

Explore →

Is Your Infrastructure Affected by CVE-2026-48121?

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