CVE-2026-48775 — LangGraph Checkpoint: Unsafe JSON deserialization in checkpoint loading
LangGraph SQLite Checkpoint is an implementation of LangGraph CheckpointSaver that uses SQLite DB (both sync and async, via aiosqlite). In versions 4.1.0 and prior, the JsonPlusSerializer can reconstruct Python objects from JSON checkpoint payloads. Under conditions where someone could modify checkpoint bytes at rest in the backing store, the deserialization path could reconstruct objects beyond what the application expects, which could in turn result in code execution at checkpoint load time. This is a defense-in-depth issue. The affected behavior is reachable only when checkpoint bytes at rest in the backing store can be modified by an unauthorized party. In most deployments that prerequisite already implies a serious incident; the additional concern is turning "checkpoint-store write access" into code execution in the application runtime. This issue has been fixed in version 4.1.1.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.7% (30-day exploitation probability)+8
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Langchain Langgraph-checkpoint, Langchain-ai Langgraph, Langchain-ai Langraph-checkpoint).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (insecure deserialization), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Langchain | Langgraph-checkpoint | < 4.1.1 | Vulnerable | NIST National Vulnerability Database |
| Langchain-ai | Langgraph | version < 1.2.2 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Langchain-ai | Langraph-checkpoint | version < 4.1.1 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.8 | CVSS 3.1 | Medium | 0.9 | 5.9 | security-advisories@github.com via NIST National Vulnerability Database |
| 6.8 | CVSS 3.1 | Medium | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (score shown at the top: security-advisories@github.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.69%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Monitor serialized objects in requests and unexpected processes spawned by the runtime.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · langchain-ai/langgraph, langchain-ai/langraph-checkpoint
- SSVC assessment updated
- Record published
- CVSS changed · 6.8
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-104873 LangGraph SDK custom auth silently ignores actions= on resource decorators 13d
- Low CVE-2026-14742 langchain-ai langgraph Task Result Cache _cache.py _freeze weak hash Jul 5, 2026
- High CVE-2026-28277 LangGraph: Unsafe msgpack deserialization in LangGraph checkpoint loading Mar 5, 2026
- High CVE-2025-67644 LangGraph SQLite Checkpoint is vulnerable to SQL Injection via metadata filter key in checkpointer list method Dec 10, 2025
- High CVE-2025-64439 LangGraph Checkpoint affected by RCE in "json" mode of JsonPlusSerializer Nov 7, 2025
- High CVE-2025-64104 LangGraph SQLite Checkpoint Filter Key SQL Injection POC for SqliteStore Oct 29, 2025
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-48775 is "LangGraph Checkpoint: Unsafe JSON deserialization in checkpoint loading", rated Medium. It affects Langgraph-checkpoint (Langchain); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.8 describes technical severity. EPSS 0.69% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.