Skip to content

← Actionable
High, CVSS 8.6amended

Klever-Go: /log controls global node logging

CVE-2026-86064GHSA-9v8p-frvj-2pcm

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/klever-io/klever-go 1.7.20), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
EPSS
  • CVE-2026-86064: 0.58% estimated exploitation activity in the next 30 days; percentile 47.62 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

An unauthenticated client can connect to GET /log, send an arbitrary logger profile as the first WebSocket message, and mutate the node's global logging configuration before receiving live logs from the process. I confirmed this against a local validator built from this repository: an unauthenticated client set the global log level to :NONE, the node accepted the profile, and the node stopped emitting normal slot logs while the WebSocket connection remained open. This is not a duplicate of the published KVM or P2P advisories. It is a management-plane flaw in the public WebSocket logging endpoint. Vulnerability details Affected code - Route exposed by default in config/node/api.yaml - Route registration in network/api/api.go - Unauthenticated upgrade in network/api/api.go - First client message is parsed as a logger profile and applied globally in network/api/logs/logSender.go - Global logger mutation happens in dependency github.com/klever-io/klever-go-logger, profile.go, Apply()…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-9v8p-frvj-2pcm

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6583

  3. Revision 1 · created ·

    Published from osv record GHSA-9v8p-frvj-2pcm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-86064

Advisory: Klever-Go: /log controls global node logging
IDs: CVE-2026-86064, GHSA-9v8p-frvj-2pcm
Record: https://patchnext.com/advisories/cve-2026-86064 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/klever-io/klever-go 1.7.20. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/klever-io/klever-go: affected <= 1.7.19; fixed in 1.7.20

## Suggested inspection (read-only)
- Go github.com/klever-io/klever-go: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/klever-io/klever-go.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6583 (OSV record GO-2026-6583 lists affected ranges: Go github.com/klever-io/klever-go >=0 <1.7.20 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-9v8p-frvj-2pcm (OSV record GHSA-9v8p-frvj-2pcm lists affected ranges: Go github.com/klever-io/klever-go >=0 <1.7.20 (fixed))
- Verified: https://github.com/advisories/GHSA-9v8p-frvj-2pcm (GitHub-reviewed advisory GHSA-9v8p-frvj-2pcm lists affected ranges: Go github.com/klever-io/klever-go >=0 <=1.7.19)

Commands are suggestions: review each one before running it.

Loading voting…