Security check
Was my seed affected by the 2026 Coldcard flaw? A two-minute check
In July 2026, Coinkite disclosed a firmware bug that made some Coldcard seeds far easier to guess. Whether yours is affected depends on how the seed was created, not on the firmware your device runs today. Answer a few questions and you will see where you stand and what to do.
Rules last checked: , against Coinkite's, Coldcard's and Block's own pages.
The check
Answer one question at a time. Change any answer and the result updates. Most people know the model and
roughly when they set the wallet up; for everything else, I don't know
is a fine answer.
The rules in full
These are the same rules the check uses, taken from Coinkite's advisory, Coldcard's migration guide and Block's analysis. You can reach your answer from this section alone; it works without JavaScript.
Step 1. Where did the seed words come from?
| If the words were created by… | Result |
|---|---|
| A wallet, app or method that is not a Coldcard, and no Coldcard ever created them | This issue does not apply. Check your own device on our advisories page. |
| Another wallet or method, then imported into a Coldcard | Not affected by this issue: importing does not weaken a seed (Coldcard). |
| A Coldcard Mk1 | Not affected (Block). |
| A TAPSIGNER, SATSCARD or OPENDIME | Not affected (Coinkite). |
| A Coldcard Mk2, Mk3, Mk4, Q or Mk5, even if you later moved the words to another device | Go to step 2. Restoring, importing or cloning a seed does not change it (Coldcard, Block). |
| You don't know | Treat it as affected (Coldcard). |
Step 2. Which firmware did the Coldcard have when it created the words?
| Model and track | Affected if created on | Not affected if created on |
|---|---|---|
| Mk2, Mk3 | 4.0.1 to 4.1.9 (29 March 2021 to 31 July 2026) | 3.2.2 or older (before 29 March 2021), or 4.2.0 |
| Mk4, Mk5 standard | Any version before 5.6.0 | 5.6.0 or later |
| Mk4, Mk5 Edge | Any version before 6.6.0X | 6.6.0X or later |
| Q standard | Any version before 1.5.0Q | 1.5.0Q or later |
| Q Edge | Any version before 6.6.0QX | 6.6.0QX or later |
- Use the date if you don't know the version. Every fixed release came out on 31 July 2026 (release tags on GitHub). Every earlier Mk4, Q and Mk5 version had the bug (Block), so a seed those models created before that date is affected unless the dice exception in step 3 applies.
- Edge and standard are separate tracks. A higher Edge number does not by itself mean the fix is included (Coinkite).
- What counts is the firmware when the words were created. Updating later does not repair the seed (Coinkite).
- Still don't know the version, the date or even the model? Treat the seed as affected, unless the dice exception in step 3 applies.
Step 3. The dice exception
If the seed was created on affected firmware but you also entered dice rolls, it may still be safe from this issue. Coinkite's exception needs all four of these:
- at least 50 fair, independent rolls of a six-sided die;
- entered through the Add Dice Rolls option when the seed was created;
- rolls that nobody else saw and that were never written down, photographed or saved;
- you use the final words the Coldcard showed after the rolls.
With all four, Coinkite does not consider the seed at risk from this issue: 50 to 98 rolls added at least 128 bits of your own randomness, and 99 or more about 256 bits. With fewer than 50 rolls, or any doubt, treat the seed as affected (Coinkite advisory). Why 50? Our dice rolls calculator shows the arithmetic.
Step 4. How urgent is it?
| Your situation | What it means |
|---|---|
| Funds behind the seed alone, or a short, memorable or reused passphrase | Act now. Start the migration today, step by step. |
| Funds behind a strong, random, unique BIP-39 passphrase | Plan a calm migration, soon. The passphrase is a second lock but does not repair the seed (Coinkite). |
| Multisig | Count the affected keys. If they reach the number needed to spend, act now; if not, replace the affected key calmly (Block). |
| No funds in any wallet on the seed, including passphrase wallets (empty or test wallet) | Nothing at risk today. Don't fund it; create a new seed on fixed firmware for real use. |
| Not sure whether it holds funds | Treat it as funded. |
The passphrase is the BIP-39 passphrase, not the Coldcard PIN (Coinkite).
What to do if your seed is affected
- Erase nothing yet. Test the written backup of your current words and note the wallet's fingerprint (the 8-character XFP code the Coldcard shows) before you erase or replace anything: on a single Coldcard, Coldcard's steps erase the old seed from the device before they make the new one. Coldcard:
Never destroy the only working copy of a wallet. Never rely on an untested backup.
(Coldcard migration guide). How to test it: testing your seed phrase backup; step 1 of our guide. - Install fixed firmware downloaded only from coldcard.com/downloads, after checking the SHA-256 hash and the signed signatures file. As of 3 November 2026 the current standard releases are 5.6.3 (Mk4, Mk5) and 1.5.3Q (Q); 4.2.0 is the final Mk2/Mk3 release (Coldcard security status). Step 3 of our guide.
- Create a completely new seed on fixed firmware, ideally on a second device. With only one Coldcard, follow the one-device path in Coldcard's migration guide: it switches between the old and new seeds, so both backups must be tested first. Never reuse the old words, and don't use Clone, which copies them. Step 4 of our guide.
- Test, then move everything. A small test to an address checked on the device screen, then the rest, for every funded wallet on the old seed. Step 5 of our guide.
- Remake other secrets made on the same firmware: paper-wallet keys, random Seed XOR splits, generated Secure Notes passwords. If you never used these features, skip this step. Our answer.
- Keep the old backup and the old device until the migration is confirmed (Coinkite asks owners not to dispose of affected devices).
The full explanation, with the reasons behind each step, is in our guide The Coldcard seed entropy flaw: who's at risk and exactly what to do. Coldcard publishes its own version in its migration guide.
Five common mistakes
I updated the firmware, so I'm fine.
An update fixes seeds created from then on. A seed created before stays exactly as weak as it was.I restored the words on a new device.
Same words, same weakness, on a Coldcard or any other brand.I used Clone to move to my new Coldcard.
Clone copies the old seed; it does not create a new one.My passphrase fixes it.
A strong one adds a lock. Coinkite still asks you to migrate as soon as practical.A website or support agent can check my seed.
No legitimate company asks for your words, and no honest website will offer to check them. Coldcard's own guide says never to enter them into a website or send them to support. Anyone asking is trying to steal them (Coldcard).
Check you've understood
Ana created her seed on a Coldcard Mk4 in 2024. In August 2026 she updated to 5.6.3. Is her seed affected?
Yes. Every Mk4 version before 5.6.0 had the bug, and updating later does not change a seed that already exists. Unless she added 50 or more private dice rolls, she needs a new seed and to move her funds.
Ben's words came from another brand of hardware wallet. In 2025 he imported them into a Coldcard Q. Is his seed affected?
Not by this issue. Coldcard's guide says a seed created safely elsewhere is not weakened by being imported into a Coldcard.
Carla created her seed on a Coldcard Mk3 in 2022, then restored the same words on a different brand. Is it affected?
Yes. In 2022 the Mk3 ran affected firmware (4.0.1 to 4.1.9), unless she had stayed on 3.2.2 or older. Moving the words to another device does not change them.
Sources, checked 3 November 2026
- Coinkite, Coldcard Security Advisory (30 July 2026; current guidance dated 14 August 2026): affected ranges, fixed releases, dice and passphrase rules, and the warning that rushing a migration creates its own risk.
- Coldcard, Migrate an Affected COLDCARD Seed (last reviewed 30 August 2026): imported and cloned seeds, unknown origin, Clone, testing the old backup first, the one-device path, migration steps.
- Coldcard, Passphrase documentation: back the passphrase up exactly and separately, record the wallet fingerprint, test it with a power cycle; a lost or mistyped passphrase cannot be recovered.
- Coldcard, Current COLDCARD Security Status (verified by Coinkite on 1 October 2026): current releases.
- Block Engineering, Predictable RNG Fallback and 32-Bit Reseed in COLDCARD Firmware (30 July 2026): Mk1, firmware up to 3.2.2, Mk4/Q/Mk5 production firmware, exported seeds, multisig, other secrets.
- Coinkite, Technical Deep Dive into the Entropy Issue: the estimates of about 40 bits (Mk2/Mk3) and about 72 bits (Mk4, Q, Mk5).
- Coinkite, Update, Sunday (2 August 2026): keep affected devices.
- Coldcard firmware on GitHub: Mk3 release history (4.0.1 on 29 March 2021, 3.2.2 on 14 January 2021) and release tags (5.6.0, 1.5.0Q, 4.2.0, 6.6.0X and 6.6.0QX tagged on 31 July 2026).
- Coinkite, Historical disclosures: firmware 4.0.0 was an internal build, never released, so the affected public releases start at 4.0.1.
Found a rule that no longer matches the sources? Our corrections log records every fix.