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

CVE-2026-32857

HIGH · 8.6 CVSS v3.1 Published 2026-03-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Firecrawl version 2.8.0 and prior contain a server-side request forgery (SSRF) protection bypass vulnerability in the Playwright scraping service where network policy validation is applied only to the initial user-supplied URL and not to subsequent redirect destinations. Attackers can supply an externally valid URL that passes validation and returns an HTTP redirect to an internal or restricted resource, allowing the browser to follow the redirect and fetch the final destination without revalidation, thereby gaining access to internal network services and sensitive endpoints. This issue is distinct from CVE-2024-56800, which describes redirect-based SSRF generally. This vulnerability specifically arises from a post-redirect enforcement gap in implemented SSRF protections, where validation is applied only to the initial request and not to the final redirected destination.

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

Firecrawl's Playwright scraping service only validates the initial URL against SSRF protection policies but fails to re-validate redirect destinations. Attackers can supply a benign external URL that passes initial validation, then receive an HTTP 30x redirect to internal or restricted resources (e.g., localhost, 127.0.0.1, cloud metadata endpoints), which the browser follows without additional validation.

MitigationImplement redirect destination validation by intercepting HTTP redirects and applying the same SSRF policy checks to the final destination URL before allowing the browser to follow it.

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
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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 Firecrawl version
    Run 'pip show firecrawl' or check your package.json/requirements.txt to find the installed version number
    Affected if Version is 2.8.0 or lower
  2. Confirm Playwright scraper is enabled
    Check your Firecrawl configuration or code that uses the scraping service to verify Playwright-based scraping is active
    Affected if Playwright scraper is in use for external URL processing
  3. Inspect Playwright redirect configuration
    Review the Playwright configuration or launch options used by Firecrawl - look for 'followRedirect' or similar settings
    Affected if Automatic redirect following is enabled without per-redirect validation
  4. Check for redirect destination validation
    Review the source code or configuration for the scraping service to determine if redirect URLs are validated against network policy before being followed
    Affected if No validation logic exists for redirect target URLs (only initial URL is validated)

You are affected if Firecrawl version is 2.8.0 or prior AND the Playwright scraper is enabled with automatic redirect following that does not validate redirect destination 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement redirect destination validation by intercepting HTTP redirects and applying the same SSRF policy checks to the final destination URL before allowing the browser to follow it.

Recommended fix Moderate confidence

Firecrawl version greater than 2.8.0 (e.g., 2.8.1 or latest stable release)

  1. 1. Identify the currently installed Firecrawl version by running 'pip show firecrawl' or checking your dependency lock file
  2. 2. Upgrade Firecrawl to the latest available version using 'pip install --upgrade firecrawl'
  3. 3. Verify the upgrade was successful by running 'pip show firecrawl' and confirming the installed version is greater than 2.8.0
  4. 4. Test that SSRF protections now properly validate redirect destinations by attempting a controlled redirect to an internal resource (e.g., localhost) - the request should be blocked
  5. 5. If using a containerized deployment, rebuild the container with the updated package and redeploy
Caveat Minor version升级通常无重大变更，但建议在非生产环境验证功能正常

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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