CVE-2026-15619
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 · uneditedA weakness has been identified in mosaxiv clawlet up to 0.2.10. The impacted element is the function web_fetch of the file tools/tool_web_fetch.go of the component IPv4 Handler. This manipulation of the argument url causes server-side request forgery. The attack can be initiated remotely. The exploit has been made available to the public and could be used for attacks. 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 confidenceServer-side request forgery (SSRF) vulnerability in mosaxiv clawlet up to version 0.2.10. The web_fetch function in tools/tool_web_fetch.go does not properly validate the url parameter, allowing an attacker to make the server perform arbitrary HTTP requests to internal or external resources.
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
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify mosaxiv clawlet installationLocate the mosaxiv clawlet installation and determine its version by checking the binary or package version (e.g., mosaxiv --version, or check installed package metadata)Affected if version is 0.2.10 or earlier
-
Locate the web_fetch toolVerify that the tools/tool_web_fetch.go file exists in the installation, indicating the web_fetch function is compiled into the applicationAffected if the web_fetch tool binary or source file is present in the deployment
-
Check for URL validation in web_fetch configurationInspect any configuration files, command-line flags, or environment variables that control web_fetch behavior to determine if URL validation has been explicitly enabledAffected if URL validation is not explicitly configured or is disabled (the default vulnerable state in affected versions)
-
Test web_fetch with internal URLIf you have access to invoke the web_fetch function, attempt a request to an internal-only resource (e.g., http://localhost:8080 or http://127.0.0.1) to confirm the vulnerability is exploitableAffected if the server successfully fetches the internal URL, indicating no SSRF protection is in place
You are affected if mosaxiv clawlet version 0.2.10 or earlier is installed AND the web_fetch function is accessible without proper URL validation controls in place.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict URL validation and allowlist controls for the url parameter in the web_fetch function. Restrict to permitted protocols (http/https), validate the destination host, and reject requests to internal/private IP ranges.
- Consultation1.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,768.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15619 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15619 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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