# CVE-2025-65519: Denial of service in n/a

> Authenticated attackers can cause denial of service in ezbookkeeping by uploading deeply nested JSON or XML files, exhausting CPU resources.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2026
- **Updated:** 18 Feb 2026
- **Also known as:** GHSA-f2fg-5m3g-hqwv

## What is CVE-2025-65519?

CVE-2025-65519 is a medium-severity denial of service vulnerability in n/a, published on 18 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

mayswind ezbookkeeping versions 1.2.0 and earlier contain a critical vulnerability in JSON and XML file import processing. The application fails to validate nesting depth during parsing operations, allowing authenticated attackers to trigger denial of service conditions by uploading deeply nested malicious files. This results in CPU exhaustion, service degradation, or complete service unavailability.

Weakness: CWE-674 (Uncontrolled Recursion)

## Which versions are affected by CVE-2025-65519?

It affects 1 product.


Products: Mayswind Ezbookkeeping.

## How do I fix CVE-2025-65519?

No fix has been published for CVE-2025-65519 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-65519 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65519 exists.

## Other vulnerabilities in n/a

- [CVE-2024-57604](https://insights.sbomify.com/CVE-2024-57604/): MaysWind ezBookkeeping has Improper Privilege Management (critical 9.8)
- [CVE-2024-57603](https://insights.sbomify.com/CVE-2024-57603/): Missing rate limit in MaysWind ezBookkeeping (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-65519 and fix it if it is affected.

What it is: CVE-2025-65519 is a medium-severity denial of service vulnerability in n/a, published on 18 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65519 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-65519/ (Markdown: https://insights.sbomify.com/CVE-2025-65519/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-65519
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-65519
- OSV: https://osv.dev/vulnerability/CVE-2025-65519

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-65519/
Summaries are generated and may contain mistakes; the official description above is the record.