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

CVE-2026-11437

HIGH · 7.3 CVSS v3.1 Published 2026-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
A flaw has been found in perfree go-fastdfs-web up to 1.3.7. Affected is the function checkServer of the file /install/checkServer of the component Installation Endpoint. Executing a manipulation can lead to server-side request forgery. The attack can be executed remotely. The exploit has been published 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) vulnerability in the checkServer function of the installation endpoint (/install/checkServer) in go-fastdfs-web versions up to 1.3.7. The function fails to properly validate URLs before making server-side requests, allowing remote attackers to manipulate the server into making requests to arbitrary internal or external resources.

MitigationDisable or restrict access to the /install/checkServer endpoint in production environments. If a fixed version is available, upgrade immediately. Otherwise, implement network segmentation and outbound firewall rules to limit the server's ability to make arbitrary HTTP requests.

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
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/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 go-fastdfs-web installation
    Search for common installation directories such as /opt/go-fastdfs-web, /usr/local/go-fastdfs-web, or the application root directory. Check for files named go-fastdfs-web, start.sh, or configuration files containing 'fastdfs' in the filename.
    Affected if The application is present on the system.
  2. Identify installed version
    Check for a version file, version info in the main executable, or look for version strings in configuration files or the binary itself. Common locations include a version.txt file in the application root or version information embedded in the main binary.
    Affected if The installed version is 1.3.7 or earlier (including any version up to and including 1.3.7).
  3. Verify /install endpoint exists
    Locate the web application files and identify if the /install routing endpoint is present. This is typically found in the router or controller configuration files that handle the /install/checkServer path.
    Affected if The /install/checkServer endpoint is present in the application's routing configuration.
  4. Confirm checkServer functionality is enabled
    Examine the application configuration to determine if the installation check functionality is accessible. This may involve checking if the application is in an installed state (whether install.lock or similar flag exists) and whether the /install routes are actively mapped.
    Affected if The checkServer function is mapped to an accessible route and the installation interface is not locked or disabled.
  5. Inspect network accessibility
    Determine if the server can make outbound HTTP requests. Review any firewall rules, network segmentation, or proxy configuration that may restrict or permit the server's ability to initiate HTTP connections to arbitrary URLs.
    Affected if The server has the ability to initiate HTTP requests to internal or external resources (no network restrictions in place).

A user is affected if go-fastdfs-web version 1.3.7 or earlier is installed, the /install/checkServer endpoint is accessible, and the server can initiate arbitrary HTTP requests.

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

Disable or restrict access to the /install/checkServer endpoint in production environments. If a fixed version is available, upgrade immediately. Otherwise, implement network segmentation and outbound firewall rules to limit the server's ability to make arbitrary HTTP requests.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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