CVE-2026-55954

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 50% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
57(Track*)
EG Risk 57/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 15, 2026

Advisory Details (4)

Auto-updated Aug 29, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github Patch Available🟡 PoC Available

"Sign in with Apple" id_token claims not verified · Advisory · ueberauth/ueberauth_apple · GitHub

https://github.com/ueberauth/ueberauth_apple/security/advisories/GHSA-pxx8-68pc-p9mr
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-55954
github_commit

commit 01e2d9c9b313 (ueberauth/ueberauth_apple)

Fix landed in ueberauth/ueberauth_apple commit 01e2d9c9b313 — awaiting tagged release

https://github.com/ueberauth/ueberauth_apple/commit/01e2d9c9b3134e1b78633ad82d136d5ff4a61f28

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
ueberauth_apple0.1.0 ... 0.6.1 (6 versions)0.6.2

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 55× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 05:24 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-27 21:33 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 23:56 UTCEG score recompute
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 19:12 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 19:50 UTCEG score recompute
  11. 2026-08-24 09:35 UTCEG score recompute
  12. 2026-08-23 03:31 UTCEG score recompute
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-22 01:14 UTCEG score recompute
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-20 23:13 UTCEG score recompute
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-20 00:34 UTCEG score recompute
  19. 2026-08-19 17:04 UTCEPSS rescore
  20. 2026-08-18 20:05 UTCEG score recompute
  21. 2026-08-18 13:48 UTCEPSS rescore
  22. 2026-08-17 15:26 UTCEG score recompute
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-16 18:02 UTCEG score recompute
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 58 more
  1. 2026-08-16 05:11 UTCEG score recompute
  2. 2026-08-16 02:14 UTCEPSS rescore
  3. 2026-08-15 03:30 UTCEG score recompute
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 01:50 UTCEG score recompute
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-12 15:36 UTCEG score recompute
  8. 2026-08-12 13:51 UTCEPSS rescore
  9. 2026-08-11 17:51 UTCEG score recompute
  10. 2026-08-11 00:45 UTCEG score recompute
  11. 2026-08-11 00:00 UTCEPSS rescore
  12. 2026-08-09 13:48 UTCEG score recompute
  13. 2026-08-09 13:46 UTCEPSS rescore
  14. 2026-08-08 20:41 UTCEG score recompute
  15. 2026-08-08 16:37 UTCEPSS rescore
  16. 2026-08-07 19:01 UTCEG score recompute
  17. 2026-08-06 17:19 UTCEG score recompute
  18. 2026-08-06 13:47 UTCEPSS rescore
  19. 2026-08-05 19:56 UTCEG score recompute
  20. 2026-08-05 19:17 UTCEPSS rescore
  21. 2026-08-04 18:09 UTCEG score recompute
  22. 2026-08-04 15:10 UTCEPSS rescore
  23. 2026-08-04 13:23 UTCEG score recompute
  24. 2026-08-04 10:39 UTCEPSS rescore
  25. 2026-08-03 13:26 UTCEG score recompute
  26. 2026-08-03 10:36 UTCEPSS rescore
  27. 2026-08-02 03:05 UTCEG score recompute
  28. 2026-08-02 02:27 UTCEPSS rescore
  29. 2026-08-01 05:40 UTCEG score recompute
  30. 2026-08-01 04:16 UTCEPSS rescore
  31. 2026-07-30 19:02 UTCEG score recompute
  32. 2026-07-30 16:28 UTCEPSS rescore
  33. 2026-07-30 10:00 UTCEG score recompute
  34. 2026-07-30 05:41 UTCEG score recompute
  35. 2026-07-30 01:30 UTCEPSS rescore
  36. 2026-07-30 01:30 UTCEPSS rescore
  37. 2026-07-28 17:39 UTCEG score recompute
  38. 2026-07-28 15:37 UTCEPSS rescore
  39. 2026-07-27 15:20 UTCEG score recompute
  40. 2026-07-26 16:08 UTCEG score recompute
  41. 2026-07-26 14:54 UTCEPSS rescore
  42. 2026-07-26 11:46 UTCEG score recompute
  43. 2026-07-25 14:18 UTCEPSS rescore
  44. 2026-07-24 14:18 UTCEPSS rescore
  45. 2026-07-23 14:18 UTCEPSS rescore
  46. 2026-07-23 03:20 UTCEG score recompute
  47. 2026-07-22 14:08 UTCEPSS rescore
  48. 2026-07-21 15:25 UTCEPSS rescore
  49. 2026-07-20 17:08 UTCEPSS rescore
  50. 2026-07-19 14:31 UTCEPSS rescore
  51. 2026-07-19 14:31 UTCEPSS rescore
  52. 2026-07-19 02:29 UTCEPSS rescore
  53. 2026-07-18 10:04 UTCEPSS rescore
  54. 2026-07-16 17:03 UTCEPSS rescore
  55. 2026-07-15 16:57 UTCEPSS rescore
  56. 2026-07-15 16:57 UTCEPSS rescore
  57. 2026-07-14 15:41 UTCEG score recompute
  58. 2026-07-14 15:40 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-55954?
CVE-2026-55954 is a critical vulnerability published on July 14, 2026. 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 idtoken against Apple's JWKS but does not validate any registered…
When was CVE-2026-55954 disclosed?
CVE-2026-55954 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55954 actively exploited?
CVE-2026-55954 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 49.8% of all scored CVEs.
What is the CVSS score of CVE-2026-55954?
CVE-2026-55954 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-55954?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55954, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55954

Explore →

Is Your Infrastructure Affected by CVE-2026-55954?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.