CVE-2026-10617
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 security vulnerability has been detected in nextlevelbuilder GoClaw up to 3.11.3. This affects the function resolveAuth of the file internal/http/auth.go of the component Webhook Verification Handler. The manipulation leads to missing authentication. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. The project tagged the reported issue as bug.
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 confidenceAuthentication bypass in the Webhook Verification Handler's resolveAuth function in GoClaw up to 3.11.3. The resolveAuth function in internal/http/auth.go lacks proper authentication verification, allowing remote attackers to send unauthenticated requests to webhook endpoints.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify GoClaw installationLocate the GoClaw application binary or source code in your environment. Check for the presence of the internal/http/auth.go file which contains the resolveAuth function.Affected if The GoClaw software is present and the internal/http/auth.go file with resolveAuth function exists in the codebase
-
Determine installed GoClaw versionRun 'goClaw --version' or check the version information in your deployment. Compare the version number to the affected range (all versions up to and including 3.11.3).Affected if The installed version is 3.11.3 or any earlier version (e.g., 3.11.2, 3.11.1, 3.10.0, etc.)
-
Verify webhook endpoint exposureIdentify if webhook endpoints are enabled or configured in your GoClaw deployment. Check configuration files or running services for webhook handler registrations.Affected if Webhook endpoints are exposed and the resolveAuth function in internal/http/auth.go handles their verification
-
Test authentication bypassSend a request to a webhook endpoint without providing authentication credentials. Observe if the request is processed without credential validation.Affected if Webhook requests are processed successfully without valid credentials due to missing validation in resolveAuth
You are affected if GoClaw version 3.11.3 or earlier is installed and webhook endpoints using the resolveAuth function are exposed without additional authentication controls.
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 proper authentication/verification in the resolveAuth function, such as signature or token validation, to ensure all webhook requests are verified before processing.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10617 — 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-10617 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