Skip to main content
VulnerabilityPublished Updated

CVE-2024-51363: Hodoku · Deserialization of Untrusted Data

Affects HodokuSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubgelcon/Hodokupkg:github/gelcon/HodokuOther threatsAffected
  • >=2.3.0 <=2.3.2
Fixed in–

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

AI-suggested

  1. Immediately upgrade Hodoku to a version that addresses this vulnerability once a patch is released. Monitor official Hodoku channels for updates.
  2. Until patches are available, restrict network access to Hodoku instances by implementing firewall rules or network segmentation to limit exposure to untrusted networks.
  3. Employ application-layer filtering or web application firewalls (WAFs) to detect and block suspicious serialized data patterns.
  4. Conduct code reviews and implement input validation to prevent deserialization of untrusted data in custom deployments or integrations.
  5. Monitor logs and network traffic for unusual deserialization activity or unexpected process executions.
  6. Use runtime application self-protection (RASP) tools if available to detect and prevent exploitation attempts.
  7. Educate development and security teams about the risks of insecure deserialization and best practices to avoid such vulnerabilities in future software.

Description

Insecure deserialization in Hodoku v2.3.0 to v2.3.2 allows attackers to execute arbitrary code.

References

Community reviews

Loading reviews…