# CVE-2023-41259: Information disclosure in n/a

> Attackers can disclose information by sending fake or spoofed email headers to Request Tracker via email or REST API.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Nov 2023
- **Updated:** 4 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-41259, GHSA-22g7-wp2f-rmqf, UBUNTU-CVE-2023-41259

## What is CVE-2023-41259?

CVE-2023-41259 is a high-severity vulnerability in n/a, published on 3 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Best Practical Request Tracker (RT) before 4.4.7 and 5.x before 5.0.5 allows Information Disclosure via fake or spoofed RT email headers in an email message or a mail-gateway REST API call.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-41259?

It affects 1 product.


Products: Bestpractical Request Tracker.

## How do I fix CVE-2023-41259?

Upgrade to a fixed version.

## Is CVE-2023-41259 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-44231](https://insights.sbomify.com/CVE-2026-44231/): RT: Privilege escalation and information disclosure via REST 2.0 user collection endpoint (critical 9.1)
- [CVE-2017-5943](https://insights.sbomify.com/CVE-2017-5943/): Information disclosure in n/a (high 8.8)
- [CVE-2017-5944](https://insights.sbomify.com/CVE-2017-5944/): Code injection in n/a (high 8.8)
- [CVE-2023-41260](https://insights.sbomify.com/CVE-2023-41260/): Information disclosure in n/a (high 7.5)
- [CVE-2023-45024](https://insights.sbomify.com/CVE-2023-45024/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-41259 and fix it if it is affected.

What it is: CVE-2023-41259 is a high-severity vulnerability in n/a, published on 3 Nov 2023. 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-2023-41259 in the wild and no public exploit code.

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-2023-41259/ (Markdown: https://insights.sbomify.com/CVE-2023-41259/index.md)
```

## Sources

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

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