CVE-2026-2654
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 · uneditedA weakness has been identified in huggingface smolagents 1.24.0. Impacted is the function requests.get/requests.post of the component LocalPythonExecutor. Executing a manipulation can lead to server-side request forgery. It is possible to launch the attack remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceServer-side request forgery (SSRF) vulnerability in huggingface smolagents 1.24.0 LocalPythonExecutor allows remote attackers to make the server perform arbitrary HTTP requests via manipulated requests.get/requests.post function calls, potentially reaching internal services, cloud metadata endpoints, or intranet resources.
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>= 1.0.0, <= 1.24.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed smolagents versionRun 'pip show smolagents' or check your dependency lock file for the smolagents version numberAffected if The installed version is >= 1.0.0 and <= 1.24.0
-
Verify LocalPythonExecutor is in useSearch your codebase for imports or instantiation of LocalPythonExecutor from smolagents (e.g., 'from smolagents import LocalPythonExecutor' or 'LocalPythonExecutor()')Affected if LocalPythonExecutor is being instantiated or used in your application
-
Confirm requests module exposureInspect the LocalPythonExecutor configuration or code to determine whether the 'requests' Python module is exposed to executed code (this is the vector for SSRF)Affected if The requests module (requests.get, requests.post) is accessible through the LocalPythonExecutor to agent-executed code
You are affected if smolagents version is between 1.0.0 and 1.24.0 AND LocalPythonExecutor is used with the requests module exposed to executed code, allowing arbitrary HTTP requests.
Generated from the published advisory. Verify against your own configuration.
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 · scopedImplement strict URL validation and allowlist controls for requests made through LocalPythonExecutor; restrict or disable arbitrary HTTP request capabilities if not required for the agent's legitimate functionality.
Upgrade to the latest available version of smolagents (greater than 1.24.0)
- Check the currently installed version of smolagents: pip show smolagents
- Upgrade to the latest version of smolagents: pip install --upgrade smolagents
- Verify the new version is installed: pip show smolagents
- Review the release notes for the new version to confirm the SSRF vulnerability is addressed
- Test that your agents function correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2654 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2654 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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