Skip to main content
VulnerabilityPublished Updated

CVE-2025-71031: Water-Melon Melon · Uncontrolled Resource Consumption

Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% 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:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Feb 2026

  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

AI-suggested

Since no official patches or updates are currently available for the Water-Melon Melon HTTP component, European organizations should implement the following specific mitigations: 1) Deploy network-level protections such as web application firewalls (WAFs) or intrusion prevention systems (IPS) configured to detect and block HTTP requests with abnormally large headers. 2) Implement rate limiting and connection throttling to restrict the number of requests and header sizes accepted from individual IP addresses. 3) Use reverse proxies or load balancers capable of enforcing maximum header size limits to prevent oversized headers from reaching the vulnerable component. 4) Monitor system memory usage and HTTP service logs for signs of abnormal resource consumption or crashes indicative of exploitation attempts. 5) Engage with Water-Melon Melon vendors or maintainers to track patch releases and apply updates promptly once available. 6) Conduct internal audits to identify all instances of Water-Melon Melon deployments and prioritize mitigation efforts accordingly. 7) Consider temporary isolation or replacement of vulnerable components in critical environments until a patch is released. These targeted actions go beyond generic advice by focusing on controlling header sizes and resource consumption at multiple layers.

Description

Water-Melon Melon commit 9df9292 and below is vulnerable to Denial of Service. The HTTP component doesn't have any maximum length. As a result, an excessive request header could cause a denial of service by consuming RAM memory.

References

Community reviews

Loading reviews…