Security brief

Historical advisory: LangChain configuration paths could escape the intended repository

REVIEW

The affected component is LangChain configuration loading, not GitHub itself.

Published 29 Oct 2026 · Material update 14 Mar 2024 — last time the underlying evidence changed · Evidence: high

What happened

CVE-2024-28088 describes directory traversal in LangChain’s load_chain configuration-loading path. An actor who controls part of the path could bypass the intended repository restriction, with possible API-key disclosure or code execution.

GitHub hosting appears in the mechanism because the loader was intended to retrieve repository configurations. That does not make this a vulnerability in GitHub’s platform.

The reviewed package table lists fixes in langchain 0.0.339 and langchain-core 0.1.30. Its prose uses a different version description, so compare the package-specific table and upstream references before deciding whether an installation is affected.

For older applications, review dependency versions and who can supply configuration paths. Avoid treating a trusted repository name as validation of every path passed to the loader.

Read the original source.

Who should check?

Maintainers of LangChain applications accepting configuration paths.

Next step

Check the package-specific advisory ranges and restrict configuration-path control.

What we know

Affected components
langchain / langchain-core

What remains unknown

Open question
The advisoryu2019s narrative and package table use different version descriptions; confirm applicability against upstream references.

Source references

Technical details

CVE
CVE-2024-28088