# CVE-2025-61084: Other in n/a

> Attackers can spoof email senders by exploiting Unicode handling in SPF/DKIM validation, bypassing anti-spoofing protections in MDaemon Mail Server.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N`)
- **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:** 5 Nov 2025
- **Updated:** 13 Nov 2025
- **Also known as:** GHSA-x43x-2mp4-28j4

## What is CVE-2025-61084?

CVE-2025-61084 is a high-severity vulnerability in n/a, published on 5 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MDaemon Mail Server 23.5.2 validates SPF, DKIM, and DMARC using the email enclosed in angle brackets (<>) in the From: header of SMTP DATA. An attacker can craft a From: header with multiple invisible Unicode thin spaces to display a spoofed sender while passing validation, allowing email spoofing even when anti-spoofing protections are in place. NOTE: this is disputed by the Supplier because UI spoofing occurs in a client, not in a server such as MDaemon's product or any other server implementation. Also, if a client without its own spoofing protection must be used, the Header Screening feature in MDaemon's product can be employed to mitigate the client-side vulnerability.

Weakness: CWE-20 (Improper Input Validation), CWE-116 (Improper Encoding or Escaping of Output)

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


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

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

## Is CVE-2025-61084 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-61084 is a high-severity vulnerability in n/a, published on 5 Nov 2025. 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-61084 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-61084/ (Markdown: https://insights.sbomify.com/CVE-2025-61084/index.md)
```

## Sources

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

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