Skip to main content

Threats Tagged 'cve-2026-73829'

View all threats tagged with 'cve-2026-73829'. Filter and sort to focus on specific types of threats.

Pro Console Lifetime

Stop chasing alerts. Route them.

Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.

Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Tag: cve-2026-73829

Threats Tagged 'cve-2026-73829'

Click on any threat for detailed analysis and mitigation recommendations

A Time-of-check Time-of-use (TOCTOU) race condition exists in ZenHive mpp that allows an unauthenticated remote client to redeem a single confirmed on-chain payment multiple times for paid-resource accesses. The vulnerability arises because the 'hash' credential verification path uses a non-atomic check-then-mark sequence, enabling concurrent requests with the same payment hash to bypass replay protection. This affects versions from 0.2.0 up to but not including 0.6.1. The default configuration does not provide replay protection, and exploitation requires a deduplication store to be configured.

Join the discussion

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. The type="hash" 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's atomic check_and_mark/2 primitive is available and used by the type="transaction" 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. This issue affects mpp: from 0.2.0 before 0.6.1.

Join the discussion

Showing 1 to 2 of 2 results

Filters:Tag: cve-2026-73829
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses