# CVE-2026-115770: Pocket ID: Email verification token remains valid after address change, enabling arbitrary verified-email spoofing

Status: published. Published: 2026-11-04. Updated: 2026-11-04.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- pocket-id / pocket-id: >= 2.2.0, < 2.12.0 (affected). Source: CNA: GitHub_M

## Severity and prioritization

- CVSS 3.1: 9.6 (critical); CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N; source: CNA: GitHub_M

- CVSS 3.1: 9.6 (critical); CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N; source: NVD: security-advisories@github.com

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-345

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://github.com/pocket-id/pocket-id/security/advisories/GHSA-rm8c-2cv8-jwf6 (CNA: GitHub_M; x_refsource_CONFIRM)

- https://github.com/pocket-id/pocket-id/pull/1625 (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/pocket-id/pocket-id/commit/43aaccd5bfacb76283b11ce039fb3f0716196fcb (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/pocket-id/pocket-id/releases/tag/v2.12.0 (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/pocket-id/pocket-id/commit/43aaccd5bfacb76283b11ce039fb3f0716196fcb (security-advisories@github.com)

- https://github.com/pocket-id/pocket-id/pull/1625 (security-advisories@github.com)

- https://github.com/pocket-id/pocket-id/releases/tag/v2.12.0 (security-advisories@github.com)

- https://github.com/pocket-id/pocket-id/security/advisories/GHSA-rm8c-2cv8-jwf6 (security-advisories@github.com)

## Provenance

- CNA: GitHub_M: https://www.cve.org/CVERecord?id=CVE-2026-115770; retrieved 2026-11-04; source updated 2026-11-04

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115770; retrieved 2026-11-05; source updated 2026-11-04

Revision: e3e22b38ae2a7df562d35328e5e9505c959a38da33c91b31405d85cee05c8959

Canonical: https://y2.dev/cve/CVE-2026-115770

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.