CVE-2025-71031 json
Water-Melon Melon commit 9df9292 and below is vulnerable to Denial of Service.
published 9mo ago modified 4mo ago also EUVD-2025-206781
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2025-71031 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 9mo ago
Exploit prediction
0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- suphawith-phusanbai.gitbook.io https://suphawith-phusanbai.gitbook.io/book-of-suphawith/my-exploits/denial-of-service-in-melon-c-library referenced PoC, tagged "exploit" by a source, unverified
- suphawith-phusanbai.gitbook.io https://suphawith-phusanbai.gitbook.io/book-of-suphawith/my-exploits/cve-2025-71031-denial-of-service-in-melon-c-library referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
suphawith-phusanbai.gitbook.io
/book-of-suphawith/my-exploits/denial-of-service-in-melon-c-library
exploit, third-party-advisory
-
suphawith-phusanbai.gitbook.io
/book-of-suphawith/my-exploits/cve-2025-71031-denial-of-service-in-melon-c-library
exploit, third-party-advisory
Sources
- CVE List CVE-2025-71031
- NVD CVE-2025-71031
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.