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

CVE-2026-5418

HIGH · 7.3 CVSS v3.1 Published 2026-04-02
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 vulnerability was identified in appsmithorg appsmith up to 1.97. Impacted is the function computeDisallowedHosts of the file app/server/appsmith-interfaces/src/main/java/com/appsmith/util/WebClientUtils.java of the component Dashboard. Such manipulation leads to server-side request forgery. The attack may be launched remotely. The exploit is publicly available and might be used. Upgrading to version 1.99 is recommended to address this issue. The affected component should be upgraded. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

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 computeDisallowedHosts function of WebClientUtils.java within the Appsmith Dashboard component. The flaw allows remote attackers to manipulate host validation logic to make the server perform arbitrary requests to internal or external resources.

MitigationUpgrade Appsmith to version 1.99 or later to obtain the patched version of WebClientUtils.java that properly validates disallowed hosts in the computeDisallowedHosts function.

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. Confirm Appsmith installation and version
    Locate the Appsmith installation directory and check the version file (typically VERSION.txt or package.json in the installation root). Alternatively, access the Appsmith Dashboard and look for the version number in the footer or admin settings.
    Affected if The installed version is earlier than 1.99 and contains the WebClientUtils.java component in the Dashboard module.
  2. Identify if Dashboard component is enabled
    Review the Appsmith configuration to determine whether the Dashboard component is actively running. Check for WebClientUtils.java presence in the deployed application files under the backend or server directory.
    Affected if The Dashboard component is deployed and WebClientUtils.java with the computeDisallowedHosts function is present in the runtime environment.
  3. Check for network access configuration
    Inspect the Appsmith configuration files (typically in config/ or conf/ directories) for network-related settings, particularly any allowlist or blocklist configurations related to disallowed hosts.
    Affected if The server is configured to allow outbound HTTP requests from the application without proper restrictions on the computeDisallowedHosts function.
  4. Review server access logs for suspicious requests
    Examine application server logs and reverse proxy logs for unusual outbound request patterns, especially to internal IP ranges (127.0.0.0/8, 10.0.0.0/8, 192.168.0.0/16) or metadata endpoints (169.254.169.254).
    Affected if Log analysis reveals requests originating from the Appsmith server to internal infrastructure or unexpected external domains that were not initiated by legitimate administrative actions.

A user is affected if running Appsmith version prior to 1.99 with the Dashboard component enabled and the computeDisallowedHosts function present, combined with outbound network access that could be exploited for SSRF attacks.

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

Upgrade Appsmith to version 1.99 or later to obtain the patched version of WebClientUtils.java that properly validates disallowed hosts in the computeDisallowedHosts function.

Recommended fix High confidence

1.99

  1. Backup your current Appsmith installation and data before upgrading
  2. Upgrade Appsmith to version 1.99 by following the official upgrade documentation at docs.appsmith.com
  3. After upgrading, verify the WebClientUtils.java file has been updated to include the computeDisallowedHosts fix
  4. Test that the SSRF protection is functioning correctly by validating that disallowed host requests are properly blocked

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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