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

CVE-2026-15620

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-14
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 5 weeks old

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 mosaxiv clawlet up to 0.2.10. This affects the function tools.webFetch of the file tools/tool_web_fetch.go. Such manipulation leads to server-side request forgery. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. The reported GitHub issue was closed with the label "not planned".

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 · moderate confidence

The tools.webFetch function in mosaxiv clawlet up to version 0.2.10 (tools/tool_web_fetch.go) is vulnerable to Server-Side Request Forgery (SSRF). The function lacks proper validation of user-supplied URLs, allowing remote attackers to make the server perform arbitrary HTTP requests to internal or external resources, potentially accessing internal services or exfiltrating data.

MitigationSince the vendor has marked this issue as 'not planned' with no official patch, implement compensating controls: add strict URL allowlist validation before fetching, restrict outbound network access, and consider disabling or rate-limiting the web fetch functionality until a fix is available.

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. Identify mosaxiv clawlet installation
    Locate the mosaxiv clawlet binary or installation directory on the system. Common locations include /opt/, /usr/local/bin/, or the user's home directory. Run 'which mosaxiv' or search for files named 'mosaxiv' or containing 'clawlet'.
    Affected if The software is installed and the binary/directory is found on the system.
  2. Determine installed version
    Run the binary with version flags such as 'mosaxiv --version', 'mosaxiv -v', or check the binary file metadata. If source code is available, inspect the version in the codebase or git tags.
    Affected if The version is 0.2.10 or lower.
  3. Verify webFetch function exists
    Locate and inspect the file tools/tool_web_fetch.go in the installation directory or source code. Confirm the webFetch function is present in the codebase.
    Affected if The file tools/tool_web_fetch.go exists and contains the webFetch function.
  4. Check if webFetch is enabled or accessible
    Review the application's configuration files (e.g., config.yaml, config.json) or CLI flags to determine if the webFetch functionality is enabled. Test by attempting to invoke the function via CLI or API if exposed.
    Affected if The webFetch function is enabled and accessible to users or attackers.
  5. Inspect URL validation implementation
    Examine the source code in tools/tool_web_fetch.go for URL validation logic. Search for functions that validate, sanitize, or whitelist URLs before performing HTTP requests. Look for patterns like url.Parse, validation functions, or allowlist checks.
    Affected if No URL validation, allowlist, or sanitization is implemented before the fetch operation.

The system is affected if mosaxiv clawlet version 0.2.10 or lower is installed, the webFetch function is enabled, and the code lacks URL validation before making 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

Since the vendor has marked this issue as 'not planned' with no official patch, implement compensating controls: add strict URL allowlist validation before fetching, restrict outbound network access, and consider disabling or rate-limiting the web fetch functionality until a fix is available.

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-15620 — 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-15620 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