CVE-2016-3180: Tor Browser Launcher (aka torbrowser-launcher) before 0.2.4, during the initial run, allows man-in-the-middle

This month

HIGH 8.1REMOTEDOWNGRADE

CVE-2016-3180 is a high-severity flaw (CVSS 8.1) affecting tor browser launcher. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Tor Browser Launcher (aka torbrowser-launcher) before 0.2.4, during the initial run, allows man-in-the-middle attackers to bypass the PGP signature verification and execute arbitrary code via a Trojan horse tar file and a signature file with the valid tarball and signature.

Why this priority

High severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	1.9% (top 20%)
CISA exploited list	No
Weakness	CWE-254
Published	2017-02-07
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: tor browser launcher project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-02-07 17:59 UTCPublished CVE record published
2026-06-17 00:45 UTCUpdated Record last modified

tor browser launcher project tor browser launcher DOWNGRADE

Affected: 0.2.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.2.3

1. Check installed version

apt-cache policy tor-browser-launcher || rpm -q tor-browser-launcher || tor-browser-launcher --version

2. No fixed release: DOWNGRADE to a release before 0.2.3 (Debian / Ubuntu)

apt-cache madison tor-browser-launcher sudo apt install tor-browser-launcher=<VERSION_BEFORE_0.2.3> sudo apt-mark hold tor-browser-launcher

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list tor-browser-launcher sudo dnf downgrade tor-browser-launcher-<VERSION_BEFORE_0.2.3> sudo dnf versionlock add tor-browser-launcher

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-3180?

tor browser launcher: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2016-3180 being exploited?

CVE-2016-3180 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-3180 affect?

CVE-2016-3180 affects tor browser launcher. Severity is high (CVSS 8.1). Tor Browser Launcher (aka torbrowser-launcher) before 0.2.4, during the initial run, allows man-in-the-middle attackers to bypass the PGP signature verification and execute arbitrary code via a Trojan horse tar file and a signature file wit

How urgent is CVE-2016-3180?

Priority 53/100. High severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs