LangchainApplication

CVE-2023-32786

HIGH · 7.5 CVSS v3.1 Published 2023-10-20
Fix available
A fix is available. Upgrade to after 0.0.155 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Langchain through 0.0.155, prompt injection allows an attacker to force the service to retrieve data from an arbitrary URL, essentially providing SSRF and potentially injecting content into downstream tasks.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A prompt injection vulnerability in Langchain through 0.0.155 allows attackers to craft malicious prompts that force the service to fetch data from arbitrary URLs, enabling SSRF attacks and potential content injection into downstream processing tasks.

MitigationUpdate to a patched version of LangChain (0.0.156 or later), implement strict input validation and sanitization for user-provided prompts, and apply network segmentation to restrict outbound requests from LLM-integrated services.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LangchainApplication
Affected:<= 0.0.155

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Langchain version
    Run 'pip show langchain' or import langchain; print(langchain.__version__) to determine the installed version
    Affected if Version is 0.0.155 or lower
  2. Verify if user prompts are processed
    Inspect your application code to confirm it accepts and processes user-supplied prompts through Langchain components
    Affected if Your application directly processes untrusted user prompts without sanitization
  3. Identify web fetching capabilities in use
    Review Langchain component usage - check for tools like 'RequestsHttpTool', 'HTTPRequestsTool', or similar HTTP-fetching tools initialized in your chain
    Affected if Your Langchain setup includes tools or components that can make outbound HTTP requests
  4. Confirm network accessibility from the environment
    Attempt a test outbound connection from the server (e.g., curl or python request to a known endpoint) or review network security groups/firewall rules
    Affected if The environment allows outbound network connections from the Langchain process

You are affected if your installed Langchain version is 0.0.155 or lower AND your application processes user-provided prompts through Langchain with outbound network capabilities enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.0.155
Interim mitigation

Update to a patched version of LangChain (0.0.156 or later), implement strict input validation and sanitization for user-provided prompts, and apply network segmentation to restrict outbound requests from LLM-integrated services.

Recommended fix Moderate confidence

langchain >= 0.0.156 (or latest stable version)

  1. 1. Identify the current Langchain version in your project by checking your requirements.txt, setup.py, or package-lock.json
  2. 2. Upgrade Langchain to a version newer than 0.0.155 using pip: pip install langchain>=0.0.156
  3. 3. Alternatively, upgrade to the latest stable version: pip install --upgrade langchain
  4. 4. After upgrading, test your application to ensure the prompt injection vulnerability is remediated
  5. 5. Verify that your application still functions correctly with the new Langchain version
Caveat Earlier Langchain versions may have different API behaviors; review migration guides if upgrading across major versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Langchain Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-32786 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-32786 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data