LiveActive security incident?Get immediate response
CVE Record

CVE-2026-55954: Missing ID token claim validation in ueberauth_apple allows account takeover

Authentication Bypass by Spoofing vulnerability in ueberauth ueberauth_apple allows account takeover via unvalidated ID token claims. The Ueberauth.Strategy.Apple.Token.payload/2 function verifies the JWT signature of the callback id_token against Apple's JWKS but does not validate any registered claims. The iss, aud, exp, and iat claims are read from the token and passed on to Ueberauth.Strategy.Apple.handle_callback!/1, which derives the logged-in user's uid and email directly from the unvalidated sub claim. An attacker who obtains any Apple-signed ID token bearing the victim's sub (via a captured expired token, or via an ID token issued to a sibling client in the same Apple developer team) can replay it against the vulnerable callback and be authenticated as the victim. The absent exp check makes stolen tokens usable indefinitely, and the absent aud check enables cross-application account takeover across clients that share an Apple developer team. This issue affects ueberauth_apple: from 0.1.0 before 0.6.2.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Applications using vulnerable ueberauth_apple for Sign in with Apple may let an attacker log in as another user if they possess a qualifying Apple-signed ID token. The library verified the token signature but failed to check key claims that prove the token is current and intended for that application.

Executive priority

Treat as urgent for any customer-facing Apple login flow. The impact is account takeover, the CVSS score is 9.1, and the fix is identified. Prioritize inventory and upgrade over broad compensating controls.

Technical view

Ueberauth.Strategy.Apple.Token.payload/2 validates the JWT signature against Apple JWKS but does not validate iss, aud, exp, or iat. handle_callback!/1 then derives uid and email from the unvalidated sub claim. Sources state ueberauth_apple versions from 0.1.0 before 0.6.2 are affected.

Likely exposure

Exposure is limited to Elixir/Phoenix applications that use ueberauth_apple versions before 0.6.2 for Apple authentication, especially where Apple developer team clients are shared across applications.

Exploitation context

No active exploitation is cited, and KEV is false. The source bundle describes replay risk using a captured expired Apple ID token or a token issued to a sibling client in the same Apple developer team.

Researcher notes

Focus validation on claim enforcement, not signature verification alone. The key exposure is acceptance of Apple-signed tokens without iss, aud, exp, or iat checks, allowing stale-token replay and cross-client acceptance as described by the advisory.

Mitigation direction

  • Upgrade ueberauth_apple to version 0.6.2 or later.
  • Review the GitHub advisory and patch notes before deployment.
  • Invalidate sensitive sessions after upgrading, based on business risk.
  • Audit Apple authentication logs for unusual cross-client or stale-token sign-ins.
  • Check vendor guidance if upgrade constraints exist.

Validation and detection

  • Check dependency manifests and lockfiles for ueberauth_apple versions below 0.6.2.
  • Confirm Apple login callbacks reject expired tokens.
  • Confirm callbacks reject tokens with the wrong audience.
  • Review code paths deriving user identity from Apple ID token claims.
  • Verify production deployments run the fixed dependency version.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-290: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-55954 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NEEF

Vulnerability scoring details

Base CVSS 4.0 score

9.1Critical
CVSS 4.0 vector shape for CVE-2026-55954Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ueberauthueberauth_appleueberauth_apple, 0.1.0unaffected
ueberauthueberauth_appleueberauth/ueberauth_apple, 3908a187d045c75994b62ce340c3aa26bb8976b8unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-290 · source CWE mapping

Authentication Bypass by Spoofing

Authentication Bypass by Spoofing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.