CVE-2026-115883 langchain-ai CVE debrief

Who should care

Defenders responsible for LangGraph deployments using Postgres and SQLite stores should assess exposure and prioritize updates to fixed versions. This includes roles managing package dependencies and security teams verifying vulnerability remediation.

Why it matters

CVE-2026-115883 allows unauthorized access or modification of data in LangGraph's Postgres and SQLite stores due to improper handling of namespace labels containing `.`. Defenders should verify exposure, prioritize updates, and assess potential impacts on data integrity and confidentiality.

• Potential unauthorized data access or modification
• Possible overwrite or deletion of items in other namespaces
• Requires verification of affected versions and exposure in environments
• Prioritization of updates to fixed versions 3.1.3 and 3.1.2 for langgraph-checkpoint-postgres and langgraph-checkpoint-sqlite respectively

Technical summary

The Postgres and SQLite stores in LangGraph save a namespace as its labels joined with `.`. This allows a label containing `.` to resolve to a different namespace, potentially allowing unauthorized access to data. The `put` method rejected labels containing `.`, but other methods like `get`, `search`, `delete`, and `list_namespaces` did not. This vulnerability could allow a caller to read, overwrite, or delete items in another namespace.

Defensive priority

Defenders should prioritize verifying and updating langgraph-checkpoint-postgres and langgraph-checkpoint-sqlite packages to the fixed versions 3.1.3 and 3.1.2 respectively, and assess exposure in their environments.

Recommended defensive actions

• Verify and update langgraph-checkpoint-postgres to version 3.1.3 or later
• Verify and update langgraph-checkpoint-sqlite to version 3.1.2 or later
• Assess exposure in environments using affected versions of langgraph-checkpoint-postgres and langgraph-checkpoint-sqlite
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The source corpus provides details on the vulnerability in LangGraph's Postgres and SQLite stores, where namespace labels containing `.` could be used to access data in other namespaces. The corpus includes references to the CVE Program record, NVD vulnerability detail, and source-specific vulnerability assessments.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.