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

> Unauthenticated attackers can cause denial of service in Zimbra Collaboration by sending crafted requests with excessive path segments to the Admin Console.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2025
- **Updated:** 22 Jul 2025
- **Also known as:** GHSA-92rg-2wcj-32jv

## What is CVE-2025-53645?

CVE-2025-53645 is a high-severity denial of service vulnerability in n/a, published on 9 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Zimbra Collaboration (ZCS) before 9.0.0 Patch 46, 10.0.x before 10.0.15, and 10.1.x before 10.1.9 is vulnerable to a denial of service condition due to improper handling of excessive, comma-separated path segments in the Admin Console. An unauthenticated remote attacker can send specially crafted GET requests that trigger redundant processing and inflated responses. This leads to uncontrolled resource consumption, resulting in denial of service.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2025-53645 being exploited?

There is no known exploitation of CVE-2025-53645 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53645 is a high-severity denial of service vulnerability in n/a, published on 9 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-53645 in the wild and no public exploit code.

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-53645/ (Markdown: https://insights.sbomify.com/CVE-2025-53645/index.md)
```

## Sources

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

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