Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-86064 high CVSS 8.6

Information Disclosure in github.com/klever-io/klever-go (CVE-2026-86064)

Summary

Vulnerability in github.com/klever-io/klever-go (CVE-2026-86064). Confidential information can be exposed externally. Exploitable via GET /log. Mitigation: upgrade to 1.7.20 or later.

Original description

The description as published by the source.

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()

Root cause

/log is enabled by default and does not require authentication. After the WebSocket upgrade, the server reads the first client message and treats it as a logger Profile. That profile is then applied process-wide through profile.Apply(), which changes global log level patterns and output formatting options for the whole node.

After that handshake, the same unauthenticated connection is registered as a log observer and receives live logs from the ru…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-86064 has been found in github.com/klever-io/klever-go.
Attackers can target a specific entry point like GET /log over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.6/10.
What to do: upgrade github.com/klever-io/klever-go to 1.7.20 or later.
If unsure, ask your IT team or search "github.com/klever-io/klever-go CVE-2026-86064" on the vendor's site.

CVE-2026-86064 (github.com/klever-io/klever-go) — CWE-200 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /log / profile.go / Profile
Patched: 1.7.20 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in github.com/klever-io/klever-go. Attackers reach the vulnerable code path via GET /log without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/klever-io/klever-go. Attack surface: GET /log / profile.go / Profile.

🔥 Severity

Severity: High (CVSS 8.6/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.7.20.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual GET /log requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/klever-io/klever-go' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/klever-io/klever-go' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/klever-io/klever-go を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /log' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /log への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade github.com/klever-io/klever-go to 1.7.20

    ステージング環境で 1.7.20 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /log on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/klever-io/klever-go
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.7.20"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details