CVE-2025-70059
CVE-2025-70059 is a high-severity vulnerability in Ymfe Yapi with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-400.
Key facts
- Severity: High (CVSS 3.x base score 7.5)
- EPSS exploit prediction: 0% (26th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2025-208415
- Weakness: CWE-400
- Affected product: Ymfe Yapi
- Published:
- Last modified:
Description
An issue pertaining to CWE-400: Uncontrolled Resource Consumption was discovered in YMFE yapi v1.12.0 and allows attackers to cause a denial of service.
Frequently asked questions
- What is CVE-2025-70059?
- An issue pertaining to CWE-400: Uncontrolled Resource Consumption was discovered in YMFE yapi v1.12.0 and allows attackers to cause a denial of service.
- How severe is CVE-2025-70059?
- CVE-2025-70059 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
- Is CVE-2025-70059 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (26th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2025-70059?
- CVE-2025-70059 affects Ymfe Yapi. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2025-70059?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- Does CVE-2025-70059 have an EU (EUVD) identifier?
- Yes. CVE-2025-70059 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-208415.
- When was CVE-2025-70059 published?
- CVE-2025-70059 was published on 2026-03-09 and last updated on 2026-06-17.
References
- https://gist.github.com/zcxlighthouse/e6090e95643c1b1cd4ecc2088c4e77ef
- https://github.com/YMFE
- https://github.com/YMFE/yapi
Affected products (1)
- cpe:2.3:a:ymfe:yapi:1.12.0:*:*:*:*:*:*:*
More vulnerabilities in Ymfe Yapi
- CVE-2025-70058 — High (CVSS 7.4): An issue pertaining to CWE-295: Improper Certificate Validation was discovered in YMFE yapi v1.12.0. The application…
- CVE-2025-70060 — Medium (CVSS 5.4): An issue pertaining to CWE-79: Improper Neutralization of Input During Web Page Generation was discovered in YMFE yapi…
- CVE-2021-36686 — Medium (CVSS 5.4): Cross Site Scripting (XSS) vulnerability in yapi 1.9.1 allows attackers to execute arbitrary code via the…
- CVE-2018-17574 — Medium (CVSS 5.4): An issue was discovered in YMFE YApi 1.3.23. There is stored XSS in the name field of a project.
- CVE-2021-27884 — Medium (CVSS 5.1): Weak JSON Web Token (JWT) signing secret generation in YMFE YApi through 1.9.2 allows recreation of other users' JWT…
All CVEs affecting Ymfe Yapi →
Other CWE-400 (Uncontrolled Resource Consumption) vulnerabilities
- CVE-2026-46775 — Critical (CVSS 9.9): Vulnerability in Oracle REST Data Services (component: Core). Supported versions that are affected are 24.2.0-26.1.0.…
- CVE-2025-61303 — Critical (CVSS 9.8): Hatching Triage Sandbox Windows 10 build 2004 (2025-08-14) and Windows 10 LTSC 2021(2025-08-14) contains a…
- CVE-2025-43193 — Critical (CVSS 9.8): The issue was addressed with improved memory handling. This issue is fixed in macOS Sequoia 15.6, macOS Sonoma 14.7.7,…
- CVE-2025-24269 — Critical (CVSS 9.8): The issue was addressed with improved memory handling. This issue is fixed in macOS Sequoia 15.4. An app may be able to…
- CVE-2025-24264 — Critical (CVSS 9.8): The issue was addressed with improved memory handling. This issue is fixed in Safari 18.4, iOS 18.4 and iPadOS 18.4,…
- CVE-2025-24260 — Critical (CVSS 9.8): The issue was addressed with improved memory handling. This issue is fixed in macOS Sequoia 15.4, macOS Sonoma 14.7.5,…
Browse all CWE-400 (Uncontrolled Resource Consumption) vulnerabilities →