-
Notifications
You must be signed in to change notification settings - Fork 18
chore(deps): update dependency langgraph-checkpoint to v3 [security] #503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate-bot
wants to merge
4
commits into
googleapis:main
Choose a base branch
from
renovate-bot:renovate/pypi-langgraph-checkpoint-vulnerability
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
chore(deps): update dependency langgraph-checkpoint to v3 [security] #503
renovate-bot
wants to merge
4
commits into
googleapis:main
from
renovate-bot:renovate/pypi-langgraph-checkpoint-vulnerability
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
|
/gcbrun |
Collaborator
|
/gcbrun |
Collaborator
|
Blocked on 3.9 removal FYI @dishaprakash |
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
Collaborator
|
/gcbrun |
Collaborator
|
Blocked on langchain-postgres update. |
Collaborator
|
/gcbrun |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
api: alloydb
Issues related to the googleapis/langchain-google-alloydb-pg-python API.
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
>=2.0.9, <3.0.0->>=3.0.0, <3.0.1GitHub Vulnerability Alerts
CVE-2025-64439
Summary
Prior to
langgraph-checkpointversion3.0, LangGraph’sJsonPlusSerializer(used as the default serialization protocol for all checkpointing) contains a remote code execution (RCE) vulnerability when deserializing payloads saved in the"json"serialization mode.If an attacker can cause your application to persist a payload serialized in this mode, they may be able to also send malicious content that executes arbitrary Python code during deserialization.
Upgrading to version langgraph-checkpoint
3.0patches this vulnerability by preventing deserialization of custom objects saved in this mode.If you are deploying in
langgraph-api, any version0.5or later is also free of this vulnerability.Details
Affected file / component
jsonplus.py
By default, the serializer attempts to use
"msgpack"for serialization. However, prior to version3.0of the checkpointer library, if illegal Unicode surrogate values caused serialization to fail, it would fall back to using the"json"mode.When operating in this mode, the deserializer supports a constructor-style format (
lc == 2,type == "constructor") for custom objects to allow them to be reconstructed at load time. If an attacker is able to trigger this mode with a malicious payload, deserializing allow the attacker to execute arbitrary functions upon load.Who is affected
This issue affects all users of
langgraph-checkpointversions earlier than 3.0 who:JsonPlusSerializer) that may fall back to"json"mode.If your application only processes trusted data or does not allow untrusted checkpoint writes, the practical risk is reduced.
Proof of Concept (PoC)
Running this PoC writes a file
/tmp/pwnd.txtto disk, demonstrating code execution.Internally, this exploits the following code path:
Fixed Version
The vulnerability is fixed in
langgraph-checkpoint==3.0.0Release link: https://github.com/langchain-ai/langgraph/releases/tag/checkpoint%3D%3D3.0.0
Fix Description
The fix introduces an allow-list for constructor deserialization, restricting permissible
"id"paths to explicitly approved module/class combinations provided at serializer construction.Additionally, saving payloads in
"json"format has been deprecated to remove this unsafe fallback path.Mitigation
Upgrade immediately to
langgraph-checkpoint==3.0.0.This version is fully compatible with
langgraph>=0.3and does not require any import changes or code modifications.In
langgraph-api, updating to0.5or later will automatically require the patched version of the checkpointer library.Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.