Auth bypass in Pocket-Id
CVE-2026-62662
Pocket ID is an OIDC provider that allows users to authenticate with their passkeys to services. From 1.11.0 until 2.10.0, createTokenFromClientCredentials in backend/internal/service/oidc_service.go accepts the client-controlled resource parameter and embeds it directly in the access token aud claim without validating that the audience is registered or that the requesting client may access it. Any authenticated OIDC client can therefore obtain a Pocket ID-signed token naming another client or an arbitrary audience. The /api/oidc/introspect endpoint cannot distinguish the unauthorized token because it treats a token as active when the introspecting client's identifier matches the attacker-selected audience. In deployments where resource servers trust Pocket ID access tokens for service-to-service authorization, this bypasses audience-based access controls and can permit unauthorized data access or actions; deployments that do not use these tokens for resource-server authorization have no immediate exploitable impact. This issue is fixed in version 2.10.0.
Vulnerability class: Drupalgeddon 2 (CVE-2018-7600)
Published .
CVSS v3 metric
CVSS v3 base score 7.7 (High). Vector: CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
- Pocket-Id — versions >= 1.11.0, < 2.10.0
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2026-62662?
- CVE-2026-62662 is a high-severity vulnerability in Pocket-Id, classified under Improper Input Validation. CVSS score: 7.7/10. Published 2026-11-04.
- How severe is CVE-2026-62662?
- High severity. CVSS v3 base score is 7.7 out of 10.