Skip to main content
CVE-2026-115770VulnerabilityPublished

github.com/pocket-id/pocket-id/backend · Pocket ID: Email verification token remains valid after address change, enabling arbitrary verified-email spoofing

Affects github.com/pocket-id/pocket-id/backendSource GCVE Database

0
Compare
Authoritative record:CVE-2026-115770· Critical 9.6

Not known to be exploited · CVSS 9.6 Critical : upgrade to 0.0.0-20260727180059-43aaccd5bfac as a priority.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 3.1 base score
9.6Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.19.6
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.0.0-20260727180059-43aaccd5bfac
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade github.com/pocket-id/pocket-id/backend to 0.0.0-20260727180059-43aaccd5bfac.

Affected software

ProductAffectedFixed in
Gogithub.com/pocket-id/pocket-id/backendAffected
  • <0.0.0-20260727180059-43aaccd5bfac
Fixed in
  • 0.0.0-20260727180059-43aaccd5bfac

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in version 0.0.0-20260727180059-43aaccd5bfac that fixes this issue by properly binding email verification tokens to the specific email address. Users of affected versions should upgrade to this fixed version. Until patched, relying parties should avoid trusting the 'email_verified' claim alone for account linking or provisioning, or implement additional verification controls. No other immediate actions are indicated by the vendor advisory.

Description

An authenticated Pocket ID user can exploit a flaw where an email verification token remains valid after changing the account email address. The token is bound only to the user ID, not the email address, allowing the attacker to verify an email address they do not control. This leads to the system marking the new email as verified without proof of control. Consequently, relying parties that trust the verified email claim in OIDC can be tricked into linking the attacker's identity to a victim's account, enabling cross-application account takeover.

References

Community reviews

Loading reviews…