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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

EPSS

• CVE-2026-115770: 0.17% estimated exploitation activity in the next 30 days; percentile 5.97 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary An authenticated Pocket ID user can request an email-verification token while their account uses an address they control, change the account email address, and then redeem the previously issued token. The token is bound only to the user ID, not to the address to which it was sent, and changing the address does not revoke outstanding tokens. As a result, Pocket ID marks the newly supplied address as verified even though the user never proved control of it. Pocket ID subsequently returns that address with `email_verified: true` in OIDC claims. A relying party that trusts this claim for email-based account linking or provisioning can therefore link the attacker's Pocket ID identity to a victim's existing account, leading to cross-application account takeover. This was verified against commit `9f559788a44cfea790de360da0a74d4bdf8ca5d5`.

Preconditions - The attacker has an ordinary Pocket ID user account. - Email verification is in use (`emailsVerified=false`, which is the…

Published by the source

9 Nov 2026, 22:12 UTC

Last modified by the source

9 Nov 2026, 22:30 UTC

Source last checked

10 Nov 2026, 06:45 UTC

1. Revision 2 · amended · 10 Nov 2026

   Amended from osv record GHSA-rm8c-2cv8-jwf6

2. Revision 1 · created · 9 Nov 2026

   Published from ghsa record GHSA-rm8c-2cv8-jwf6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-115770

Advisory: Pocket ID: Email verification token remains valid after address change, enabling arbitrary verified-email spoofing
IDs: CVE-2026-115770, GHSA-rm8c-2cv8-jwf6
Record: https://patchnext.com/advisories/cve-2026-115770 (revision 2, source checked 10 Nov 2026, 06:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/pocket-id/pocket-id/backend 0.0.0-20260727180059-43aaccd5bfac. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/pocket-id/pocket-id/backend: affected < 0.0.0-20260727180059-43aaccd5bfac; fixed in 0.0.0-20260727180059-43aaccd5bfac

## Suggested inspection (read-only)
- Go github.com/pocket-id/pocket-id/backend: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/pocket-id/pocket-id/backend.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-rm8c-2cv8-jwf6 (GitHub-reviewed advisory GHSA-rm8c-2cv8-jwf6 lists affected ranges: Go github.com/pocket-id/pocket-id/backend >=0 <0.0.0-20260727180059-43aaccd5bfac)
- Verified: https://osv.dev/vulnerability/GHSA-rm8c-2cv8-jwf6 (OSV record GHSA-rm8c-2cv8-jwf6 lists affected ranges: Go github.com/pocket-id/pocket-id/backend >=0 <0.0.0-20260727180059-43aaccd5bfac (fixed))

Commands are suggestions: review each one before running it.