Skip to main content
VulnerabilityPublished Updated

CVE-2026-58262: klever-go · Insufficient Verification of Data Authenticity

Affects klever-goSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 1.7.20 soon.

Data as of 5 Nov 2026, 23:24 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.7.20
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade klever-go and github.com/klever-io/klever-go to 1.7.20.

Affected software

ProductAffectedFixed in
klever-ioklever-goAffected
  • <1.7.20
Fixed in
  • 1.7.20
Gogithub.com/klever-io/klever-gopkg:golang/github.com/klever-io/klever-goOther threatsAffected
  • <1.7.20
Fixed in
  • 1.7.20

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Klever-Go to version 1.7.20 or later, where the issue is fixed. Patch status is confirmed by the vendor advisory indicating the fix in 1.7.20. No other mitigation is indicated.

Description

Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, header signature verification counts the unused padding bits of the PubKeysBitmap toward the two-thirds validator quorum. These padding bits do not correspond to any validator and are ignored by the actual BLS aggregate-signature check, so a malicious or compromised block producer can set them to reach the required quorum while gathering fewer genuine validator signatures than the protocol demands. As a result, nodes that import or intercept the header accept it as correctly signed without a real two-thirds quorum, weakening consensus safety and undermining finality. This issue is fixed in version 1.7.20.

References

Community reviews

Loading reviews…