<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 18:26:55 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-55764</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-55764</link>
      <description>&lt;p&gt;Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.19, Klever-Go allows a mint-role holder to bypass a finite per-nonce MaxSupply on the semi-fungible token add-quantity path. In core/kapp/systemAccount/systemAcount.go, SFTAddCirculation performed meta.Circulation += amount before evaluating whether Circulation exceeded MaxSupply, without checking for signed int64 overflow. A large positive raw Amount supplied through processSemiFungibleAddQuantity in core/kapp/kda/mint.go can wrap Circulation negative, causing the signed maximum-supply comparison to pass and crediting approximately MaxInt64 units while corrupting the on-chain counter. The fungible path is not affected because its MintedValue &amp;lt;= 0 guard detects the overflow. The correction uses the consensus activation flag FixMarketBuyOverflow. This issue is fixed in version 1.7.19.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.19, Klever-Go allows a mint-role holder to bypass a finite per-nonce MaxSupply on the semi-fungible token add-quantity path. In core/kapp/systemAccount/systemAcount.go, SFTAddCirculation performed meta.Circulation += amount before evaluating whether Circulation exceeded MaxSupply, without checking for signed int64 overflow. A large positive raw Amount supplied through processSemiFungibleAddQuantity in core/kapp/kda/mint.go can wrap Circulation negative, causing the signed maximum-supply comparison to pass and crediting approximately MaxInt64 units while corrupting the on-chain counter. The fungible path is not affected because its MintedValue &amp;lt;= 0 guard detects the overflow. The correction uses the consensus activation flag FixMarketBuyOverflow. This issue is fixed in version 1.7.19.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-55764</guid>
    </item>
    <item>
      <title>GHSA-mrpp-v6pg-p54x — klever-go: SFT add-quantity `int64` overflow bypasses a finite per-nonce MaxSupply</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-mrpp-v6pg-p54x</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/klever-io/klever-go&lt;/p&gt;
&lt;p&gt;## Summary
On the SFT add-quantity path the only supply bound is `SFTAddCirculation`, which does
`meta.Circulation += amount` with **no overflow guard**, then checks
`if meta.Circulation &amp;gt; meta.MaxSupply &amp;amp;&amp;amp; meta.MaxSupply != 0`. If `amount` overflows `int64` and wraps
**negative**, `negative &amp;gt; MaxSupply` is false, the cap check passes, the function returns `nil`, and the balance
credit stands. A nonce created with a finite `MaxSupply` (e.g. 1000) can thus be minted to ~`MaxInt64` tokens in
one transaction. The fungible mint path is **not** vulnerable — it has a post-increment `MintedValue &amp;lt;= 0` guard
that the SFT path lacks.&lt;/p&gt;
&lt;p&gt;## Affected code
- `core/kapp/systemAccount/systemAcount.go:132-138` (`SFTAddCirculation`, the unguarded `+=`).
- Caller: `core/kapp/kda/mint.go:247-283` (`processSemiFungibleAddQuantity`); contrast guard `mint.go:289`.&lt;/p&gt;
&lt;p&gt;## Impact
A mint-role holder mints ~9.2e18 units of a nonce whose declared `MaxSupply` is small, with no authorized debit,
and corrupts the on-chain `Circulation` counter to a negative value (misleading any market/indexer that reads it).&lt;/p&gt;
&lt;p&gt;## Reachability
Mint-role holder (asset owner or an address granted the role). The mint `Amount` is a raw `int64` from the
contract with no upstream upper bound.&lt;/p&gt;
&lt;p&gt;## Proof of concept&lt;/p&gt;
&lt;p&gt;### Unit test
`TestExploit_SFTCirculationOverflowBypassesCap` creates a nonce capped at `MaxSupply = 1000`, seeds
`Circulation = 5`, then calls `SFTAddCirculation(MaxInt64)`. The call returns `nil` (cap bypassed) and `Cir…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/klever-io/klever-go&lt;/p&gt;
&lt;p&gt;## Summary
On the SFT add-quantity path the only supply bound is `SFTAddCirculation`, which does
`meta.Circulation += amount` with **no overflow guard**, then checks
`if meta.Circulation &amp;gt; meta.MaxSupply &amp;amp;&amp;amp; meta.MaxSupply != 0`. If `amount` overflows `int64` and wraps
**negative**, `negative &amp;gt; MaxSupply` is false, the cap check passes, the function returns `nil`, and the balance
credit stands. A nonce created with a finite `MaxSupply` (e.g. 1000) can thus be minted to ~`MaxInt64` tokens in
one transaction. The fungible mint path is **not** vulnerable — it has a post-increment `MintedValue &amp;lt;= 0` guard
that the SFT path lacks.&lt;/p&gt;
&lt;p&gt;## Affected code
- `core/kapp/systemAccount/systemAcount.go:132-138` (`SFTAddCirculation`, the unguarded `+=`).
- Caller: `core/kapp/kda/mint.go:247-283` (`processSemiFungibleAddQuantity`); contrast guard `mint.go:289`.&lt;/p&gt;
&lt;p&gt;## Impact
A mint-role holder mints ~9.2e18 units of a nonce whose declared `MaxSupply` is small, with no authorized debit,
and corrupts the on-chain `Circulation` counter to a negative value (misleading any market/indexer that reads it).&lt;/p&gt;
&lt;p&gt;## Reachability
Mint-role holder (asset owner or an address granted the role). The mint `Amount` is a raw `int64` from the
contract with no upstream upper bound.&lt;/p&gt;
&lt;p&gt;## Proof of concept&lt;/p&gt;
&lt;p&gt;### Unit test
`TestExploit_SFTCirculationOverflowBypassesCap` creates a nonce capped at `MaxSupply = 1000`, seeds
`Circulation = 5`, then calls `SFTAddCirculation(MaxInt64)`. The call returns `nil` (cap bypassed) and `Cir…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-mrpp-v6pg-p54x</guid>
    </item>
  </channel>
</rss>
