Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

klever-go: Percentage-transfer royalty skips the source debit at exactly-100% splits

CVE-2026-55763GHSA-v358-wf77-39xv

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.19-rc4), 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.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-55763: 0.51% estimated exploitation activity in the next 30 days; percentile 43.30 (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.

Summary In processPercentageRoyaltiesTransfer the royalty pool is collected from the sender by SubFromBalance that is ordered after the split loop and after if royaltiesToPay <= 0 { return Ok }. The split-payout guard rejects only an allocation that exceeds the pool (a strict splitToPay royaltiesToPay), so a split entry of exactly 100% (PercentTransferPercentage = 10000) is a valid config: it drives royaltiesToPay to 0 and hits the early-return before the sender is debited. The split recipient keeps the full royalty; the sender pays nothing for it → mint. The sibling fixed-royalty path (processFixedRoyaltiesTransfer) debits the sender first and is safe. Only the percentage-transfer path collects and distributes in the same function with the collect placed after the early-return. Affected code - core/kapp/accounts/accounts.go — processPercentageRoyaltiesTransfer: split loop → if royaltiesToPay <= 0 { return Ok } → acntSrc.SubFromBalance(royaltyAmount) (debit after the early-return).…

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

    Amended from ghsa record GHSA-v358-wf77-39xv

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6323

  4. Revision 1 · created ·

    Published from osv record GHSA-v358-wf77-39xv

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-55763

Advisory: klever-go: Percentage-transfer royalty skips the source debit at exactly-100% splits
IDs: CVE-2026-55763, GHSA-v358-wf77-39xv
Record: https://patchnext.com/advisories/cve-2026-55763 (revision 4, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
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.19-rc4. A vendor fix does not mean a deployment is fixed.

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

## 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/GHSA-v358-wf77-39xv (OSV record GHSA-v358-wf77-39xv lists affected ranges: Go github.com/klever-io/klever-go >=0 <1.7.19-rc4 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6323 (OSV record GO-2026-6323 lists affected ranges: Go github.com/klever-io/klever-go >=0)
- Verified: https://github.com/advisories/GHSA-v358-wf77-39xv (GitHub-reviewed advisory GHSA-v358-wf77-39xv lists affected ranges: Go github.com/klever-io/klever-go >=0 <=1.7.19-rc2)

Commands are suggestions: review each one before running it.

Loading voting…