Critical LangGraph Vulnerabilities Expose AI Agents to Remote Code Execution Risks + Video

Listen to this Post

Featured Image

Introduction

Artificial intelligence frameworks are rapidly becoming the backbone of modern enterprise applications, powering autonomous agents capable of accessing databases, APIs, cloud environments, and sensitive business information. While these capabilities create powerful automation opportunities, they also introduce a new generation of cybersecurity risks. Recent research has revealed a dangerous chain of vulnerabilities affecting LangGraph, a widely used open-source framework developed by LangChain for building stateful and multi-agent AI applications.

Security researchers have disclosed three vulnerabilities that, when combined under specific conditions, can potentially grant attackers remote code execution on vulnerable self-hosted deployments. The findings highlight how traditional security weaknesses such as SQL injection and unsafe deserialization can become significantly more dangerous when integrated into AI agent ecosystems that often operate with elevated privileges and broad system access.

Researchers Uncover Three Security Flaws in LangGraph

Cybersecurity researchers have identified three now-patched vulnerabilities affecting LangGraph and its associated checkpointing components. The framework is commonly used by developers building sophisticated AI agent workflows that maintain memory, state tracking, and multi-step reasoning processes.

The disclosed vulnerabilities include:

CVE-2025-67644: SQL Injection in SQLite Checkpointer

This vulnerability affects langgraph-checkpoint-sqlite versions prior to 3.0.1. The flaw allows attackers to manipulate SQL queries through specially crafted metadata filter keys. The vulnerability received a CVSS score of 7.3 and serves as a crucial entry point in the reported attack chain.

CVE-2026-28277: Unsafe Msgpack Deserialization

Affecting LangGraph versions before 1.0.10, this vulnerability allows malicious object reconstruction during checkpoint loading operations. With a CVSS score of 6.8, it becomes particularly dangerous when paired with the SQL injection flaw.

CVE-2026-27022: RediSearch Query Injection

This issue impacts @langchain/langgraph-checkpoint-redis versions before 1.0.1. The vulnerability can enable attackers to bypass access controls through manipulated RediSearch queries. It carries a CVSS score of 6.5.

How the Remote Code Execution Chain Works

According to researchers, the most severe attack scenario combines CVE-2025-67644 and CVE-2026-28277 into a complete remote code execution chain.

The attack begins when a vulnerable deployment exposes the get_state_history() endpoint. This endpoint allows retrieval of historical checkpoints using metadata-based filters.

An attacker first prepares a specially crafted Msgpack payload containing instructions designed to execute arbitrary code. The next stage involves exploiting the SQL injection vulnerability by supplying a malicious filter parameter.

Instead of returning legitimate checkpoint information, the manipulated query generates a fake checkpoint record containing attacker-controlled serialized data. When LangGraph processes the returned data, it automatically deserializes the malicious payload.

The unsafe deserialization mechanism then reconstructs attacker-controlled objects, resulting in arbitrary code execution on the target server.

This sequence effectively transforms a database manipulation flaw into complete system compromise.

Why AI Frameworks Increase Security Impact

Traditional SQL injection vulnerabilities have existed for decades, but AI frameworks introduce new levels of risk.

Modern AI agents frequently possess access to:

Sensitive Business Data

AI systems often interact with internal databases, customer information, intellectual property, and confidential documents.

Cloud Infrastructure

Many AI agents operate within cloud environments where they can interact with storage systems, compute resources, and orchestration platforms.

External APIs

Agentic workflows commonly maintain credentials for third-party services, payment systems, communication platforms, and business applications.

Autonomous Decision-Making Capabilities

Unlike traditional applications, AI agents may independently execute actions based on retrieved information, potentially amplifying the consequences of a successful compromise.

Researchers warn that vulnerabilities inside these frameworks should be viewed through the lens of privileged identity abuse rather than conventional application flaws.

Managed Deployments Remain Protected

An important aspect of the disclosure is that LangChain’s managed platform, known as LangSmith Deployment, is not affected by the reported attack chain.

The vulnerabilities primarily impact self-hosted environments using SQLite or Redis checkpoint mechanisms with user-controlled filter inputs.

LangGraph maintainers emphasized that CVE-2026-28277 should be considered a post-exploitation vulnerability. Successful exploitation requires attackers to gain the ability to manipulate checkpoint data before code execution can occur.

Hosted environments are generally designed with additional safeguards that prevent direct access to the checkpoint persistence layer, reducing exposure to these attack scenarios.

Potential Consequences of Successful Exploitation

A successful attack could provide far-reaching access within affected environments.

Exposure of Runtime Secrets

Attackers may gain access to API keys, authentication tokens, encryption credentials, and environment variables stored within the application runtime.

Lateral Movement Opportunities

Compromised AI agents could serve as a stepping stone into connected infrastructure, enabling broader network penetration.

Unauthorized Data Access

Sensitive business information processed by AI workflows could become accessible to malicious actors.

System Takeover

Remote code execution effectively grants attackers the ability to run arbitrary commands, potentially resulting in complete server compromise.

Security Recommendations for LangGraph Users

Organizations operating self-hosted LangGraph deployments should immediately apply available security updates.

Additional defensive measures include:

Implement Strong Authentication

Every exposed LangGraph endpoint should require robust authentication mechanisms to prevent unauthorized access.

Limit Secret Exposure

Avoid long-lived credentials and rotate sensitive secrets regularly.

Enforce Network Segmentation

Separate AI infrastructure from critical production systems to reduce the impact of potential breaches.

Apply Least Privilege Principles

AI agents should only possess the permissions required to perform their designated tasks.

Monitor Checkpoint Storage Systems

Database activity involving checkpoint data should be closely monitored for suspicious modifications or unauthorized access attempts.

Deep Analysis: Linux Commands Security Teams Can Use

Security teams investigating potential exposure can leverage several Linux commands to assess vulnerable environments and monitor AI infrastructure.

Identify Running LangGraph Services

ps aux | grep langgraph
systemctl status langgraph

Monitor Network Activity

ss -tulpn
netstat -antp
lsof -i

Search for Suspicious Logs

grep -Ri "checkpoint" /var/log/
journalctl -xe
tail -f /var/log/syslog

Inspect Open Files and Processes

lsof -p <PID>
cat /proc/<PID>/maps

Check Redis Activity

redis-cli monitor
redis-cli info

Review SQLite Database Files

sqlite3 checkpoints.db
.tables
.schema

Audit Recent File Changes

find / -type f -mtime -1
find /var -type f -name ".db"

Investigate Environment Variables

printenv
cat /proc/<PID>/environ

Detect Unexpected Network Connections

tcpdump -i any
iftop
nethogs

Validate Package Versions

pip list | grep langgraph
pip show langgraph
npm list @langchain/langgraph-checkpoint-redis
What Undercode Say:

The discovery of these vulnerabilities represents a broader trend in AI security where traditional application weaknesses gain new relevance inside autonomous systems.

The SQL injection issue itself is not particularly novel. Security professionals have been defending against similar flaws for decades.

What makes this case notable is the environment in which the vulnerability exists.

LangGraph is not merely a web application component. It functions as a coordination layer for AI agents that often possess access to privileged resources.

The attack chain demonstrates how old security problems can evolve when combined with modern AI architectures.

Unsafe deserialization has historically been one of the most dangerous programming mistakes because it bridges the gap between data processing and code execution.

When combined with SQL injection, attackers gain a reliable pathway from user input to system compromise.

The presence of checkpointing mechanisms adds another dimension to the risk.

Checkpoint systems are designed to preserve agent memory and execution state.

If these memory systems become attack vectors, adversaries can effectively weaponize the persistence features that make AI agents useful.

The disclosure also reveals an important security lesson.

Many organizations focus heavily on AI model security while overlooking the surrounding infrastructure.

Frameworks, orchestration layers, memory stores, databases, and APIs often represent more practical attack targets than the models themselves.

This mirrors historical cloud security trends.

Organizations initially concentrated on securing virtual machines while attackers targeted identity systems and management layers.

Today, AI ecosystems are following a similar trajectory.

Identity, memory, orchestration, and state management components are becoming high-value targets.

The fact that managed LangSmith deployments remain unaffected highlights the security advantages of controlled infrastructure.

Self-hosted deployments offer flexibility but require stronger operational discipline.

Security teams should increasingly treat AI agents as privileged service accounts.

Every permission granted to an AI system expands the potential blast radius of compromise.

Organizations deploying autonomous agents should perform privilege audits regularly.

Network segmentation becomes particularly important when AI agents interact with sensitive business systems.

Zero-trust principles should be extended to AI infrastructure.

Checkpoint storage systems deserve special attention because they represent persistent memory locations.

Monitoring unusual modifications to these systems may provide early warning indicators of compromise.

Threat modeling exercises should now include AI-specific workflows.

Many organizations have not updated their security architecture to account for agentic applications.

This gap creates opportunities for attackers.

The LangGraph vulnerabilities serve as a reminder that AI security is fundamentally application security, infrastructure security, and identity security combined.

As agentic systems continue to expand across enterprises, vulnerabilities affecting orchestration frameworks will likely become more attractive to threat actors.

Future attacks may increasingly focus on AI memory stores, agent communication channels, and state management layers rather than the underlying language models themselves.

Organizations that recognize this shift early will be better positioned to defend their AI environments.

✅ Researchers disclosed three patched vulnerabilities affecting LangGraph and related checkpoint components.

✅ Security researchers demonstrated that CVE-2025-67644 and CVE-2026-28277 can be chained together under specific self-hosted deployment conditions to achieve remote code execution.

✅ LangSmith-managed deployments were reported as unaffected, while self-hosted installations using vulnerable checkpoint configurations face the highest risk and should apply available patches immediately.

Prediction

(+1) AI framework vendors will introduce stricter checkpoint validation and safer serialization mechanisms to prevent similar exploitation chains.

(+1) Enterprise security teams will begin auditing AI orchestration platforms with the same rigor applied to cloud infrastructure and identity systems.

(-1) As adoption of autonomous AI agents increases, attackers will increasingly target memory systems, orchestration frameworks, and agent state management components.

(-1) More legacy vulnerability classes such as SQL injection and deserialization flaws will emerge within AI ecosystems as organizations rapidly deploy agentic applications without mature security reviews.

(+1) Security tooling specifically designed for AI runtime monitoring and agent privilege management will become a major focus across the cybersecurity industry.

▶️ Related Video (86% Match):

🕵️‍📝Let’s dive deep and fact‑check.

🎓 Live Courses & Certifications:

Join Undercode Academy for Verified Certifications

🚀 Request a Custom Project:

Secure, high-velocity infrastructure and disruptive technological engineering. Contact our engineering team for high-tier development and proprietary systems:
[email protected]
💎 Smart Architecture | 🛡️ Secure by Design | ⭐ Trusted by Thousands

References:

Reported By: thehackernews.com
Extra Source Hub (Possible Sources for article):
https://www.pinterest.com
Wikipedia
OpenAi & Undercode AI

Image Source:

Unsplash
Undercode AI DI v2

🔐JOIN OUR CYBER WORLD [ CVE News • HackMonitor • UndercodeNews ]

💬 Whatsapp | 💬 Telegram

📢 Follow UndercodeNews & Stay Tuned:

𝕏 formerly Twitter 🐦 | @ Threads | 🔗 Linkedin | 🦋BlueSky | 🐘Mastodon | 📺Youtube