Advisory record · GHSA-h5gc-rm8j-5gpr

A Server-Side Request Forgery (SSRF) vulnerability exists in the RequestsToolkit component of the langchain-community package (specifically, langchain_community.agent_toolkits.openapi.toolkit.Reque...

CVSS 8.4 HighCriticalEPSS 0.21 · 97th percentile

Critical, because:

  • CVSS score 8.4 (7.0 or more) and EPSS 0.21 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 23 Jun 2025, 21:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
langchain-communityPyPI<e188d4ecb085d4561a0be3c583d26aa9c2c3283f || <0.0.28e188d4ecb085d4561a0be3c583d26aa9c2c3283f, 0.0.28
Identifiers
GHSA-h5gc-rm8j-5gpr · CVE-2025-2828 · PYSEC-2025-70
Weakness (CWE)
CWE-918
Published
23 Jun 2025
Updated
10 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The langchain-community package is vulnerable to server-side request forgery in its RequestsToolkit component (langchain_community.agent_toolkits.openapi.toolkit.RequestsToolkit) in versions before 0.0.28. The toolkit does not restrict requests to local addresses, so an attacker who can get it to make requests could port scan, reach local services, read cloud instance metadata, and interact with servers on the local network. Upgrade to langchain-community 0.0.28 or later.

Written 10 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.4 High 3.0 CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H CNA (@huntr_ai)
  • CISA KEV Not listed.
  • EPSS 0.21, the 97th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 23 Jun 2025. New records show when each source confirmed them.

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.