Vaults created before 12 October 2026: what to do
Summary. Since 15 July 2026, whoever was in the creation room: a member, the relay we operate, or whoever had the invite (and the PIN, if there was one), could obtain the group key; since 29 August, also the vault’s access secret. We fixed the creation on 12 October. Vaults that already existed stay as they were, and this notice says what to do with them.
Who is affected
- A vault that requires fewer approvals than the number of members (for example, 2 of 3): it could be spent without the quorum, and its balance, history and memos could be read.
- A vault that requires everyone’s approval (2 of 2): it could not be spent without the quorum, by our analysis; its balance, history and memos could be read.
Whoever obtained the key or the read access before the update still has it. Only a new vault changes that.
What the update changes
- A vault that already exists: nothing changes. The key and the secret are the same; updating the app does not replace them.
- A new vault, created with the updated app: the key swap that allowed this is no longer possible. Before any secret, all members read a code to each other. The check depends on people reading the code with all the listed members.
- A new vault, created with the old app: it is still accepted, until the coordinator starts refusing it (see “What is still open”).
What was wrong
When a vault was created, each device sent secret material sealed to a key that the other device announced, and nobody verified that the key really belonged to it. A member, or the relay, could announce its own key in its place and receive what was meant for someone else. With that, in partial-quorum vaults it could rebuild the group key; in any vault, it could obtain read access.
Whether it was used
We do not know. From what we read in the code, using this flaw does not change the group key, the address or the signatures, and the relay keeps the creation traffic only in memory, for about an hour. We have not yet reproduced this in a test (see “What is still open”).
What to do
- Create a new vault with the same members, all present.
- Each device shows a code.
- Everyone reads it aloud.
- They only confirm if it matches.
- Send the funds from the old vault to the new one, with the old vault’s quorum approving.
- Keep the old vault until the new one shows the funds.
- Update the app:
- Web: already updated.
- Desktop: through the v0.13.1 installer.
Creating a new vault protects what comes afterwards. It does not undo a read that has already happened.
What changed
- 12 October (v0.12.0): creation requires a code that all members read to each other before any secret is sent.
- v0.13.0: before signing, the device reads the payment and shows the recipient, amount and fee with the full address. On this device, it refuses to sign a second transaction for the same approval without the explicit confirmation of the member who signs.
- v0.13.1: a screen opened while the vault is busy keeps what it showed. The update banner says which version replaces which and sits above the menu. The version appears in the app.
What is still open
- The old app still creates vaults the old way.
- Plan: the new app already sends a field that identifies the app’s version. When the new desktop installer is available and a notice period has passed, the coordinator will refuse registrations without it.
- Status: the new app is live. The coordinator already records the field and still refuses nothing; the refusal is ready and switched off, with no date. We will say here when it is switched on.
- Issue: #670.
- The old app shows no warning, and the desktop has no updater.
- Plan: signed installers and an updater.
- Status: open.
- Issue: #606.
- The approval still comes from the coordinator at signing time.
- Plan: bind it to the content between devices.
- Status: in design, for review.
- Issue: #567.
- Reading a new vault is not yet guaranteed.
- Plan: bind it to the creation.
- Status: in design.
- Issue: no public number until fixed.
- We have not reproduced the problem in a test, and we have not checked the coordinator’s records.
- Plan: run the proof of concept with two devices and a relay that swaps the announced key, and count, in the coordinator’s vaults, devices above n or without a seat.
- Status: specified, not yet run. The result will be posted in this topic.
- Issue: #671.
Timeline
- 15 July 2026: the first version of the creation screen already worked this way.
- 11 October: found by an internal code review, done by us with the help of AI.
- 12 October: fixed in v0.12.0.
- 14 October: v0.13.0 and v0.13.1 live on the web.
- 15 October: this notice.
Contact
- Forum: a private message to me (@danielgorgonha).
- GitHub: a private security advisory at github.com/deegalabs/konclave/security/advisories/new.
Do not send a passphrase or the full vault identifier.