New Release: Tor Browser 8.5.2

Tor Browser 8.5.2 is now available from the Tor Browser Download page and also from our distribution directory.

This release fixes a critical security update in Firefox. In addition, we update NoScript to 10.6.3, fixing a few issues.

Users of the safer and safest security levels were not affected by this security issue.

Note: As part of our team is currently traveling to an event, we are unable to access our Android signing token, therefore the Android release is not yet available. We expect to be able to publish the Android release this weekend. In the meantime, Android users should use the safer or safest security levels. The security level on Android can be changed by going in the menu on the right of the URL bar and selecting Security Settings.

The full changelog since Tor Browser 8.5.1 is:

  • All platforms
    • Pick up fix for Mozilla's bug 1544386
    • Update NoScript to 10.6.3

June 20, 2019


Does not launch on macOS Catalina 10.15b2. Followed Security and Privacy steps to allow the app to launch, still no joy.

  1. “updater” can’t be opened because it is from an unidentified developer.</p>
  2. <p>Your security preferences allow installation of only apps from the App Store and identified developers.</p>


June 20, 2019


To get Tor to launch on macOS Catalina 10.15b2 run the following command to restore the "anywhere" Security and Privacy option.

sudo spctl --master-disable

The option will not persist.

Tried the 'spctl' fix, begins execution then fails with a segmentation fault: 11
Exception Codes: EXC_I386_GPFLT

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [1748]


June 20, 2019


Hello, there is a problem, TOR on Windows is not compatible with the use of visual disabilities when using the keyboard to surf the Internet I mean shortcuts to navigate through the links and headers and lists ... Please find a solution to this problem quickly The program used with it is NVDA

have the default bridges been changed to working ones with this release?

also download page still has 8.5.1 for android

finally, about >> torbrowser from settings does not report torbrowser version but firefox instead

guys can someone please address this

I guess that's all for mobile?

Yes, we updated our default bridges on Android. Additionally, we plan to release the new Android stable versions as soon as we can, probably on the weekend (see the above blog post you are commenting to). Finally, yes, we don't have a way to report the Tor Browser version yet. We should fix that, though. I've opened:

I am having a ton of problems loading any pages. I just received the latest update to TOR the other evening, so it should be up to day. When I launch TOR, it works great for about 5 minutes and then it starts timing out on any page I attempt to go to. Any tips?

Assigned defect # 30441""

The issue still continues with operating bridges not being handed out.
Should the circuit Bridge obfs4 IP change occasionally ?

example Tor circuit
this browser
bridge: obfs4:XX.XX.XX.XX
Unites states
Unites states

Stop writing bridge IP addresses. You are putting yourself and other Tor users at risk. The only way you should reference a bridge is by its hashed_fingerprint. Not its fingerprint in the bridge line. The hashed fingerprint seen on the bridge's Metrics page.

My TBB ignores "Never check for updates" option I selected. Why?

about:config > extensions.torbutton.versioncheck_enabled ; false