On this page (7 sections)
Pocket ID, a self-hosted OIDC provider that signs users in with passkeys, has a critical flaw in how it handles email verification. According to the GitHub advisory, an ordinary signed-in user can get Pocket ID to report an email address as verified even though they never proved they control it.
If you run Pocket ID, or you operate an application that signs users in through it and matches accounts by email, you should care. The fix is in version 2.12.0.
What happened
Pocket ID can send a user a token to prove they own their email address. The advisory says that token is tied only to the user's account ID, not to the address it was sent to. Changing the account email does not cancel tokens that are already outstanding.
The result is a gap between what was proven and what is recorded. A user proves control of one address, switches the account to a different address, and then redeems the old token. Pocket ID then marks the new address as verified and passes it to other applications with email_verified set to true.
Technical details
The weakness class is CWE-345: the system accepts a piece of data (the token) as proof of something it never actually established. A verification token should answer the question "did the person at this address click this link?" Here it only answers "did this account request a token at some point?"
According to the advisory, these conditions must hold:
- The attacker has an ordinary Pocket ID user account. No administrator rights are needed.
- Email verification is in use with emailsVerified=false, which is the default.
- Users may edit their own account (allowOwnAccountEdit=true), which is also the default.
- The target address is not already assigned to another Pocket ID user.
- For the downstream takeover, a relying application links or provisions users based on a trusted, verified email.
The advisory states that no victim interaction and no access to the victim's mailbox is required. The advisory also includes a regression test; this article does not reproduce it or the request sequence. The research lists pull request 1625, a fix commit and the v2.12.0 release as references for the fix.
Who is realistically exposed
Two groups are affected, and the second is easy to overlook.
- Pocket ID operators running a version from 2.2.0 up to but not including 2.12.0 with the default settings. Any user with an account can attempt the attack.
- Owners of relying applications (wikis, dashboards, internal tools, self-hosted services) that use Pocket ID for sign-in and automatically match or create accounts from the email claim.
The advisory says applications that rely exclusively on the stable OIDC sub claim are not affected by the downstream consequence. The Pocket ID instance itself is still running a flawed verification flow, so update it regardless.
How to check your exposure
- Find which Pocket ID version you run, from the release or image tag you deployed. Anything from 2.2.0 up to but not including 2.12.0 is affected.
- Check your relying applications. For each one, find out whether it links or creates accounts by email and whether it trusts email_verified, or whether it keys accounts on the sub claim.
- Review your Pocket ID settings for emailsVerified and allowOwnAccountEdit. The advisory names the defaults (false and true) as the affected configuration.
- Look through your user list for recent, unexpected email changes, and compare against account records in downstream apps.
If you run Pocket ID in Docker, this read-only command lists running containers with their names and image tags, so you can see which version is deployed. Run it on the Docker host and look for the Pocket ID image:
docker ps --format '{{.Names}}\t{{.Image}}'What to do now
- Upgrade Pocket ID to 2.12.0 or later, following your normal deployment method.
- Confirm the new version is running after the restart.
- Audit downstream applications for accounts that were linked or created by email, and look for any that do not match the person who owns them.
- Where possible, change relying apps to match users on the stable sub claim rather than email.
- If an app must use email, require its own email confirmation before linking an existing account.
- Review Pocket ID users for unexpected email changes since you installed 2.2.0 or later, and investigate any you cannot explain.
- If you find a suspicious link, remove it in the downstream app and reset access for the affected user.
Detection and monitoring
The research does not describe specific log signatures for this issue, so do not rely on a fixed pattern. Instead, look at behavior: an account whose email changes shortly after a verification email was requested, and that ends up verified, deserves a second look. Compare the timing of email changes with sign-ins in your relying applications.
Going forward, keep your identity provider on a patch watch list, as it sits in front of many other services. If you expose it publicly, a certificate and uptime monitor helps you notice expired certificates or outages that affect sign-in, and the free SSL checker gives a quick look at the certificate itself. Neither detects this flaw; the fix is the upgrade.
Timeline
| Date | Event |
|---|---|
| Jul 29, 2026 | GitHub advisory GHSA-rm8c-2cv8-jwf6 published |
| Nov 4, 2026 | CVE record published, CVSS 9.6 |
| Nov 9, 2026 | GitHub advisory last updated |
Only one independent publisher, the GitHub advisory, covers this story so far. Details here come from that advisory and the CVE record, and may be refined as more information appears. For broader guidance on keeping sign-in and accounts safe, see our small business website security guide.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
