Security Resilience

CVE-2023-36188

Langchain 0.0.64

Public PoC
Published
06 July 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.019 79th percentile
Risk Priority 81 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-36188 is a critical-severity Injection (CWE-74) vulnerability in Langchain Langchain. Its CVSS base score is 9.8 (Critical).

Operationally, ranked in the top 21% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

This vulnerability is AI-related — categorised as LLM Application Platforms.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2023-36188 is a remote code execution vulnerability in LangChain version 0.0.64 that stems from unsafe handling of the PALChain parameter, which is passed directly to Python's exec method. The flaw is tracked under CWE-74 and carries a CVSS 3.1 score of 9.8, reflecting network attackability without authentication or user interaction.

A remote attacker can supply a malicious PALChain value to trigger arbitrary code execution on the affected system, resulting in full confidentiality, integrity, and availability impact. The current and peak EPSS scores both stand at 0.1119 with no material increase after disclosure.

Public references point to a GitHub issue and an associated pull request that address the problem in the LangChain repository.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

An issue in langchain v.0.0.64 allows a remote attacker to execute arbitrary code via the PALChain parameter in the Python exec method.

CWE(s)

AI Security AnalysisAI

AI Category
LLM Application Platforms
Risk Domain
N/A
OWASP Top 10 for LLMs 2025
None mapped
AI-specific weaknesses CR
  • CWE-1426 — PALChain LLM output reaches exec sink with no validation.
Mapped by Security Resilience · not in NVD. Poisoning and extraction cases are routed to MITRE ATLAS instead of a synthetic CWE.
Classification Reason
Matched keywords: langchain

Related Threats

CVEs Like This One

CVE-2023-39659Same product: Langchain Langchain
CVE-2023-32786Same product: Langchain Langchain
CVE-2023-29374Same product: Langchain Langchain
CVE-2023-38896Same product: Langchain Langchain
CVE-2024-8309Same product: Langchain Langchain
CVE-2026-25750Same vendor: Langchain
CVE-2023-39661Shared CWE-74
CVE-2024-36420Shared CWE-74
CVE-2023-29827Shared CWE-74
CVE-2025-9148Shared CWE-74

Affected Assets

langchain
langchain
0.0.64

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-74

Developer assessments and testing (including injection-focused techniques) identify improper neutralization of special elements, and the verifiable flaw remediation corrects them pre-deployment.

addresses: CWE-74

Identifies indicators of injection attacks (command, SQL, LDAP, etc.) via anomaly and attack monitoring.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.15 Logging partial match
finds

Logging supports detection of injection attempts but does not prevent the weakness.

finds

Monitoring activities can identify active injection attacks after they occur.

blocks

A.8.25 mandates a secure SDLC process that includes secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training to reduce injection flaws, but does not itself enforce or guarantee neutralization of special elements at runtime.

blocks

Application security requirements explicitly call for controls against injection attacks in software design.

blocks

A.8.27 mandates security-by-design principles (including distrust external input, data validation/sanitization, secure architecture layers, and design reviews against attack patterns) that reach injection when applied to output construction; this stops exploitation for a minority slice (e.g. where principles drive sanitization) but leaves most code-level injection defects untouched without further implementation rigor.

prevents

Secure coding standards require proper neutralization of special elements, directly addressing CWE-74.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-74, a class-level weakness, and none of its children carries one either.

References