Most recent entries from all

CVE-2026-40087 — LangChain has incomplete f-string validation in prompt templates

Affected: langchain-ai langchain

LangChain is a framework for building agents and LLM-powered applications. Prior to 0.3.84 and 1.2.28, LangChain's f-string prompt-template validation was incomplete in two respects. First, some prompt template classes accepted f-string templates and formatted them without enforcing the same attribute-access validation as PromptTemplate. In particular, DictPromptTemplate and ImagePromptTemplate could accept templates containing attribute access or indexing expressions and subsequently evaluate those expressions during formatting. Second, f-string validation based on parsed top-level field names did not reject nested replacement fields inside format specifiers. In this pattern, the nested replacement field appears in the format specifier rather than in the top-level field name. As a result, earlier validation based on parsed field names did not reject the template even though Python formatting would still attempt to resolve the nested expression at runtime. This vulnerability is fixed in 0.3.84 and 1.2.28.

GHSA-926x-3r5x-gfhw — LangChain has incomplete f-string validation in prompt templates

Affected: PyPI: langchain-core

LangChain's f-string prompt-template validation was incomplete in two respects.

First, some prompt template classes accepted f-string templates and formatted them without enforcing the same attribute-access validation as `PromptTemplate`. In particular, `DictPromptTemplate` and `ImagePromptTemplate` could accept templates containing attribute access or indexing expressions and subsequently evaluate those expressions during formatting.

Examples of the affected shape include:

```python "{message.additional_kwargs[secret]}" "https://example.com/{image.__class__.__name__}.png" ```

Second, f-string validation based on parsed top-level field names did not reject nested replacement fields inside format specifiers. For example:

```python "{name:{name.__class__.__name__}}" ```

In this pattern, the nested replacement field appears in the format specifier rather than in the top-level field name. As a result, earlier validation based on parsed field names did not reject the template even though Python formatting would still attempt to resolve the nested expression at runtime.

## Affected usage

This issue is only relevant for applications that accept untrusted template strings, rather than only untrusted template variable values.

In addition, practical impact depends on what objects are passed into template formatting:

- If applications only format simple values such as strings and numbers, impact is limited and may only result in formatting errors. - If applications format ric…

PYSEC-2026-2563 — LangChain has incomplete f-string validation in prompt templates