CVE-2026-86065 klever-io CVE debrief

Who should care

Defenders responsible for Klever-Go nodes and blockchain protocol implementations should assess exposure and prioritize upgrading to version 1.7.20 or later. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify exposure and plan for remediation to prevent potential memory or scheduler exhaustion.

Why it matters

CVE-2026-86065 is a high-severity vulnerability in the Klever-Go implementation of the Klever blockchain protocol. Defenders should prioritize verifying exposure and upgrading to version 1.7.20 or later to prevent potential memory or scheduler exhaustion.

• Potential memory exhaustion due to unbounded address list growth
• Potential scheduler exhaustion due to retained goroutines and buffered channels
• Node crash and interruption of P2P and consensus participation
• Verification of exposure and remediation priority

Technical summary

The vulnerability affects the default-open GET /subscribe endpoint in network/api/websocket/routes.go, which accepts unauthenticated WebSocket clients with permissive origin handling. This allows for potential memory or scheduler exhaustion, which can crash the node and interrupt P2P and consensus participation. The issue is fixed in version 1.7.20. Defenders should prioritize verifying exposure and upgrading to prevent potential memory or scheduler exhaustion. The CVE record and NVD vulnerability detail provide information on the vulnerability, its impact, and the fixed version.

Defensive priority

Defenders should prioritize verifying exposure of Klever-Go nodes to the /subscribe endpoint and upgrading to version 1.7.20 or later.

Recommended defensive actions

• Verify exposure of Klever-Go nodes to the /subscribe endpoint
• Upgrade to version 1.7.20 or later
• Monitor for potential memory or scheduler exhaustion
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD vulnerability detail provide information on the vulnerability, its impact, and the fixed version. However, the corpus does not establish versions, exploitation, impact, or remediation beyond the provided official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.