CVE-2025-2828 is a server-side request forgery vulnerability in the RequestsToolkit component of the langchain-community package, specifically langchain_community.agent_toolkits.openapi.toolkit.RequestsToolkit, affecting langchain-ai/langchain version 0.0.27. The flaw stems from insufficient restriction of outbound requests: the toolkit permits requests to remote internet destinations and does not prevent access to local or otherwise sensitive internal addresses. This allows attacker-controlled input processed through the toolkit to cause the server-side application to issue requests to localhost, internal network hosts, or cloud metadata endpoints. The vulnerability can be used to probe internal services, enumerate ports, and access resources that are not directly reachable by the attacker.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.