Vulnerability in tor (DEBIAN-CVE-2026-44599)

Summary

Vulnerability in tor (DEBIAN-CVE-2026-44599). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.4.9.8-0+deb12u1 or later.

Original description

The description as published by the source.

Tor before 0.4.9.7 can attempt or accept BEGIN_DIR via conflux legs, aka TROVE-2026-008.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A weakness called DEBIAN-CVE-2026-44599 was discovered in tor.
Severity is Info. Low severity or not yet rated.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "tor DEBIAN-CVE-2026-44599".

DEBIAN-CVE-2026-44599 (tor). Severity: Info.
Response plan:

Check the vendor advisory for affected versions and the patched release.
If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.

❓ What is the problem

A weakness (DEBIAN-CVE-2026-44599) in tor. A serious software flaw has been identified.

📍 Affected scope

Target versions of tor (see vendor advisory). If running in production, identify exposure immediately.

🔥 Severity

Severity: Info. Low severity or not yet rated.

🔧 How to fix

Update to the patched release as listed in the vendor advisory.

🛡️ Workaround

If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.

🔍 Detection

Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'tor' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で tor を grep し、稼働しているサービス・バージョンを把握する。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Debian:11 tor

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Debian:12 tor

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.9.8-0+deb12u1"}]}]

Debian:13 tor

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.9.8-0+deb13u1"}]}]

Debian:14 tor

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.9.8-1"}]}]

References

advisory security-tracker.debian.org