Back to the CVE list
CVE-2026-62662

Pocket ID: Client credentials grant allows any OIDC client to obtain tokens for arbitrary audiences

CVSS score

7.7

EPSS probability

—

Risk score

0.8

Published

3 h ago

Patch status has not yet been verified

Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.

Impact on My Inventory

Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.

Checking session…

Vulnerability description

DayBreach AI Explanation

Verified against sources

CVE-2026-62662: Pocket ID Authorization Bypass Vulnerability

Sources read

1

Source agreement

Tam uyum

Evidence confidence

%55

Short explanation

CVE-2026-62662 in Pocket ID allows any authenticated OIDC client to obtain tokens for arbitrary audiences due to missing resource validation in the client credentials grant.

Why does it matter?

This vulnerability bypasses audience-based access controls and can permit unauthorized data access or actions in affected deployments.

What should be done?

  • Upgrading to version 2.10.0 or later
  • Following the vendor security advisory
Chain of evidence and sources2 verified claims

Pocket ID, OIDC istemcilerinin hedef kitle doğrulaması olmadan rastgele kitleler için belirteç almasına izin verir.

Bu güvenlik açığı 1.11.0 sürümünden 2.10.0 sürümüne kadar olan sürümleri etkiler.

Show the technical text from the sources

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.

CVSS vector: CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N

CWE: CWE-20, CWE-863

This explanation was compiled automatically from the source records. Scores, active exploitation, patch and exploit status come straight from the sources.

IMPACT: Affected Products and Software

Affected Products

The following products are affected by CVE-2026-62662 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.

IDVENDORPRODUCTACTION
1pocket-idpocket-id View
Total affected vendors: 1|Products: 1

RED HAT CSAF/VEX: Product Impact Check

Red Hat has not yet published a CSAF/VEX impact record for this CVE. This does not mean “not affected”.

SCORING: CVSS from Multiple Sources

CVSS Scores

The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.

SCOREVERSIONSEVERITYVECTORSOURCE
7.7CVSS V3_0HIGHCVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:NCVE CNA
7.7CVSS V30HIGHCVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:NNVD

Patch and Remediation Guide

Solution & Remediation Advisory

Patch status unknown

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Confirm the affected product and version against the source evidence above.
Restrict access to internet-facing services and apply network segmentation.
Until a patch is confirmed, follow the vendor advisory; do not read an unknown status as “no patch”.
Monitor server logs and network endpoints for signs of anomalous execution.

Public exploit and active exploitation status

Verified exploit intelligence

No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.

Weakness Classification and Attack Patterns (CWE & CAPEC)

CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-62662 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-62662 weaknesses.

Attack Vector and Accessibility

ExposureAğ üzerinden
PermissionsHigh
UserGerekmiyor

Official Sources and Advisories

CVSS Vector Radar Chart

7.7 / 10
Attack VectorNetworkComplexityHighPrivilegesHighUser Interact.NoneConfidentialityHighIntegrityNoneAvailabilityNone

Vulnerability Scoring Details

CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N
Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredHigh privileges
User InteractionNone required
Confidentiality (Gizlilik)High
Integrity (Bütünlük)None
Availability (Erişilebilirlik)None

Yama durumu bilinmiyor

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Follow the vendor

Weakness Type (CWE & CAPEC)

Similar Vulnerabilities

Get this vulnerability through the API

Affected products, version ranges, exploitation status and patch information in a single request, with a free key.

curl -H "x-api-key: $DAYBREACH_API_KEY" \
  "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-62662"
CVE-2026-62662 · Pocket ID: Client credentials grant allows…