Skip to main content
VulnerabilityPublished Updated

CVE-2025-26866: Apache HugeGraph-Server · Deserialization of Untrusted Data

Affects Apache HugeGraph-ServerSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High · fixed in 1.7.0 : patch Apache HugeGraph-Server soon.

Data as of 26 Oct 2026, 14:05 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Dec 2025

  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
Mavenorg.apache.hugegraph/hugegraph-serverpkg:maven/org.apache.hugegraph/hugegraph-serverOther threatsAffected
  • =1.0.0
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. Immediate upgrade to Apache HugeGraph-Server version 1.7.0 or later, which includes the fix for this vulnerability.
  2. Implement network-level controls to restrict access to the cluster communication ports, allowing only trusted IP addresses and nodes to connect.
  3. Use firewall rules and segmentation to isolate HugeGraph clusters from untrusted networks.
  4. Monitor cluster membership and logs for any unauthorized or suspicious Raft node join attempts.
  5. Employ intrusion detection systems (IDS) to detect anomalous serialized payloads or unusual cluster behavior.
  6. Regularly audit and review cluster configurations to ensure IP-based authentication and class whitelisting are enforced.
  7. Educate administrators about the risks of insecure deserialization and the importance of applying vendor patches promptly.
  8. Consider deploying additional runtime application self-protection (RASP) or endpoint detection and response (EDR) solutions to detect exploitation attempts in real time.

Description

A remote code execution vulnerability exists where a malicious Raft node can exploit insecure Hessian deserialization within the PD store. The fix enforces IP-based authentication to restrict cluster membership and implements a strict class whitelist to harden the Hessian serialization process against object injection attacks. Users are recommended to upgrade to version 1.7.0, which fixes the issue.

References

Community reviews

Loading reviews…