https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 21:28:30 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-356514 EUVD-2026-356514 https://cve.radiocsirt.org/vuln/euvd-2026-356514 https://cve.radiocsirt.org/vuln/fkie_cve-2026-73829 <p>Time-of-check Time-of-use (TOCTOU) Race Condition in ZenHive mpp allows an unauthenticated remote client to redeem one confirmed on-chain payment for multiple paid-resource accesses.</p> <p>The type=&#34;hash&#34; credential path in MPP.Methods.Tempo.verify/2 guards against replay with a non-atomic check-then-mark sequence: check_hash_unused/2 reads the dedup store, an eth_getTransactionReceipt round trip verifies the payment on chain, and only then does mark_hash_used/2 write the mark. Concurrent requests carrying the same settled payment hash all pass the read before any of them writes, so each is issued a receipt. The store&#39;s atomic check_and_mark/2 primitive is available and used by the type=&#34;transaction&#34; path, but the hash path calls plain get and put even when the configured store implements it. Exploitation requires a dedup store to be configured; the default nil store is stateless and documented as offering no replay protection at all.</p> <p>This issue affects mpp: from 0.2.0 before 0.6.1.</p> <p>Time-of-check Time-of-use (TOCTOU) Race Condition in ZenHive mpp allows an unauthenticated remote client to redeem one confirmed on-chain payment for multiple paid-resource accesses.</p> <p>The type=&#34;hash&#34; credential path in MPP.Methods.Tempo.verify/2 guards against replay with a non-atomic check-then-mark sequence: check_hash_unused/2 reads the dedup store, an eth_getTransactionReceipt round trip verifies the payment on chain, and only then does mark_hash_used/2 write the mark. Concurrent requests carrying the same settled payment hash all pass the read before any of them writes, so each is issued a receipt. The store&#39;s atomic check_and_mark/2 primitive is available and used by the type=&#34;transaction&#34; path, but the hash path calls plain get and put even when the configured store implements it. Exploitation requires a dedup store to be configured; the default nil store is stateless and documented as offering no replay protection at all.</p> <p>This issue affects mpp: from 0.2.0 before 0.6.1.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-73829 https://cve.radiocsirt.org/vuln/ghsa-vjfr-ffhr-5g8p <p>Time-of-check Time-of-use (TOCTOU) Race Condition in ZenHive mpp allows an unauthenticated remote client to redeem one confirmed on-chain payment for multiple paid-resource accesses.</p> <p>The type=&#34;hash&#34; credential path in MPP.Methods.Tempo.verify/2 guards against replay with a non-atomic check-then-mark sequence: check_hash_unused/2 reads the dedup store, an eth_getTransactionReceipt round trip verifies the payment on chain, and only then does mark_hash_used/2 write the mark. Concurrent requests carrying the same settled payment hash all pass the read before any of them writes, so each is issued a receipt. The store&#39;s atomic check_and_mark/2 primitive is available and used by the type=&#34;transaction&#34; path, but the hash path calls plain get and put even when the configured store implements it. Exploitation requires a dedup store to be configured; the default nil store is stateless and documented as offering no replay protection at all.</p> <p>This issue affects mpp: from 0.2.0 before 0.6.1.</p> <p>Time-of-check Time-of-use (TOCTOU) Race Condition in ZenHive mpp allows an unauthenticated remote client to redeem one confirmed on-chain payment for multiple paid-resource accesses.</p> <p>The type=&#34;hash&#34; credential path in MPP.Methods.Tempo.verify/2 guards against replay with a non-atomic check-then-mark sequence: check_hash_unused/2 reads the dedup store, an eth_getTransactionReceipt round trip verifies the payment on chain, and only then does mark_hash_used/2 write the mark. Concurrent requests carrying the same settled payment hash all pass the read before any of them writes, so each is issued a receipt. The store&#39;s atomic check_and_mark/2 primitive is available and used by the type=&#34;transaction&#34; path, but the hash path calls plain get and put even when the configured store implements it. Exploitation requires a dedup store to be configured; the default nil store is stateless and documented as offering no replay protection at all.</p> <p>This issue affects mpp: from 0.2.0 before 0.6.1.</p> https://cve.radiocsirt.org/vuln/ghsa-vjfr-ffhr-5g8p