# CVE-2025-65318: Security feature bypass in n/a

> Attackers can bypass Windows and third-party file protection mechanisms by saving attachments without Mark-of-the-Web tags in Canary Mail.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-w2r9-w6fr-cq88

## What is CVE-2025-65318?

CVE-2025-65318 is a critical vulnerability in n/a, published on 16 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

When using the attachment interaction functionality, Canary Mail 5.1.40 and below saves documents to a file system without a Mark-of-the-Web tag, which allows attackers to bypass the built-in file protection mechanisms of both Windows OS and third-party software.

Weakness: CWE-693 (Protection Mechanism Failure)

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

It affects 1 product.


Products: Canarymail Canary Mail.

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

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

## Is CVE-2025-65318 being exploited?

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

Public exploit code:

- Insecure attachment handling when using Canary Mail or Blue mail (github_poc): https://github.com/bbaboha/CVE-2025-65318-and-CVE-2025-65319

## Other vulnerabilities in n/a

- [CVE-2021-26911](https://insights.sbomify.com/CVE-2021-26911/): Security feature bypass in n/a (high 7.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65318 is a critical vulnerability in n/a, published on 16 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65318 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-65318/ (Markdown: https://insights.sbomify.com/CVE-2025-65318/index.md)
```

## Sources

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

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