# CVE-2025-42599: Qualitia Active! Mail Stack-Based Buffer Overflow

> Remote unauthenticated attackers can trigger a stack-based buffer overflow in Active! mail 6, leading to arbitrary code execution or denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 28 Apr 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Apr 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-wvvm-3j2m-8rj3

## What is CVE-2025-42599?

CVE-2025-42599 is a critical memory corruption vulnerability in QUALITIA CO., LTD. Active! mail 6, published on 18 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Active! mail 6 BuildInfo: 6.60.05008561 and earlier contains a stack-based buffer overflow vulnerability. Receiving a specially crafted request created and sent by a remote unauthenticated attacker may lead to arbitrary code execution and/or a denial-of-service (DoS) condition.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Qualitia Active\! Mail.

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

No fix has been published for CVE-2025-42599 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 19 May 2025.

## Is CVE-2025-42599 being exploited?

Yes. Attackers have exploited CVE-2025-42599 in the wild since at least 28 Apr 2025.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42599 is a critical memory corruption vulnerability in QUALITIA CO., LTD. Active! mail 6, published on 18 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-42599 in the wild since at least 28 Apr 2025.

Affected product: QUALITIA CO., LTD. Active! mail 6. 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-42599/ (Markdown: https://insights.sbomify.com/CVE-2025-42599/index.md)
```

## Sources

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

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