Langraph Checkpoint
Approved changes feed: RSS · Atom
cpe:2.3:a:langchain-ai:langraph-checkpoint:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Langchain Ai (95fad776-1fab-55af-bd3a-6177850e04d4) |
|---|---|
| Product | Langraph Checkpoint (f3e1bb2a-d79d-575b-bff7-102091b3e645) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-48775 |
vulnerable | 2026-07-29 00:55:01.629196 |
LangGraph Checkpoint: Unsafe JSON deserialization in checkpoint loading
MEDIUM (6.8)
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.
Published: 2026-06-16T17:53:10.808Z
Updated: 2026-06-16T18:42:07.221Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.