dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-6616

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
A security vulnerability has been detected in TransformerOptimus SuperAGI up to 0.0.14. This affects the function extract_with_bs4/extract_with_3k/extract_with_lxml of the file superagi/helper/webpage_extractor.py of the component WebScraperTool. Such manipulation leads to server-side request forgery. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used. 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 confidence

Server-side request forgery (SSRF) in TransformerOptimus SuperAGI's WebScraperTool allows remote attackers to make the server perform arbitrary HTTP requests to internal or external resources via the webpage_extractor.py functions (extract_with_bs4, extract_with_3k, extract_with_lxml). The tool lacks proper validation of user-supplied URLs before fetching web content.

MitigationImplement strict URL allowlist validation to restrict web scraping to permitted domains only, and block requests to internal/private IP ranges (127.0.0.0/8, 10.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12) and cloud metadata endpoints.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Locate SuperAGI installation
    Identify the SuperAGI installation directory and confirm the presence of the WebScraperTool module. Search for the file webpage_extractor.py in the codebase.
    Affected if The file webpage_extractor.py exists in the SuperAGI installation and contains the extract_with_bs4, extract_with_lxml, or extract_with_3k functions.
  2. Verify SuperAGI version
    Check the installed SuperAGI version by reviewing version files, setup.py, pyproject.toml, or the package metadata.
    Affected if The installed version of SuperAGI falls within any affected version range (if known) or is a version where the WebScraperTool lacks URL validation.
  3. Inspect URL validation in webpage_extractor.py
    Examine the source code of webpage_extractor.py, specifically the extract_with_bs4, extract_with_lxml, and extract_with_3k functions, for any URL validation or allowlist logic.
    Affected if The code directly uses user-supplied URLs in requests without validating them against an allowlist or checking for internal/private IP ranges.
  4. Test WebScraperTool for SSRF
    If the tool is accessible, attempt to provide an internal URL (such as http://127.0.0.1, http://169.254.169.254, or http://internal-resource) as input to the WebScraperTool.
    Affected if The tool successfully makes requests to internal or private IP addresses, indicating the SSRF vulnerability is present and exploitable.
  5. Check network segmentation
    Review network configuration and firewall rules to determine if the SuperAGI server has unrestricted outbound network access.
    Affected if The server can initiate arbitrary HTTP connections to external or internal resources without restrictions.

A defender is affected if SuperAGI with the WebScraperTool is installed and the webpage_extractor.py code lacks proper URL validation, allowing the tool to fetch content from internal or arbitrary URLs.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict URL allowlist validation to restrict web scraping to permitted domains only, and block requests to internal/private IP ranges (127.0.0.0/8, 10.0.0.0/8, 192.168.0.0/16, 172.16.0.0/12) and cloud metadata endpoints.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6616 — 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-2026-6616 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