CVE-2026-14716
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.13.0-beta.2. Impacted is the function MethodRouter.Handle of the file internal/gateway/router.go of the component WebSocket RPC Handler. Such manipulation leads to incorrect authorization. The attack may be launched remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report.
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 confidenceA security vulnerability in the WebSocket RPC Handler's MethodRouter.Handle function in GoClaw allows remote attackers to bypass authorization checks. The issue exists in internal/gateway/router.go, enabling unauthorized access to RPC methods due to incorrect authorization logic.
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 checksWork through these to decide whether this CVE applies to you.
-
Locate GoClaw installationIdentify where GoClaw is installed by checking common installation paths, service definitions, or running processes (e.g., ps aux | grep -i claw, systemctl list-units | grep claw, or checking /opt/, /usr/local/bin/)Affected if GoClaw is installed and the WebSocket RPC Handler is in use
-
Determine installed GoClaw versionRun the version command for GoClaw (typically 'goclaw --version', 'goclaw version', or check the binary metadata) and compare the version number against the fixed version 3.13.0-beta-2Affected if The installed version is at or below the vulnerable version range and WebSocket RPC is enabled
-
Verify WebSocket RPC Handler is exposedInspect the GoClaw configuration files (commonly in /etc/goclaw/, ~/.config/goclaw/, or a config.yaml/json file) for WebSocket server settings, RPC endpoint configuration, or the 'rpc', 'websocket', or 'gateway' sectionsAffected if WebSocket RPC Handler is enabled and listening on a network-accessible interface
-
Inspect the router.go authorization logicLocate the internal/gateway/router.go file in the GoClaw installation directory or source tree and review the MethodRouter.Handle function for authorization check implementationAffected if The authorization logic in MethodRouter.Handle appears to have conditional bypasses or missing authorization enforcement
-
Test WebSocket RPC authorizationIf possible, use a WebSocket client to connect to the RPC endpoint and attempt to invoke RPC methods without providing valid credentials or authorization tokensAffected if Unauthorized RPC methods can be executed without proper authorization validation
A user is affected if GoClaw with a version at or below 3.13.0-beta-2 is running with the WebSocket RPC Handler exposed and the authorization bypass in internal/gateway/router.go is present.
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 dataUpgrade to a version beyond 3.13.0-beta.2 once the vendor releases a patch. If no patched version is available, implement network-level access controls and additional authentication layers for WebSocket connections.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14716 — 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-14716 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