Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1amended

Klever-Go: Zombie-order theft: Buy missing IsClaimed guard in native marketplace

CVE-2026-82406GHSA-26r5-4mm2-px5c

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.

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
7.1 · 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 · score source
EPSS
  • CVE-2026-82406: 0.43% estimated exploitation activity in the next 30 days; percentile 37.70 (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.

Location: core/kapp/market/market.go — Buy() (approx. L281–436)\ Severity: High The native marketplace enforces an IsClaimed guard in Claim (market.go:752), CancelOrder (market.go:1125), and orderEscrowAmount (market.go:251), but not in Buy. Marketplace escrow is virtual: the market KApp account never custodies currency. A bid burns funds from the bidder (bidderAcc.SubFromBalance, ~L378), and refunds/payouts mint to the recipient (AddToBalance, e.g. the prior-bidder refund at ~L349). Soundness depends on each order's CurrentBid being paid out exactly once. A seller can settle a resting-bid auction early via the seller-accept branch of Claim (~L776) → executeBuyMarket (~L656). That path sets IsClaimed=true, delivers the NFT, pays the seller, and re-saves the order (SetMarketOrder, ~L726) — but, unlike every other settle path, it does not reset EndTime (contrast immediate-buy Buy ~L416 and CancelOrder ~L1206), and no code path deletes the order. The result is a "zombie" order: already…

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

    Amended from ghsa record GHSA-26r5-4mm2-px5c

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

  4. Revision 1 · created ·

    Published from osv record GHSA-26r5-4mm2-px5c

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

Advisory: Klever-Go: Zombie-order theft: `Buy` missing `IsClaimed` guard in native marketplace
IDs: CVE-2026-82406, GHSA-26r5-4mm2-px5c
Record: https://patchnext.com/advisories/cve-2026-82406 (revision 4, 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 7.1)
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-6584 (OSV record GO-2026-6584 lists affected ranges: Go github.com/klever-io/klever-go >=0 <1.7.20 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-26r5-4mm2-px5c (OSV record GHSA-26r5-4mm2-px5c lists affected ranges: Go github.com/klever-io/klever-go >=0 <1.7.20 (fixed))
- Verified: https://github.com/advisories/GHSA-26r5-4mm2-px5c (GitHub-reviewed advisory GHSA-26r5-4mm2-px5c 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…