# CVE-2025-48738: Denial of service in TheHive

> Unauthenticated attackers can flood email systems via unlimited password resets, causing storage exhaustion and server blacklisting in TheHive.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2025
- **Updated:** 23 May 2025
- **Also known as:** GHSA-8hx5-5mh4-xhjv

## What is CVE-2025-48738?

CVE-2025-48738 is a medium-severity denial of service vulnerability in StrangeBee TheHive, published on 23 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An e-mail flooding vulnerability in StrangeBee TheHive 5.2.0 before 5.2.16, 5.3.0 before 5.3.11, 5.4.0 before 5.4.10, and 5.5.0 before 5.5.1 allows unauthenticated remote attackers to use the password reset feature without limits. This can lead to several consequences, including mailbox storage exhaustion for targeted users, reputation damage to the SMTP server, potentially causing it to be blacklisted, and overload of the SMTP server's outbound mail queue.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

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

## Is CVE-2025-48738 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48738 is a medium-severity denial of service vulnerability in StrangeBee TheHive, published on 23 May 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-48738 in the wild and no public exploit code.

Affected product: StrangeBee TheHive. 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-48738/ (Markdown: https://insights.sbomify.com/CVE-2025-48738/index.md)
```

## Sources

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

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