Hydro is a next-generation high-performance online judge platform. From 4.10.4 until 5.0.2, the session recreation logic in packages/hydrooj/src/service/layers/base.ts creates a replacement session token without deleting the previous token from the server-side session token store, so an old sid cookie can remain valid after logout or another renewal flow. An attacker who possesses a victim's previously valid stale cookie can replay it over HTTP or HTTPS without knowing the victim's username or password and without victim interaction at exploitation time. Successful replay can take over the victim's account, disclose private data, and permit unauthorized modification or deletion of data available to that account. This issue is fixed in version 5.0.2.
CVE-2026-55617
This medium-severity CVE scores 6.9 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
- 6.9
- EG Score
- 6.9(low)
- EG Risk
- 31(Track)EG Risk 31/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 computedSeverity69% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
June 18, 2026
Last Modified
September 15, 2026
Advisory Details (4)
Auto-updated Sep 15, 2026commit 8d76be8f0b83 (hydro-dev/Hydro)
Fix landed in hydro-dev/Hydro commit 8d76be8f0b83 — awaiting tagged release
https://github.com/hydro-dev/Hydro/commit/8d76be8f0b83d911bf7671962b0467e9d4b5719acommit 8450390fcce5 (hydro-dev/Hydro)
Fix landed in hydro-dev/Hydro commit 8450390fcce5 — awaiting tagged release
https://github.com/hydro-dev/Hydro/commit/8450390fcce5f7dc3f11c43a14f1d76dbb949a0dcore: delete old session after recreate
Fix merged in hydro-dev/Hydro PR #1173 on 2026-06-06 — awaiting tagged release
https://github.com/hydro-dev/Hydro/pull/1173Insufficient session expiration when recreating sessions in Hydro · Advisory · hydro-dev/Hydro · GitHub
https://github.com/hydro-dev/Hydro/security/advisories/GHSA-94jp-7776-qj6qVendor Advisories for CVE-2026-55617(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)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| hydrooj | — | 5.0.2 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× 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-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 19:41 UTCEG score recompute
- 2026-09-15 18:25 UTCEG score recompute
- 2026-09-15 15:35 UTCEG score recompute
- 2026-09-15 14:53 UTCEG score recompute▲ 6.90
- 2026-09-15 14:52 UTCMITRE cvelistV5CVSS v3 → 6.9 · CVSS v4 → 6.9
- 2026-08-02 03:50 UTCEG score recompute
- 2026-07-26 18:48 UTCEG score recompute
- 2026-07-23 03:20 UTCEG score recompute
- 2026-06-18 13:45 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-55617?
When was CVE-2026-55617 disclosed?
Is CVE-2026-55617 actively exploited?
What is the CVSS score of CVE-2026-55617?
How do I remediate CVE-2026-55617?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55617
Is Your Infrastructure Affected by CVE-2026-55617?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.