Skip to main content
VulnerabilityPublished

CVE-2026-55617: Hydro · Insufficient Session Expiration

Affects HydroSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 5.0.2 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.0.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Hydro and hydro-dev/Hydro to 5.0.2.

Affected software

ProductAffectedFixed in
hydro-devHydroAffected
  • >=4.10.4 <5.0.2
Fixed in
  • 5.0.2
GitHubhydro-dev/Hydropkg:github/hydro-dev/HydroOther threatsAffected
  • >=4.10.4 <5.0.2
Fixed in
  • 5.0.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Hydro to version 5.0.2 or later, where the session recreation logic properly invalidates old session tokens upon renewal. Until upgrading, be aware that stale session cookies may remain valid after logout or session renewal, posing a risk of session replay attacks.

Description

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.

References

Community reviews

Loading reviews…