Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-86064 – Unauthenticated Log-Level Manipulation (DoS/Info Exposure) – klever-go ≤ 1.7.19

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-86064 is a missing-authentication vulnerability in klever-go, the Go implementation of the Klever blockchain node. The node’s GET /log WebSocket endpoint accepts an unauthenticated client’s first message as a logger "Profile" and applies it to the process-wide global logger, letting a remote, unauthenticated attacker suppress all node logging, flood it with verbose trace output, or otherwise tamper with logging behavior for the duration of the connection. The issue has a CVSS v3.1 base score of 8.6 (High).

Technical details

  • Root cause: The /log route is registered directly on the HTTP engine and bypasses the API’s authentication wrapper entirely. The LogSender component parses the first inbound WebSocket message as a logger Profile and applies it to the global logger without verifying the caller is authenticated.
  • Trigger conditions: The /log endpoint is open/exposed by default; no credentials, tokens, or prior authentication are required to connect and send a profile message.
  • Attack vector: Network — an attacker only needs to open a WebSocket connection to the exposed node’s /log endpoint and send a crafted logger profile message (e.g., *:NONE to mute logging or *:TRACE to flood it).
  • Impact: A remote unauthenticated attacker can mute all node logging (hindering incident detection/forensics), flood logs with excessive verbosity (resource exhaustion/log noise), or otherwise manipulate correlation/verbosity settings process-wide for the life of the connection — impacting confidentiality (exposure of operational log data), integrity, and availability of node observability.

Affected software

  • Product: github.com/klever-io/klever-go (Klever blockchain node / seednode)
  • Affected versions: All versions ≤ 1.7.19
  • Fixed version: 1.7.20 and later

Severity

  • CVSS v3.1 Base Score: 8.6 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

Mitigation and recommended actions

  • Immediate: Upgrade klever-go (node and seednode components) to version 1.7.20 or later, where the /log route is gated behind Basic Authentication before the WebSocket upgrade, logger profile application is restricted to authenticated sessions, and the global logger state is reverted on disconnect.
  • If immediate patching is not possible:
    • Disable or restrict network exposure of the /log endpoint (e.g., via firewall rules or reverse-proxy access controls) so it is not reachable from untrusted networks.
    • Ensure the endpoint is marked as secured/authenticated in node/seednode API route configuration where such options exist in your deployed version.
    • Monitor for unexpected WebSocket connections to /log and for anomalous changes in log verbosity or gaps in log output that could indicate exploitation.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge