dbcve.org
LangchainApplication

CVE-2025-2828

CRITICAL · 10.0 CVSS v3.1 Published 2025-06-23
Fix available
A fix is available. Upgrade to 0.0.28 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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
A Server-Side Request Forgery (SSRF) vulnerability exists in the RequestsToolkit component of the langchain-community package (specifically, langchain_community.agent_toolkits.openapi.toolkit.RequestsToolkit) in langchain-ai/langchain version 0.0.27. This vulnerability occurs because the toolkit does not enforce restrictions on requests to remote internet addresses, allowing it to also access local addresses. As a result, an attacker could exploit this flaw to perform port scans, access local services, retrieve instance metadata from cloud environments (e.g., Azure, AWS), and interact with servers on the local network. This issue has been fixed in version 0.0.28.

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 · high confidence

SSRF vulnerability in langchain-community's RequestsToolkit (langchain_community.agent_toolkits.openapi.toolkit.RequestsToolkit) version 0.0.27 allows attackers to bypass restrictions and make requests to local addresses. The toolkit fails to enforce network boundaries, enabling port scanning, access to local services, and retrieval of cloud instance metadata from AWS/Azure.

MitigationUpgrade langchain-community package to version 0.0.28 or later to patch the vulnerability. Implement network-level controls restricting outbound access from the application to prevent potential SSRF exploitation.

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.28

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
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify installed langchain-community version
    Run 'pip show langchain-community' or check your requirements.txt/pipfile.lock for the installed version number
    Affected if Version is 0.0.27 or lower (any version below 0.0.28)
  2. Verify RequestsToolkit import usage
    Search your codebase for 'from langchain_community.agent_toolkits.openapi.toolkit import RequestsToolkit' or 'langchain_community.agent_toolkits.openapi' imports
    Affected if The vulnerable RequestsToolkit from langchain-community is imported and used in your code
  3. Check for HTTP request capabilities in agent configurations
    Review any LangChain agent or chain configurations that use the OpenAPI toolkit or make outbound HTTP requests
    Affected if Your agents/chains invoke the toolkit to make HTTP requests to arbitrary URLs
  4. Inspect runtime environment network access
    Review your application logs, proxy configs, or network policies for any unexpected outbound requests to localhost, 127.0.0.1, or internal IP ranges (e.g., 10.x.x.x, 169.254.x.x for metadata)
    Affected if Your application has made or can make requests to local addresses or cloud metadata endpoints (169.254.169.254)

You are affected if langchain-community version is below 0.0.28 AND your code uses RequestsToolkit to make HTTP requests, especially if the environment has access to local services or cloud metadata endpoints.

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 0.0.28 or later
Fixed in 0.0.28
Vendor patch github.com →
Interim mitigation

Upgrade langchain-community package to version 0.0.28 or later to patch the vulnerability. Implement network-level controls restricting outbound access from the application to prevent potential SSRF exploitation.

Recommended fix High confidence

langchain-community version 0.0.28 or later

  1. Verify the current installed version of langchain or langchain-community by running: pip show langchain-community or pip list | grep langchain
  2. Upgrade langchain-community to version 0.0.28 or later using: pip install --upgrade langchain-community>=0.0.28
  3. Alternatively, upgrade the langchain package if that's what's installed: pip install --upgrade langchain>=0.0.28
  4. Verify the upgrade was successful by checking: pip show langchain-community
  5. Test that the application functions correctly with the updated package

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

Fix this in Langchain Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2025-2828 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