CVE-2026-55834

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% 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
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: Elevated riskExposed: 0

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

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.

CVSS v3
4.3
EG Score
4.3(medium)
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 computed
Severity43% × 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

September 9, 2026

Advisory Details (3)

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

Open 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-22qv
github_release Patch Available

v2.9.0

Patch available: pocket-id/pocket-id v2.9.0

https://github.com/pocket-id/pocket-id/releases/tag/v2.9.0
github_commit

commit 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/8a7577497131229badb35cb4b3a4227b1300afff

Vendor 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.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/pocket-id/pocket-id/backend2.9.0

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 40× 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-09-20 20:16 UTCEPSS rescore
  2. 2026-09-20 16:18 UTCEG score recompute
  3. 2026-09-19 14:32 UTCEG score recompute
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 12:43 UTCEG score recompute
  6. 2026-09-17 19:31 UTCEPSS rescore
  7. 2026-09-17 10:57 UTCEG score recompute
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 09:11 UTCEG score recompute
  10. 2026-09-16 05:15 UTCEPSS rescore
  11. 2026-09-15 06:04 UTCEG score recompute
  12. 2026-09-15 03:11 UTCEPSS rescore
  13. 2026-09-14 04:15 UTCEG score recompute
  14. 2026-09-13 16:47 UTCEPSS rescore
  15. 2026-09-13 02:30 UTCEG score recompute
  16. 2026-09-12 00:43 UTCEG score recompute
  17. 2026-09-11 14:53 UTCEPSS rescore
  18. 2026-09-10 22:57 UTCEG score recompute
  19. 2026-09-10 09:35 UTCEPSS rescore
  20. 2026-09-09 00:27 UTCEG score recompute
  21. 2026-09-08 22:01 UTCEPSS rescore
  22. 2026-09-07 16:01 UTCEPSS rescore
  23. 2026-09-07 15:02 UTCEG score recompute
  24. 2026-09-06 13:47 UTCEPSS rescore
  25. 2026-09-06 13:03 UTCEG score recompute
Show 15 more
  1. 2026-09-05 11:18 UTCEG score recompute
  2. 2026-09-04 09:31 UTCEG score recompute
  3. 2026-09-04 05:07 UTCEPSS rescore
  4. 2026-09-03 07:45 UTCEG score recompute
  5. 2026-09-02 14:12 UTCEPSS rescore
  6. 2026-09-02 05:56 UTCEG score recompute
  7. 2026-09-01 13:54 UTCEPSS rescore
  8. 2026-09-01 04:40 UTCEPSS rescore
  9. 2026-08-31 02:20 UTCEG score recompute
  10. 2026-08-30 19:17 UTCEPSS rescore
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-28 22:48 UTCEG score recompute
  13. 2026-08-28 22:09 UTCEG score recompute
  14. 2026-08-28 20:25 UTCEG score recompute
  15. 2026-08-28 17:11 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-55834?
CVE-2026-55834 is a medium vulnerability published on August 28, 2026. 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 redirecturi query parameter and frontend/src/routes/authorize/+page.svelte uses the raw callbackURL in redirectWithError when…
When was CVE-2026-55834 disclosed?
CVE-2026-55834 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55834 actively exploited?
CVE-2026-55834 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.7% of all scored CVEs.
What is the CVSS score of CVE-2026-55834?
CVE-2026-55834 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-55834?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55834, 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-55834

Explore →

Is Your Infrastructure Affected by CVE-2026-55834?

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