Pocket ID is an OIDC provider that allows users to authenticate with their passkeys to services. From 2.6.0 until 2.9.0, frontend/src/routes/authorize/+page.ts reads the redirect_uri query parameter and frontend/src/routes/authorize/+page.svelte uses the raw callbackURL in redirectWithError when prompt=none cannot complete silent authorization. The client-side path only blocks javascript and data schemes and does not invoke the backend callback allow-list validation, so an unauthenticated attacker who knows a valid client_id can redirect a victim browser to an arbitrary HTTP or HTTPS origin for phishing or OIDC error and state smuggling. This issue is fixed in version 2.9.0.
CVE-2026-55834
This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(low)
- EG Risk
- 35(Track)EG Risk 35/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 computedSeverity43% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 19%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (3)
Auto-updated Aug 28, 2026Open Redirect on the OIDC /authorize page via unvalidated redirect_uri with prompt=none · Advisory · pocket-id/pocket-id · GitHub
https://github.com/pocket-id/pocket-id/security/advisories/GHSA-2wvm-8mvp-22qvv2.9.0
Patch available: pocket-id/pocket-id v2.9.0
https://github.com/pocket-id/pocket-id/releases/tag/v2.9.0commit 8a7577497131 (pocket-id/pocket-id)
Fix landed in pocket-id/pocket-id commit 8a7577497131 — awaiting tagged release
https://github.com/pocket-id/pocket-id/commit/8a7577497131229badb35cb4b3a4227b1300afffVendor Advisories for CVE-2026-55834(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 22:48 UTCEG score recompute
- 2026-08-28 22:09 UTCEG score recompute
- 2026-08-28 20:25 UTCEG score recompute
- 2026-08-28 17:11 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-601
Frequently asked(5)
What is CVE-2026-55834?
When was CVE-2026-55834 disclosed?
Is CVE-2026-55834 actively exploited?
What is the CVSS score of CVE-2026-55834?
How do I remediate CVE-2026-55834?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-55834
Is Your Infrastructure Affected by CVE-2026-55834?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.