Klever: Marketplace settlement mints KLV when referral % + royalty % exceed the bid (negative seller share silently skipped)
CVE-2026-54754GHSA-p7gw-2pcp-5pf8
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), 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
Go github.com/klever-io/klever-go
- Affected
- < 1.7.19
- Fixed in
- 1.7.19
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-p7gw-2pcp-5pf8 lists affected ranges: Go github.com/klever-io/klever-go >=0 <1.7.19 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GO-2026-6315 lists affected ranges: Go github.com/klever-io/klever-go >=0 <1.7.19 (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-p7gw-2pcp-5pf8 lists affected ranges: Go github.com/klever-io/klever-go >=0 <1.7.19
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H
- EPSS
- CVE-2026-54754: 0.43% estimated exploitation activity in the next 30 days; percentile 37.60 (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 When a marketplace order is settled (MarketBuy / BuyItNow, and auction Claim), the buyer's payment is split three ways — referral, royalties, and the seller (market-order owner) remainder: Referral and royalties are paid out unconditionally, but the seller remainder is only paid when positive (computeMarketOwnerAmount returns Ok and pays nothing when the amount is <= 0). When referral% + royalty% exceeds 100% of the bid, marketOwnerAmount goes negative and is silently skipped — so the marketplace pays out more KLV / sale currency than the buyer paid in, minting the difference out of thin air. The combined ceiling royalty% + referral% <= 100% is checked once, at listing time (Sell). But the two percentages are sourced asymmetrically at settlement: - referral % is snapshotted into the order at Sell (MarketOrderData.ReferralPercentage); - royalty % is never snapshotted — it is read live from the asset at buy time (asset.Royalties.MarketPercentage). So the listing-time invariant…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-p7gw-2pcp-5pf8
- Revision 2 · amended ·
Amended from osv record GO-2026-6315
- Revision 1 · created ·
Published from osv record GHSA-p7gw-2pcp-5pf8
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-54754 Advisory: Klever: Marketplace settlement mints KLV when referral % + royalty % exceed the bid (negative seller share silently skipped) IDs: CVE-2026-54754, GHSA-p7gw-2pcp-5pf8 Record: https://patchnext.com/advisories/cve-2026-54754 (revision 3, 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: Critical (CVSS 9.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.19. 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.19 ## 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-p7gw-2pcp-5pf8 (OSV record GHSA-p7gw-2pcp-5pf8 lists affected ranges: Go github.com/klever-io/klever-go >=0 <1.7.19 (fixed)) - Verified: https://osv.dev/vulnerability/GO-2026-6315 (OSV record GO-2026-6315 lists affected ranges: Go github.com/klever-io/klever-go >=0 <1.7.19 (fixed)) - Verified: https://github.com/advisories/GHSA-p7gw-2pcp-5pf8 (GitHub-reviewed advisory GHSA-p7gw-2pcp-5pf8 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…