CVE-2026-115770

Received Received - Intake

Email Verification Bypass in Pocket ID

Publication date: 2026-11-04

Last updated on: 2026-11-04

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-11-04

Last Modified

2026-11-04

Generated

2026-11-05

AI Q&A

2026-11-05

EPSS Evaluated

N/A

NVD

CVE-2026-115770

Affected Vendors & Products

Vendor	Product	Version / Range
pocket-id	pocket-id	>= 2.2.0, < 2.12.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-345	The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.

Attack-Flow Graph

Executive Summary

Pocket ID is an OIDC provider that allows passkey authentication. From versions 2.2.0 to 2.12.0, a flaw exists in the email verification process. An attacker can request a verification token for an email they control, change the account email to a new unused address, and then use the old token to verify the new address. This allows the attacker to mark the new address as verified without proper validation.

Impact Analysis

If you rely on Pocket ID for authentication, an attacker could link their identity to your account by exploiting this flaw. This could lead to unauthorized access or account takeover if the relying application trusts the verified email for matching or provisioning. Applications using the stable OIDC sub claim are not affected.

Compliance Impact

This vulnerability could compromise data integrity and user authentication, potentially violating GDPR's requirements for secure identity verification and HIPAA's access control standards. Unauthorized account linking may lead to unauthorized data access, impacting compliance with these regulations.

Mitigation Strategies

Upgrade Pocket ID to version 2.12.0 or later to address the vulnerability. Review configurations to ensure email verification tokens are invalidated when account emails are changed.

Hi! I’m here to help you understand CVE-2026-115770. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70

EPSS Chart

Security Radar

News mentioning this vulnerability

Loading related security news...