# CVE-2026-44603: Memory corruption in Tor

> An out-of-bounds read in Tor allows attackers to cause denial of service or disclose information via a malformed BEGIN cell.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 May 2026
- **Updated:** 7 May 2026
- **Also known as:** DEBIAN-CVE-2026-44603, GHSA-m47q-4224-6rvc, UBUNTU-CVE-2026-44603

## What is CVE-2026-44603?

CVE-2026-44603 is a low-severity memory corruption vulnerability in torproject Tor, published on 7 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tor before 0.4.9.7 has an out-of-bounds read by one byte via a malformed BEGIN cell, aka TROVE-2026-007.

Weakness: CWE-193 (Off-by-one Error)

## Which versions are affected by CVE-2026-44603?

It affects 1 product.


Products: Torproject Tor.

## How do I fix CVE-2026-44603?

Upgrade to a fixed version.

## Is CVE-2026-44603 being exploited?

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

## Other vulnerabilities in torproject Tor

- [CVE-2026-77638](https://insights.sbomify.com/CVE-2026-77638/): Race condition in Tor (high 8.9)
- [CVE-2026-77642](https://insights.sbomify.com/CVE-2026-77642/): Memory corruption in Tor (high 7.5)
- [CVE-2022-33903](https://insights.sbomify.com/CVE-2022-33903/): Denial of service in n/a (high 7.5)
- [CVE-2021-38385](https://insights.sbomify.com/CVE-2021-38385/): Denial of service in n/a (high 7.5)
- [CVE-2021-34548](https://insights.sbomify.com/CVE-2021-34548/): Security feature bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44603 and fix it if it is affected.

What it is: CVE-2026-44603 is a low-severity memory corruption vulnerability in torproject Tor, published on 7 May 2026. 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-2026-44603 in the wild and no public exploit code.

Affected product: torproject Tor. 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-2026-44603/ (Markdown: https://insights.sbomify.com/CVE-2026-44603/index.md)
```

## Sources

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

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