# CVE-2025-2545: Deprecated 3DES cryptographic algorithm used by Request Tracker in emails encrypted with S/MIME

> Request Tracker uses obsolete 3DES for S/MIME emails, allowing attackers to potentially compromise message confidentiality via birthday attacks.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 May 2025
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2025-2545, GHSA-33cx-2vvq-mf52, UBUNTU-CVE-2025-2545

## What is CVE-2025-2545?

CVE-2025-2545 is a low-severity vulnerability in Best Practical Solutions Request Tracker, published on 5 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Vulnerability in Best Practical Solutions, LLC's Request Tracker prior to v5.0.8, where the Triple DES (3DES) cryptographic algorithm is used to protect emails sent with S/MIME encryption. Triple DES is considered obsolete and insecure due to its susceptibility to birthday attacks, which could compromise the confidentiality of encrypted messages.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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


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

Upgrade to a fixed version.

## Is CVE-2025-2545 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2545 is a low-severity vulnerability in Best Practical Solutions Request Tracker, published on 5 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-2545 in the wild and no public exploit code.

Affected product: Best Practical Solutions Request Tracker. 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-2545/ (Markdown: https://insights.sbomify.com/CVE-2025-2545/index.md)
```

## Sources

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

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