Advisories
Coordinated disclosure, made public.
Numbered advisories for vulnerabilities affecting smart contracts, wallets, RPC providers, bridges, and node software. Every advisory is OpenPGP-signed. Search by CVE or GHSA to find our coverage.
158 of 158 advisories
Premia options vaults on Arbitrum drained of about $400k-$465k via empty option pools and flash loans
An attacker drained about $400k-$465k of collateral from six Premia options vaults on Arbitrum on 2026-11-01 by routing vault collateral into attacker-created option pools. Funds were bridged to Ethereum and swapped to BTC. Premia vault depositors should avoid the affected vaults until Premia confirms a fix.
b14g dual-staking protocol on Core: about 97M staked CORE withdrawn without authorization to attacker addresses
About 97M CORE staked through b14g was withdrawn without authorization on 2026-10-31 at 09:29 UTC and sent to attacker addresses. b14g paused the affected contracts. BTC staked via b14g is not affected. Exchanges should flag the two attacker addresses.
Troves xWBTC/WBTC vault on Starknet drained of about 8.57 WBTC via legacy rebalancer that kept vault permissions
On 2026-10-31 an attacker drained about 8.57 WBTC-equivalent (about $667k) from Troves' Ekubo xWBTC/WBTC vault on Starknet through a retired rebalancing contract that still held vault permissions. Troves revoked the permissions and paused affected vaults.
Kintsu DNS Hijack (StepDrainer Campaign)
Kintsu's website was hijacked via a registrar-level DNS attack and rerouted to a StepDrainer wallet-drainer page, in a campaign that also hit Flap and StonkBrokers.
filecoin-pin upload GitHub Action lets fork PRs spend the repository owner's Filecoin wallet
The filecoin-pin upload GitHub Action before 1.1.0 skips its fork check under workflow_run, letting an external contributor's fork PR upload attacker-controlled artifacts using, and spending funds from, the repository's Filecoin wallet. Upgrade to 1.1.0.
CVE-2026-62335: OpenVM
OpenVM is a performant and modular zkVM framework built for customization and extensibility. Before 1.7.0 in the 1.x line and in affected 2.0 and 2.1 prereleases, `OpenVmHalo2Verifier.verify` accepts `appExeCommit` and `appVmCommit` as `bytes32` values without checking that either is less than the `BN254` scalar field modulus. Although public-value and proof-data lengths are checked, callers can provide non-canonical 256-bit encodings greater than or equal to that modulus at the Solidity wrapper boundary. Applications relying on the wrapper can therefore accept non-canonical app executable an…
CVE-2026-62334: OpenVM
OpenVM is a performant and modular zkVM framework built for customization and extensibility. Before 1.7.0 in the 1.x line and in affected 2.0 and 2.1 prereleases, `OpenVmHalo2Verifier.verify` constructs raw proof calldata from user-controlled `proofData`, performs a `staticcall` to `address(this)`, and treats a successful call as proof acceptance. If the first four proof bytes match another external selector exposed by the wrapper, dispatch can invoke a successful non-verifier function instead of the generated Halo2 fallback verifier. Applications using the generated Solidity wrapper can cons…
CVE-2026-117349: Bitcoin Core
Bitcoin Core prior to 29.5, 30.4, 31.2 and 32.1 is vulnerable to an OOM issue.
CVE-2026-117346: Bitcoin Core through 31
Bitcoin Core through 31.1 is vulnerable to Denial of Service via undo files having no size limit
CVE-2026-117350: Bitcoin Core
Bitcoin Core prior to 29.5, 30.4, 31.2 and 32.1 is vulnerable to an OOM issue.
Trezor warns CryptoBilis buyers after reported hardware implant in Safe 5 that may exfiltrate wallet backups
Trezor received a credible, not yet lab-verified report of a cellular hardware implant in a Trezor Safe 5 bought from former reseller CryptoBilis. Anyone who bought a Trezor from CryptoBilis since March 2026 should move funds to a new wallet with a new seed.
Binance Hot-Wallet EIP-7702 Delegation Hack
An attacker hijacked a Binance Ethereum hot wallet via an EIP-7702 delegation and swept an estimated $6.3 billion across several chains — the largest theft in crypto history.
Polymarket DebugBear Supply-Chain Frontend Attack
A compromise of monitoring vendor DebugBear injected malicious JavaScript into Polymarket's international frontend, draining about $2.7M in POL from roughly 700 wallets.
zkLink Nova bridge escrows drained of about $743k-$783k via forged batch root in Arbitrator relay path
An attacker forged a zkLink Nova batch root on Ethereum through a public relayer and the Arbitrator's claimMessage flaw, draining both Ethereum escrows (about $743k-$783k); a second actor repeated it on Optimism, Base, Blast and Mantle. Withdrawals were disabled and contracts patched.
Teku 26.10.3: security release for Ethereum node operators
Teku 26.10.3 (released 2026-10-27) includes security fixes according to its release notes. Ethereum node operators running Teku should review and upgrade.
Fence Finance Tranche Vault Share Inflation
A flash-loan attacker inflated vault share accounting to drain about 1.01 million USDC from an Avalanche Tranche Vault linked to Fence Finance and Valinor Digital.
Besu 26.10.2: security release for Ethereum node operators
Besu 26.10.2 (released 2026-10-26) includes security fixes according to its release notes. Ethereum node operators running Besu should review and upgrade.
Bloom Trading Solana Bot Wallet Drain
A remote code execution flaw in a third-party module let an attacker drain roughly $947,000 in SOL from 49 wallets belonging to nine users of the Bloom Trading Telegram bot.
Avalanche Safe Stale-Approval Drain
A stale, unrevoked token approval let an attacker drain ~$7.45M from a 2-of-7 Safe multisig on Avalanche, but a MEV bot front-ran the theft and returned most funds.
rotki before 1.44.2: unsalted SHA-256 premium sync key lets attackers brute-force encrypted cloud backups
rotki before 1.44.2 derives its premium cloud-backup key from a single unsalted SHA-256 of the user password, so anyone holding a backup blob can guess passwords offline and decrypt exchange API keys and wallet data. Upgrade to 1.44.2 and rotate exchange API keys.
Yapeswap on Ethereum drained of about $21.9k after zero-quorum governance vote handed attacker YapeFactory feeToSetter role
Yapeswap's WorkersUnion governance had zero quorum, letting an attacker with ~0.000055% of voting power take YapeFactory's feeToSetter role and divert YapePair deposits to fake vaults (~$21.9k lost). Avoid Yapeswap pools and revoke approvals.
Keystone hardware wallet web shop breach exposed customer names, contact details and shipping addresses
Keystone says an unauthorized party accessed its official website and obtained customers' names, contact details, shipping addresses and order details; recovery phrases, keys and payment data were not exposed. Expect targeted phishing posing as Keystone refunds or replacement devices.
X100 Global on Ethereum drained of about $4.75M-$4.85M via flash-loan-funded Senate governance takeover
An attacker used flash-loaned funds to take two of X100 Global's three Senate seats and immediately execute a treasury proposal that dumped 400,000 X into an attacker-seeded pool, realising about $4.75M-$4.85M in USDT. Avoid interacting with X100 Freezer/treasury governance until the project publishes guidance.
X100 Global Senate Governance Takeover
A flash loan bought two of three governance Senate seats in a single block, passing a malicious proposal that drained roughly $4.85M from X100 Global's treasury.
Electrum before 4.8.3: malicious server can swap a broadcast tx and trick users into RBF-signing a payment to the attacker
Electrum Bitcoin wallet before 4.8.3 trusts its server for unconfirmed transactions, so a malicious server can substitute a conflicting transaction paying the attacker; fee-bumping it signs a real payment to the attacker. Exploited in the wild. Upgrade to 4.8.3 and verify outputs before signing any fee bump.
Erigon v3.8.1: security release for Ethereum node operators
Erigon v3.8.1 (released 2026-10-23) includes security fixes according to its release notes. Ethereum node operators running Erigon should review and upgrade.
Initia L1 halted after MoveVM mint bug let attacker create unbacked bridged tokens and drain about $2.7M to Ethereum
On 2026-10-23 Initia halted its L1 and rollups after an attacker minted unbacked bridged tokens on Initia and redeemed them via LayerZero and CCTP for about $2.6M-$2.7M of AUSD, ETH and USDC on Ethereum. Initia says native INIT is not affected. Do not bridge to or from Initia until the team confirms a fix.
Fake Solidity interview repo sol-live hides VS Code terminal backdoor that steals wallet and browser data
SlowMist found that 'interview practice' GitHub repositories such as Hylance/sol-live hide malicious VS Code terminal profiles. These download and run an infostealer that targets wallet extensions, browser logins and the Keychain. Inspect .vscode/settings.json before opening a terminal, and hunt for the listed IOCs.
WAX multi-chain bridge exploited to release about $75k-$90k in mapped tokens on Solana and Ethereum
On 2026-10-22 Blockaid flagged an ongoing attack on the WAX multi-chain bridge (WAX, Solana, Ethereum): mapped tokens were withdrawn on WAX without the matching assets being paid in, and the Solana and Ethereum bridge contracts still released the funds. Reported losses are about $75k-$90.5k. Bridge users should hold off on transfers until WAX confirms a fix.
NemTokenV2 (NEM) on BNB Chain exploited for about $822k via LP sell-recycle accounting flaw
SlowMist and CertiK report that the NemTokenV2 ($NEM) contract on BNB Chain was exploited for about $822k. The attacker repeated transfer, skim and flushLpSellRecycle 42 times to burn the PancakeSwap USDT/NEM pair reserves, then sold NEM for USDT. Avoid the pool until the project remediates.
About $16M in USDT and TRX drained from CoinDCX hot wallet and deprecated deposit addresses on Tron
On 2026-10-21 about 15.99M USDT and 5,783.81 TRX moved from CoinDCX's hot wallet and deposit addresses to one Tron address. CoinDCX says the addresses were deprecated after its July 2025 compromise, that it absorbed the losses, and that users were credited. Do not deposit to old CoinDCX addresses.
Swell swETH and rswETH admin keys suspected compromised; malicious upgrade contracts deployed
A researcher reports that Swell's swETH and rswETH admin keys appear compromised, with unbacked NAV increases and four malicious upgrade contracts deployed that could take about 2,500 ETH. Swell is investigating, says no ETH has left its contracts, and says no user action is required.
WAX Bridge Zero-Fee Withdrawal Exploit
A missing fee check in WAX's bridge withdraw function let an attacker pull mapped tokens for free, draining about $90,500 across WAX, Solana and Ethereum.
Solidity compiler bug SOL-2026-7: Yul Optimizer Knowledge Base Stale Bookkeeping
The Yul optimizer could consider two memory or storage locations distinct even though their addresses were computed from different values of the same reassigned variable and coincided at runtime. This could lead to loads being replaced with outdated values and to needed stores being removed. Affects 0.8.19 ≤ solc < 0.8.38.
NemTokenV2 Liquidity Pool Accounting Exploit
A settlement-accounting flaw in the NemTokenV2 contract let an attacker drain its PancakeSwap pool on BNB Chain for roughly $822,000 by repeatedly skimming reserves.
Fearless Wallet browser extension 3.0.1-3.0.5 leaked users' private keys to attacker server since February 2025
The Polkadot Community Foundation reports that the third-party Fearless Wallet browser extension (3.0.1, 3.0.3-3.0.5) sent users' private keys to an attacker-controlled server on unlock since February 2025; 17,286 DOT in losses reported. Anyone who used the extension should create a new keypair in another wallet and move all funds now.
Slice FundsModule on Base drained of about $41k via unverified release amounts from attacker-supplied contracts
An attacker drained about $41k in ETH and USDC store earnings from Slice's FundsModule on Base on 2026-10-20 because a legacy release function trusted payout amounts reported by caller-chosen contracts. Slice has paused and fixed the contracts; affected store owners should check their Slice dashboard.
Erigon v3.8.0: security release for Ethereum node operators
Erigon v3.8.0 (released 2026-10-20) includes security fixes according to its release notes. Ethereum node operators running Erigon should review and upgrade.
Lighthouse v8.3.0: security release for Ethereum node operators
Lighthouse v8.3.0 (released 2026-10-19) includes security fixes according to its release notes. Ethereum node operators running Lighthouse should review and upgrade.
AlpsCon AI Trade Hub on BNB Chain drained of about $152k via whitelisted Hardhat test key and reward-accounting bug
An attacker drained about $152.8k USDC from AlpsCon's AI Trade Hub staking contract on BNB Chain on 18-19 Oct 2026, combining a still-whitelisted Hardhat default account (public key) with a reward-accounting flaw. Projects should purge test accounts from production allowlists.
Predictable Qubic wallet seeds from Apple browsers and early iOS app let attacker drain 1,404 wallets (~$1.3M)
Qubic says weak randomness in wallet seed generation let an attacker drain about 2.94T QU (~$1.3M) from 1,404 wallets on 2026-10-17/18. The network is halted. Treat seeds made on iPhone/iPad browsers, Mac Safari, or the pre-July-2025 iOS app as compromised. Fixed in 4.26.4.
Cysic Bridge Unbacked CYS Mint
An attacker abused Cysic's bridge to mint 10 million unbacked CYS on BNB Chain, dumping most of it for about $727,000 in ETH before the token could be blacklisted.
Ngrave LIQUID Notification Phishing
Attackers hijacked the push-notification provider behind Ngrave's LIQUID app and sent fake alerts that phished recovery phrases, draining about 70 wallets for roughly $2.56 million.
Nethermind 2.2.0: security release for Ethereum node operators
Nethermind 2.2.0 (released 2026-10-16) includes security fixes according to its release notes. Ethereum node operators running Nethermind should review and upgrade.
Besu 26.10.0: security release for Ethereum node operators
Besu 26.10.0 (released 2026-10-16) includes security fixes according to its release notes. Ethereum node operators running Besu should review and upgrade.
CVE-2026-92427: The Coinsnap Bitcoin Crowdfunding WordPress plugin through 1
The Coinsnap Bitcoin Crowdfunding WordPress plugin through 1.2.0 does not restrict access to the secret used to authenticate its payment gateway webhook, disclosing it to unauthenticated users and rendering the webhook's signature check ineffective. This allows unauthenticated attackers to forge payment-confirmation notifications and record arbitrary donations as completed, with attacker-chosen amounts, donor names and messages.
Lighthouse v8.2.0: security release for Ethereum node operators
Lighthouse v8.2.0 (released 2026-10-16) includes security fixes according to its release notes. Ethereum node operators running Lighthouse should review and upgrade.
Lighthouse v8.2.2: security release for Ethereum node operators
Lighthouse v8.2.2 (released 2026-10-16) includes security fixes according to its release notes. Ethereum node operators running Lighthouse should review and upgrade.
Lighthouse v8.2.1: security release for Ethereum node operators
Lighthouse v8.2.1 (released 2026-10-16) includes security fixes according to its release notes. Ethereum node operators running Lighthouse should review and upgrade.
bitcoinj up to 0.17: SSRF in BIP-70 PaymentSession via attacker-controlled payment_url, no fix available
bitcoinj through 0.17 sends BIP-70 Payment messages to an unvalidated payment_url, so a malicious payment request can make the wallet or server issue requests to internal hosts. No fix exists yet; disable BIP-70 payment-request handling or filter destination URLs.
CVE-2026-111171: Web3
Web3.py 7.15.0 through 7.16.0 and 8.0.0b2 through 8.0.0 contains a server-side request forgery vulnerability because _check_ip_blocked() does not unwrap IPv4-mapped IPv6 addresses in CCIP Read URL validation. Malicious contracts can return OffchainLookup URLs with IPv4-mapped IPv6 hosts or AAAA records, making clients with CCIP Read enabled send requests to loopback, private, or link-local services.
Polygon Bor v2.10.3 fixes two BlockSTM V2 denial-of-service bugs that can stall or exhaust PoS nodes
Bor v2.10.1 and v2.10.2 (BlockSTM V2 on by default) carry two Medium DoS bugs, an unbounded keccak256 cache and repeated code hashing, that can delay block import or exhaust memory on Polygon PoS nodes. Upgrade to Bor v2.10.3; no hardfork required.
Jetty EthereumAuthenticator (SIWE) login-path matching flaw lets unauthenticated clients reach protected resources
Eclipse Jetty's jetty-ethereum EthereumAuthenticator 12.1.0–12.1.12 matches the login path as an unanchored substring, so protected routes containing the login path as a later segment can be reached without authentication. Upgrade beyond 12.1.12.
IntentKit through 2.6.3 lets public callers run owner-only tools, including wallet transfers
IntentKit (crestalnetwork/intentkit) through 2.6.3 enforces tool visibility only when advertising tools to the model, not at execution, so a public caller can get owner-only tools such as the wallet transfer tool executed with no approval step. No fixed release was identified; operators of public agents should restrict state-changing tools.
UNCX Smart Token Vesting shared pool on Ethereum drained of about $86k in five ERC-20 tokens
An attacker drained roughly $86k-$88k of EDGEN, ZC, PEPECOIN, LO0P and PAAL from UNCX's shared Smart Token Vesting pool on Ethereum on 14 Oct 2026 (Blockaid, ExVul). UNCX has blocked new vesting positions; holders of affected tokens should follow UNCX's updates.
CVE-2026-93885: The Cryptocurrency Donation Box – Bitcoin & Crypto Donations plugin for WordPres
The Cryptocurrency Donation Box – Bitcoin & Crypto Donations plugin for WordPress is vulnerable to Stored Cross-Site Scripting via data_object Parameter in all versions up to, and including, 2.2.13 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is exploitable by unauthenticated attackers because the cdbbc_payment_verify AJAX action is registered under wp_ajax_nopriv_ and its only authentication gate — a nonce check — is by…
Pirate Chain transaction-validation flaw exploited to mint about 39.8M ARRR (about 20% of supply)
On 2026-10-14, an attacker exploited a Pirate Chain (ARRR) validation flaw to mint about 39.8M ARRR; SlowMist puts the loss at about $10.7M. Users are asked not to move funds, and exchanges and pools to pause ARRR operations, while a rollback is considered.
Gamdom Hot-Wallet Breach
A server intrusion drained crypto casino Gamdom's hot wallets across several chains for roughly $4.2 million in a suspected key compromise.
Autheo THEO unbacked Hyperlane warp-route mint on Base drains about $1.7M
An attacker minted 19M unbacked THEO on Base through Autheo's Hyperlane warp route, then swapped it for about 700.8 ETH (~$1.76M per PeckShield) and bridged the ETH to Ethereum. Autheo says not to buy, sell, or bridge THEO until it gives an all-clear.
Unauthenticated security-check bypass in Pay With MetaMask for WooCommerce plugin up to 1.7.2
The WordPress plugin Pay With MetaMask For WooCommerce (Cryptocurrency Payment Gateway) up to 1.7.2 has an unauthenticated bypass vulnerability (CWE-345, CVSS 5.3). Update to 1.7.3 or later.
Papertrade Launch-Day Price Manipulation
A trader moved Hyperliquid's ETH reference price while holding leveraged Papertrade positions, netting about $1.28 million from the platform's shared USDC pool on launch day.
xrpld 3.4.0 and earlier: payment-engine integer overflow allowed minting XRP; Batch wrapper validation gap
An integer overflow in the xrpld payment engine (3.4.0 and earlier) let a crafted set of offers plus one payment mint spendable XRP. A Batch wrapper validation gap also risked a consensus halt. Both are fixed in xrpld 3.4.1, and no exploitation was found. Operators must run 3.4.1 or later; older servers are now amendment blocked.
Ledger CryptoBilis Reseller Supply-Chain Drain
An estimated $86 million was drained from Ledger users who bought devices from reseller CryptoBilis, in a suspected supply-chain attack that captured their seed phrases.
go-ethereum v1.17.8 security release fixes p2p DoS issues and a STUN-response node crash
go-ethereum (Geth) v1.17.8 is a security-focused release fixing several denial-of-service risks in the eth/snap p2p handlers, JUMPDEST analysis caching, BAL account handling, and a crash triggered by a rogue STUN server. Most fixes concern post-Amsterdam behaviour. Node operators should upgrade to v1.17.8.
79th Vault (79AU) operator-key compromise drains about $12.5M from the 79AU/USDT pool on BNB Chain
On 7 Oct 2026 the 79th Vault operator key was used to move 2.01M 79AU out of the PancakeSwap 79AU/USDT pair and sell it, a loss of about $12.5M (16,249 BNB) per CertiK, Defimon and GoPlus. Do not interact with the attacker addresses listed; follow 79th Vault's official channels.
Malicious npm packages hardhat-option and hardhat-promised impersonate Hardhat and load a wallet-data stealer
Typosquatted npm packages hardhat-option@2.0.1 and hardhat-promised@2.21.0 run an obfuscated loader on import that beacons to a C2 at 167.88.172.33:8087 and spawns file-upload and browser-wallet LevelDB stealer modules. Remove them and treat affected hosts and keys as compromised.
79thVault Operator Key Compromise
An attacker used the 79thVault operator's leaked key to drain a 79AU PancakeSwap pool for ~$12.5M on BNB Chain; most funds were later returned.
CVE-2026-106511: MultiversX's multisig-improved (repository: mx-multisig-and-modules) reference i
MultiversX's multisig-improved (repository: mx-multisig-and-modules) reference implementation of their on-chain multisig smart contract system contains a vulnerability where a missing independent authorization check allows any account with the Proposer role to perform explicitly barred actions. This vulnerability allows the Proposer role to move funds alone, draining 100% of a contract's EGLD/ESDT balance in two transactions with zero signatures.
Vyper: Memory corruption using function calls within tuples / nested calls
Vyper: Memory corruption using function calls within tuples / nested calls. When performing a function call inside a tuple or as an argument inside another function call, there is a memory corruption issue that occurs because of an incorrect pointer to the the tip of the stack.
Vyper: Call stack corruption when passing complex type containing non-base type members as argument
Vyper: Call stack corruption when passing complex type containing non-base type members as argument. When we pass a multi-dimensional array (like [[1, 2], [3, 4]]) as an argument to internal/external functions we get incorrect output. This is due to a stack management issue, because it was assumed that the size of each subtype of an array/struct is 32, which is not always correct.
Vyper: Return inside for loop more than 1 level deep
Vyper: Return inside for loop more than 1 level deep. Earlier today, we received a responsible disclosure of a potential issue from @michwill (developer of @curvefi) for Vyper users who use return statements inside for loops of nested internal calls.
MakerDAO ETH-A Liquidation Keeper Bot exploit — $538k lost on Ethereum
MakerDAO ETH-A Liquidation Keeper Bot lost an estimated $538k on Ethereum (improper access control), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
Base wstETH Vault Whitelist Exploit
An attacker whitelisted a fresh contract on an unidentified Base vault and borrowed against its Aave V3 position to drain about 1,783 wstETH, roughly $6 million.
Core Lightning urges upgrade from 26.06.7 and earlier as attackers target unpatched nodes
Core Lightning says attackers are targeting nodes running 26.06.7 or earlier. Releases 26.06.8 and 26.06.9 fix remote node crashes, unauthenticated clnrest memory exhaustion, rune restriction bypasses and fund-loss bugs. Upgrade Lightning nodes to 26.06.9 now.
GoldPesa exploit — $115k lost on Base
GoldPesa lost an estimated $115k on Base (incorrect share accounting), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
Lighthouse v8.2.3: security release for Ethereum node operators
Lighthouse v8.2.3 (released 2026-10-01) includes security fixes according to its release notes. Ethereum node operators running Lighthouse should review and upgrade.
NEAR Intents exploit — $3.8M lost on BNB Chain
NEAR Intents lost an estimated $3.8M on BNB Chain (bridge logic flaw), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
FlashLoopAdapter exploit — $305k lost on Ethereum
FlashLoopAdapter lost an estimated $305k on Ethereum (improper access control), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
SKYDAO exploit — $183k lost on BNB Chain
SKYDAO lost an estimated $183k on BNB Chain (swap logic flaw), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
Besu 26.9.0: security release for Ethereum node operators
Besu 26.9.0 (released 2026-09-28) includes security fixes according to its release notes. Ethereum node operators running Besu should review and upgrade.
CVE-2026-48100: Payy
Payy is an Ethereum L2 zk-rollup for privacy preserving and regulatory compliant transactions. Prior to version 1.3.0, agg_agg forwards the compacted message stream from its inner proofs into a public messages: [Field; 1000] array, but it never checks that the unused tail of the outer array is zero. A registered prover can build a valid agg_final proof for an approved rollup block while inserting an extra burn message after the real messages. RollupV1.verifyRollup() then parses that public input as a normal burn and transfers USDC from the rollup contract to the attacker. This is a severe cir…
Fake GIWA Bridge social-engineering incident — $2.1M lost on Ethereum
Fake GIWA Bridge lost an estimated $2.1M on Ethereum (impersonation scam), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
CVE-2026-100248: The Rattadan Cosmowarp smart contract
The Rattadan Cosmowarp smart contract before 56c6147 can have a comparison to an unintended value of current_admin.
CVE-2026-61604: The ixo Blockchain
The ixo Blockchain is a Layer 1 blockchain that runs on both Testnet and Mainnet. Prior to version 8.0.0, the x/bonds module moved funds from an address that was resolved from a DID verification method, without verifying that the resolved address belonged to the transaction signer. Affected handlers included MsgMakeOutcomePayment, MsgBuy, MsgSell, MsgSwap, and MsgWithdrawShare, as well as the batch order processor. Because any account may list an arbitrary blockchainAccountID as a verification method on a DID it controls (without the consent of that address's owner), an attacker could registe…
Payy Network exploit — $1.8M lost on Ethereum
Payy Network lost an estimated $1.8M on Ethereum (bridge logic flaw), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
Limit Break Payment Processor exploit — $1.8M lost on Ethereum, ApeChain, Polygon, Base
Limit Break Payment Processor lost an estimated $1.8M on Ethereum, ApeChain, Polygon, Base (token approval abuse), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
Duelbits key compromise — $7.0M lost on Ethereum, BNB Chain, Bitcoin, Tron
Duelbits lost an estimated $7.0M on Ethereum, BNB Chain, Bitcoin, Tron (hot wallet key compromised), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
Bitget key compromise — $387.0M lost on Ethereum, XRP, Tron, Zcash
Bitget lost an estimated $387.0M on Ethereum, XRP, Tron, Zcash (hot wallet key compromised), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
CVE-2026-19125: The EthPress – Web3 Login plugin for WordPress
The EthPress – Web3 Login plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 2.3.5. This is due to the verify_login() function in app/Login.php containing a missing return statement in the signature verification failure branch — when Signature::verify2() reports a mismatch, the function only assigns a WP_Error to a local variable and continues executing, causing unconditional fall-through to the login block where Address::log_in() calls wp_set_auth_cookie() regardless of whether the submitted signature is valid. This makes it possible for unauthe…
CVE-2026-86065: Klever-Go
Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, the default-open GET /subscribe endpoint in network/api/websocket/routes.go accepts unauthenticated WebSocket clients with permissive origin handling, does not call SetReadLimit to bound message size, and has no live-connection cap. SocketHub.HandleClientInsertion also accepts an unbounded address list that grows addressSubscription, and client.loopIn continues reading without a size limit, allowing one client to grow subscription maps or many clients to retain goroutines, buffered channels, and descriptors…
CVE-2026-86064: Klever-Go
Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, the default-open GET /log WebSocket route configured in config/node/api.yaml and registered by network/api/api.go does not require authentication. The first client message is parsed as a logger Profile in network/api/logs/logSender.go and applied process-wide through Profile.Apply, allowing a remote client to change global log levels and formatting options until the connection closes. The same connection is registered as a log observer and can receive live process logs. An attacker can suppress normal logs,…
CVE-2026-82409: Klever-Go
Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, indexer/common.go serializedDataForUpdateAccounts places the attacker-controlled acc.Name value into an Elasticsearch _bulk JSON and NDJSON request without escaping it. The SetAccountName transaction accepts valid UTF-8 account names containing quotes, backslashes, and newlines, and the resulting name is stored in consensus account state. When an indexer processes the account, those characters can break the JSON string, reject a bulk batch, or inject additional bulk actions that create, overwrite, or delete…
CVE-2026-82407: Klever-Go
Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, core/kapp/validators/validators.go Register and the runtime validator update path accept a submitted BLSPublicKey without curve, prime-order subgroup, or nonzero validation. When a validator with a malformed key becomes eligible and is selected into a consensus group, MultiSigner.Reset and the corresponding signature verification creation path cannot deserialize the group key and cancel the slot. This causes repeated missed rounds and throughput degradation, and a network whose consensus group equals the el…
CVE-2026-82406: Klever-Go
Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, the native marketplace function core/kapp/market/market.go Buy does not check IsClaimed before accepting a bid. A seller can use the Claim seller-accept branch to settle a resting-bid auction while leaving the claimed order loadable with a future EndTime and stale CurrentBid and CurrentBidder values. A later bidder can submit a higher bid, be debited, and cause the previous bidder to receive a refund even though the NFT has already been delivered. Because Claim and CancelOrder reject the later bidder when I…
CVE-2026-82405: Klever-Go
Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, the KleverUpdateAccountPermission built-in authorizes replacement of a target account's permissions by checking attacker-controlled vmInput.RecipientAddr instead of authenticated vmInput.CallerAddr. An attacker-controlled contract can choose a victim account with configured permissions as RecipientAddr, and contractHasValidPermission can accept the victim's default self-signer as authorization. UpdatePermission can then replace the victim's entire permission set with attacker-supplied Owner permissions, ena…
Meter Passport Unbacked Mint Exploit
An attacker abused a block-validation flaw in Meter to mint unbacked wrapped MTRG through the Meter Passport bridge, dumping about $2.3 million of it on PancakeSwap and crashing both MTR and MTRG.
Drop exploit — $4.4M lost on Neutron
Drop lost an estimated $4.4M on Neutron (malicious proposal), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
Astroport exploit — $4.9M lost on Neutron
Astroport lost an estimated $4.9M on Neutron (malicious proposal), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
Neutron Governance Takeover
An attacker bought cheap voting power to pass a malicious Neutron governance proposal, seizing admin rights over ten Astroport and Drop contracts and draining about $9.4 million in 24 minutes.
Fetch.ai key compromise — $1.5M lost on Ethereum
Fetch.ai lost an estimated $1.5M on Ethereum (private key compromised), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
NuNet key compromise — $463k lost on Ethereum
NuNet lost an estimated $463k on Ethereum (private key compromised), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
ASI Alliance SingularityNET Bridge Key Compromise
A compromised bridge signing key let an attacker drain FET and mint AGIX, NTX and WMTx across the ASI Alliance's Ethereum token-conversion contracts, amassing roughly $16.77 million in tokens.
Nostra Money Market exploit — $3.5M lost on Starknet
Nostra Money Market lost an estimated $3.5M on Starknet (spot price manipulation), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
Flamincome exploit — $595k lost on Ethereum
Flamincome lost an estimated $595k on Ethereum (spot price manipulation), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
D'CENT App Wallet Key Compromise
Attackers used compromised recovery phrases to sweep roughly 11.7 million XRP — about $18 million — from over 6,600 D'CENT App Wallet accounts across five chains.
CVE-2026-57583: OpenZeppelin Contracts Wizard
OpenZeppelin Contracts Wizard is a web application to interactively build a contract out of components from OpenZeppelin Contracts. Prior to @openzeppelin/wizard 0.10.11, @openzeppelin/wizard-cairo 3.0.1, @openzeppelin/wizard-stellar 0.6.2, and @openzeppelin/wizard-stylus 0.3.1, the setInfo code path prints info.securityContact and info.license verbatim into single-line comments in generated Solidity, Cairo, Stellar/Soroban, and Stylus source. A line terminator ends the comment and causes following input to be emitted as source declarations. Exploitation requires an integration to populate th…
Chainflip AMM exploit — $736k lost on Tron
Chainflip AMM lost an estimated $736k on Tron (bridge logic flaw), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
Solidity compiler bug SOL-2026-5: Memory Byte Array Element Delete Clears Whole Word
Applying ``delete`` to a single element of a ``bytes`` array in memory clears not only that element but the whole 32-byte word starting at the element's location, zeroing up to 31 bytes beyond the element. Affects solc < 0.8.37.
Symbiosis exploit — $336k lost on BNB Chain, Ethereum
Symbiosis lost an estimated $336k on BNB Chain, Ethereum (unbacked cross-chain mint), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
Solidity compiler bug SOL-2026-6: Misordered Named Parameters In Require With Custom Errors
Custom error arguments passed to ``require`` using named-parameter syntax are ABI-encoded in call-site order instead of declaration order when compiling via IR. Affects 0.8.26 ≤ solc < 0.8.37.
Solidity compiler bug SOL-2026-4: Spill Slot Collision Across Mutual Recursion
Local variables of two simultaneously active functions moved to fixed memory offsets by the stack limit evader may be assigned the same offset if the call graph contains mutual recursion, so that one variable is silently overwritten by the other. Affects 0.7.2 ≤ solc < 0.8.37.
Erigon v3.6.1: security release for Ethereum node operators
Erigon v3.6.1 (released 2026-09-09) includes security fixes according to its release notes. Ethereum node operators running Erigon should review and upgrade.
Nomic exploit — $3.1M lost on Nomic
Nomic lost an estimated $3.1M on Nomic (unbacked cross-chain mint), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
Zentra Finance exploit — $140k lost on Citrea
Zentra Finance lost an estimated $140k on Citrea (rounding error), according to the DeFiLlama hacks database. Users and integrators should review exposure and follow the project's official channels.
Solidity compiler bug SOL-2026-3: Inheritance Order Reversal On Storage End Warning
Emitting a warning about storage base location being too close to the storage end unintentionally reversed the ``linearizedBaseContracts`` annotation, possibly leading to miscompilation due to reversing the order in which inheritance is resolved. Affects 0.8.29 ≤ solc < 0.8.36.
Solidity compiler bug SOL-2026-2: Unsound Spill In Mutual Recursion
Local variables of a function involved in mutual recursion may spuriously be moved to fixed memory offsets and overwritten across recursive calls. Affects 0.7.2 ≤ solc < 0.8.36.
Zebra: Missing copy constraint in halo2_gadgets variable-base scalar multiplication allows under-constrained base, breaking Orchard Action circuit soundness
Zebra: Missing copy constraint in halo2_gadgets variable-base scalar multiplication allows under-constrained base, breaking Orchard Action circuit soundness. A soundness vulnerability in the variable-base scalar multiplication gadget of halo2gadgets allowed a malicious prover to produce a valid proof for an Orchard Action with an under-constrained base point.
Zebra Address Book Aborted by IPv4-Mapped Mempool Misbehavior Update
Zebra Address Book Aborted by IPv4-Mapped Mempool Misbehavior Update. You are affected if: 1. You run zebrad up to and including v4.4.1. 2. Your node listens on the default [::] address on a Linux host (the standard deployment configuration — net.
zebrad has unbounded memory leak in mempool download pipeline via timeout path cancel_handles retention
zebrad has unbounded memory leak in mempool download pipeline via timeout path cancel_handles retention. You are affected if: 1. You run zebrad up to and including v4.4.1. 2. Your node accepts inbound P2P connections (network.listenaddr is set, which is the default).
zebrad has persistent on-disk corruption of Sapling/Orchard subtree roots after chain fork via pop_tip
zebrad has persistent on-disk corruption of Sapling/Orchard subtree roots after chain fork via pop_tip. You are affected if: 1. You run zebrad up to and including v4.4.1. 2. Your node participates in a network where chain forks occur (mainnet, testnet, or any network with multiple miners).
Zebra: Repeated Non-Finalized Shielded Transaction Aborts Zebra Before Duplicate-Nullifier Rejection
Zebra: Repeated Non-Finalized Shielded Transaction Aborts Zebra Before Duplicate-Nullifier Rejection. You are affected if: 1. You run zebrad up to and including v4.4.1. 2. Your node processes blocks past the checkpoint height (non-finalized state is active). 3. The network has NU5 or later activated.
Zebra: Finalized address balance credit-first overflow on consensus-valid blocks
Zebra: Finalized address balance credit-first overflow on consensus-valid blocks. You are affected if: 1. You run zebrad up to and including v4.4.1. 2. Your node processes blocks on any Zcash network. The finalized transparent address balance writer processes all newly-created outputs (credits) before processing spent outputs (debits) within the same block.
Zebra has sync restart poisoning from single unauthenticated peer via above-lookahead block
Zebra has sync restart poisoning from single unauthenticated peer via above-lookahead block. You are affected if: 1. You run zebrad up to and including v4.4.1. 2. Your node accepts inbound P2P connections and is syncing or catching up to the chain tip. A malicious peer can answer Zebra's outbound getblocks/FindBlocks request with a small two-hash inventory, then serve a syntactically valid block whose coinbase height is far above the victim's local tip.
zebrad has consensus divergence via P2SH sigop undercount in pure-Rust disabled-opcode parser
zebrad has consensus divergence via P2SH sigop undercount in pure-Rust disabled-opcode parser. You are affected if: 1. You run any version of zebrad up to and including v4.4.1. 2. Your node validates blocks on mainnet, testnet, or any network where both Zebra and zcashd nodes participate.
Zebra has block suppression via NU5 same-header body poisoning of sent-hash cache
Zebra has block suppression via NU5 same-header body poisoning of sent-hash cache. You are affected if: 1. You run any version of zebrad up to and including v4.4.1. 2. Your node accepts inbound P2P connections (network.listenaddr is set, which is the default).
Zebra has pre-handshake buffer capacity reservation based on attacker-claimed body length
Zebra has pre-handshake buffer capacity reservation based on attacker-claimed body length. You are affected if: 1. You run zebrad up to and including v4.4.1. 2. Your node accepts inbound P2P connections (network.listenaddr is set, which is the default).
zebrad has mempool transaction admission denial via single-peer inbound queue saturation
zebrad has mempool transaction admission denial via single-peer inbound queue saturation. You are affected if: 1. You run zebrad up to and including v4.4.1. 2. Your node accepts inbound P2P connections (network.listenaddr is set, which is the default).
zebrad vulnerable to full node denial of service via crafted Sapling receiver in z_listunifiedreceivers
zebrad vulnerable to full node denial of service via crafted Sapling receiver in z_listunifiedreceivers. You are affected if: 1. You run zebrad up to and including v4.4.1. 2. Your zebrad.toml sets rpc.listenaddr to a TCP address (RPC server is enabled). 3. An attacker can authenticate to the RPC endpoint.
zebrad vulnerable to getblocks/getheaders locator CPU amplification via uncapped vector length
zebrad vulnerable to getblocks/getheaders locator CPU amplification via uncapped vector length. You are affected if: 1. You run zebrad up to and including v4.4.1. 2. Your node accepts inbound P2P connections. The readgetblocks and readgetheaders codec paths accepted block locator vectors up to approximately 65,535 entries (the generic TrustedPreallocate ceiling derived from MAXPROTOCOLMESSAGELEN), rather than the protocol-specification limit of 101 entries (matching zcashd's MAXLOCATORSZ).
zebrad has full node denial of service via non-ASCII LongPollId in getblocktemplate
zebrad has full node denial of service via non-ASCII LongPollId in getblocktemplate. You are affected if: 1. You run zebrad up to and including v4.4.1. 2. Your zebrad.toml sets rpc.listenaddr to a TCP address (RPC server is enabled). 3. An attacker can authenticate to the RPC endpoint.
Anchor: `InterfaceAccount` allows account substitution between unexpected types
Anchor: `InterfaceAccount` allows account substitution between unexpected types. Any uses of InterfaceAccount allows another unexpected account type to be passed, after https://github.com/solana-foundation/anchor/pull/3837 disabled discriminator checking for this type.
Anchor: Program<'info, System> is not properly validated
Anchor: Program<'info, System> is not properly validated. An logic error causes anchor programs to accept any program id when requiring the system program id, causing false assumptions resulting in potential arbitrary cpi in programs that invoke system program instructions.
Zebra has Permanent Block Discovery Halt via Gossip Queue Saturation and Syncer Poisoning
Zebra has Permanent Block Discovery Halt via Gossip Queue Saturation and Syncer Poisoning. A composite denial-of-service vulnerability in Zebra's block discovery pipeline allows an unauthenticated remote attacker to permanently halt all new block discovery on a targeted node.
Zebra v4.4.0 still accepts V5 SIGHASH_SINGLE without a corresponding output
Zebra v4.4.0 still accepts V5 SIGHASH_SINGLE without a corresponding output. Zebra failed to enforce a ZIP-244 consensus rule for V5 transparent transactions: when an input is signed with SIGHASHSINGLE and there is no transparent output at the same index as that input, validation must fail.
Zebra's Transparent SIGHASH_SINGLE Handling Diverges from zcashd for Corresponding Outputs
Zebra's Transparent SIGHASH_SINGLE Handling Diverges from zcashd for Corresponding Outputs. For V5+ transparent spends, Zebra and zcashd disagree on the same consensus rule: SIGHASHSINGLE must fail when the input index has no corresponding output. zcashd treats this as consensus-invalid under ZIP-244, while Zebra's transparent verification path computes a digest for the missing-output case instead of failing.
Zebra has Consensus Divergence in Transparent Sighash Hash-Type Handling due to Stale Buffer
Zebra has Consensus Divergence in Transparent Sighash Hash-Type Handling due to Stale Buffer. The fix for https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-8m29-fpq5-89jj introduced a separate issue due to insuficient error handling of the case where the sighash type is invalid, during sighash computation.
Zebra Vulnerable to Allocation Amplification in Inbound Network Deserializers
Zebra Vulnerable to Allocation Amplification in Inbound Network Deserializers. Several inbound deserialization paths in Zebra allocated buffers sized against generic transport or block-size ceilings before the tighter protocol or consensus limits were enforced.
Zebra's Block Validator Undercounts Coinbase and P2SH Sigops
Zebra's Block Validator Undercounts Coinbase and P2SH Sigops. Zebra's block validator undercounts transparent signature operations against the 20000-sigop block limit (MAXBLOCKSIGOPS), allowing it to accept blocks that zcashd rejects with bad-blk-sigops.
Zebra Vulnerable to Consensus Divergence in Transparent Sighash Hash-Type Handling
Zebra Vulnerable to Consensus Divergence in Transparent Sighash Hash-Type Handling. After a refactoring, Zebra failed to validate a consensus rule that restricted the possible values of sighash hash types for V5 transactions which were enabled in the NU5 network upgrade.
Zebra Vulnerable to Denial of Service via Interrupted JSON-RPC Requests from Authenticated Clients
Zebra Vulnerable to Denial of Service via Interrupted JSON-RPC Requests from Authenticated Clients. A vulnerability in Zebra's JSON-RPC HTTP middleware allows an authenticated RPC client to cause a Zebra node to crash by disconnecting before the request body is fully received.
Zebra has rk Identity Point Panic in Transaction Verification
Zebra has rk Identity Point Panic in Transaction Verification. Orchard transactions contain a rk field which is a randomized validating key and also an elliptic curve point. The Zcash specification allows the field to be the identity (a "zero" value), however, the orchard crate which is used to verify Orchard proofs would panic when fed a rk with the identity value.
Zebra: addr/addrv2 Deserialization Resource Exhaustion
Zebra: addr/addrv2 Deserialization Resource Exhaustion. When deserializing addr or addrv2 messages, which contain vectors of addresses, Zebra would fully deserialize them up to a maximum length (over 233,000) that was derived from the 2 MiB message size limit.
Zebra: Cached Mempool Verification Bypasses Consensus Rules for Ahead-of-Tip Blocks
Zebra: Cached Mempool Verification Bypasses Consensus Rules for Ahead-of-Tip Blocks. A logic error in Zebra's transaction verification cache could allow a malicious miner to induce a consensus split. By carefully submitting a transaction that is valid for height H+1 but invalid for H+2 and then mining that transaction in a block at height H+2, a miner could cause vulnerable Zebra nodes to accept an invalid block, leading to a consensus split from the rest of the Zcash network.
web3.py: SSRF via CCIP Read (EIP-3668) OffchainLookup URL handling
web3.py: SSRF via CCIP Read (EIP-3668) OffchainLookup URL handling. web3.py implements CCIP Read / OffchainLookup (EIP-3668) by performing HTTP requests to URLs supplied by smart contracts in offchainlookuppayload["urls"].
Zebra has a Consensus Failure due to Improper Verification of V5 Transactions
Zebra has a Consensus Failure due to Improper Verification of V5 Transactions. --- A logic error in Zebra's transaction verification cache could allow a malicious miner to induce a consensus split. By matching a valid transaction's txid while providing invalid authorization data, a miner could cause vulnerable Zebra nodes to accept an invalid block, leading to a consensus split from the rest of the Zcash network.
Zebra node crash — V5 transaction hash panic (P2P reachable)
Zebra node crash — V5 transaction hash panic (P2P reachable). --- A vulnerability in Zebra's transaction processing logic allows a remote, unauthenticated attacker to cause a Zebra node to panic (crash). This is triggered by sending a specially crafted V5 transaction that passes initial deserialization but fails during transaction ID calculation.
Cosmos EVM: incorrect state handling during nested EVM execution paths
Cosmos EVM: incorrect state handling during nested EVM execution paths. Advisory ID: ASA-2026-002 Component: ICS20 Precompile Status: Resolved Published: March 2026 Contact: security@cosmoslabs.io --- Status: Resolved. A patch is available and all known affected chains have either applied mitigations or upgraded.
Go Ethereum Improperly Validates the ECIES Public Key in RLPx Handshake
Go Ethereum Improperly Validates the ECIES Public Key in RLPx Handshake. Through a flaw in the ECIES cryptography implementation, an attacker may be able to extract bits of the p2p node key. The issue is resolved in the v1.16.9 and v1.
Go Ethereum affected by DoS via malicious p2p message
Go Ethereum affected by DoS via malicious p2p message. A vulnerable node can be forced to shutdown/crash using a specially crafted message. More details to be released later. The problem is resolved in the v1.16.9 and v1.
Go Ethereum affected by DoS via malicious p2p message
Go Ethereum affected by DoS via malicious p2p message. An attacker can cause high memory usage by sending a specially-crafted p2p message. More details to be released later. The issue is resolved in the v1.17.0 release.
Solidity compiler bug SOL-2026-1: Transient Storage Clearing Helper Collision
Clearing both storage and transient storage variables in the same contract may result in only one of these locations being cleared. Affects 0.8.28 ≤ solc < 0.8.34.
CometBFT has inconsistencies between how commit signatures are verified and how block time is derived
CometBFT has inconsistencies between how commit signatures are verified and how block time is derived. Name: CSA-2026-001: Tachyon Criticality: Critical (Catastrophic Impact; Possible Likelihood per ACMv1.
go-ethereum is vulnerable to high CPU usage leading to DoS via malicious p2p message
go-ethereum is vulnerable to high CPU usage leading to DoS via malicious p2p message. Impact An attacker can cause high CPU usage by sending a specially crafted p2p message. More details to be released later.
go-ethereum is vulnerable to DoS via malicious p2p message affecting a vulnerable node
go-ethereum is vulnerable to DoS via malicious p2p message affecting a vulnerable node. Impact A vulnerable node can be forced to shutdown/crash using a specially crafted message. More details to be released later. Credit This issue was reported to the Ethereum Foundation Bug Bounty Program by DELENE TCHIO ROMUALD.
Elliptic Uses a Cryptographic Primitive with a Risky Implementation
Elliptic Uses a Cryptographic Primitive with a Risky Implementation. The ECDSA implementation of the Elliptic package generates incorrect signatures if an interim value of 'k' (as computed based on step 3.2 of RFC 6979 https://datatracker.
Solidity compiler bug SOL-2025-1: Lost Storage Array Write On Slot Overflow
Operations that involve clearing or copying from arrays that straddle the end of storage could result in silent data retention. Affects 0.1.0 ≤ solc < 0.8.32.
Cosmos EVM Vulnerability
Cosmos EVM Vulnerability. Patched in versions v0.3.1, v0.4.2, and in the v0.5.0 release. More information will be disclosed at a later point to ensure chains have time to safely upgrade. No workarounds for chains that make use of static or dynamic precompiles.
CometBFT's invalid BitArray handling can lead to network halt
CometBFT's invalid BitArray handling can lead to network halt. Name: ASA-2025-003: Invalid BitArray handling can lead to network halt Criticality: High (Considerable Impact; Possible Likelihood per ACMv1.2) Affected versions: <= v0.