New Release: Tor Browser 13.0.10
Tor Browser 13.0.10 is now available from the Tor Browser download page and also from our distribution directory.
This version includes important security updates to Firefox.
This release updates Firefox to 115.8.0esr, OpenSSL to 3.0.13, zlib to 1.3.1, and Snowflake to 2.9.0. It also includes various bug fixes (see changelog for details).
Send us your feedback
If you find a bug or have a suggestion for how we could improve this release, please let us know.
Full changelog
The full changelog since Tor Browser 13.0.9 is:
- All Platforms
- Updated OpenSSL to 3.0.13
- Updated zlib to 1.3.1
- Updated Snowflake to 2.9.0
- Bug tor-browser#42374: spoof english leaks via numberingSystem: numbers (non-latn) or decimal separator (latn)
- Bug tor-browser#42411: Rebase Tor Browser stable onto 115.8.0esr
- Bug tor-browser-build#41079: Bump version of Snowflake to v2.9.0
- Windows + macOS + Linux
- Updated Firefox to 115.8.0esr
- Bug tor-browser#42338: Changing circuit programmatically in Tor Browser not working anymore!
- Android
- Updated GeckoView to 115.8.0esr
- Bug tor-browser#42402: Remove Android YEC strings
- Bug tor-browser#42416: Backport Android security fixes from Firefox 123
- Linux
- Bug tor-browser#42293: Updater is disabled when tor-browser is run by torbrowser-launcher flatpak
- Build System
- All Platforms
- Updated Go to 1.20.14 and 1.21.7
- Bug tor-browser-build#41067: Use Capture::Tiny instead of IO::CaptureOutput
- Bug rbm#40067: Use --no-verbose wget option when not running in a terminal
- Bug rbm#40068: Switch from IO::CaptureOutput to Capture::Tiny
- Bug rbm#40069: Make stdout and stderr utf8
- Bug rbm#40072: Move capture_exec to a separate module
- All Platforms
Comments
We encourage respectful, on-topic comments. Comments that violate our Code of Conduct will be deleted. Off-topic comments may be deleted at the discretion of the moderators. Please do not comment as a way to receive support or to report bugs on a post unrelated to a release. If you are looking for support, please see our FAQ, user support forum or ways to get in touch with us.