GPU VulnDB

Database/AI/ML frameworks & serving

LangChain Core: unescaped 'lc' keys let user data be revived as LangChain objects on load

CVSS 8.2CVE-2025-68664AI/ML frameworks & servingcurated

Impact

LangChain marks its own serialized objects with an 'lc' key, and dumps()/dumpd() did not escape that key when serializing free-form dictionaries. User-controlled data carrying the right key structure is therefore treated as a genuine LangChain object when the payload is deserialized, not as plain data. Where an agent persists messages, tool results or checkpoints and reloads them later, an attacker who can plant a dictionary in that path influences what gets reconstructed on the serving host - the record scores it as high confidentiality with some integrity impact. Distinct from the prompt-template injection in CVE-2025-65106: the flaw is in the serialization layer, with its own fix and versions.

Who can reach it

Network. Any user whose input reaches a dictionary that the application serializes with dumps()/dumpd() and later deserializes. No authentication is required by the record (PR:N); the effect depends on the application round-tripping the data.

What to do

Upgrade langchain-core to 0.3.81 or 1.2.5 and restart the application and any workers that load persisted state. Treat already-stored serialized blobs as untrusted - the fix escapes new writes, it does not sanitize data written before the upgrade.

References

Related entries

All AI/ML frameworks & serving entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.