Tor Project blog

New Release: Tails 7.10.1

2026-08-05T00:00:00Z

This release is an emergency release to fix critical security vulnerabilities in the Linux kernel and the expat XML library.

Changes and updates

Update the Linux kernel to 6.12.100, which fixes CVE-2026-64560, a vulnerability that could allow Tor Browser in Tails to gain administrator privileges.

For example, if a malicious website that you visit is able to exploit CVE-2026-64560, they might take full control of your Tails and deanonymize you.

This attack is very unlikely but could be performed by a strong attacker, such as a government or a hacking firm. We are not aware of this attack being used in practice until now.

Update the expat XML library to 2.8.2, which fixes DSA-6404-1, a set of vulnerabilities that could allow different applications in Tails to gain administrator privileges.

For example, if an attacker tricks you into opening a malicious file in an application that uses expat , such as LibreOffice , Audacity , or Git , they might then use one of these vulnerabilities to take full control of your Tails and deanonymize you.

This attack is very unlikely but could be performed by a strong attacker, such as a government or a hacking firm. We are not aware of this attack being used in practice until now.

Compress automatic upgrades with zstd for a faster startup, as we already did for the USB image in Tails 7.0.
Make USB images and automatic upgrades 70 MB smaller by removing unused firmware.

For more details, read our changelog.

Get Tails 7.10.1

To upgrade your Tails USB stick and keep your Persistent Storage

Automatic upgrades are available from Tails 7.0 or later to 7.10.1.
If you cannot do an automatic upgrade or if Tails fails to start after an automatic upgrade, please try to do a manual upgrade.

To install Tails 7.10.1 on a new USB stick

Follow our installation instructions.

The Persistent Storage on the USB stick will be lost if you install instead of upgrading.

To download only

If you don't need installation or upgrade instructions, you can download Tails 7.10.1 directly:

Support and feedback

For support and feedback, visit the Support section on the Tails website.

Arti 2.5.1 released

2026-08-04T00:00:00Z

Arti is our ongoing project to create a next-generation Tor implementation in Rust. We're happy to announce the latest release, Arti 2.5.1.

This release consists mostly of internal improvements and bug fixes, as well as our ongoing development towards using Arti as a relay and as a directory authority. For onion service hosts, onion services can now be configured to connect to unix socket addresses. Arti also now has experimental support for congestion control and Counter Galois Onion cryptography on onion service circuits, which we hope to make stable soon.

For full details on what we've done, including API changes, and for information about many more minor and less-visible changes, please see the CHANGELOG.

For more information on using Arti, see our top-level README, and the documentation for the arti binary.

Thanks to everybody who's contributed to this release, including Andrew Kloet, Jérôme Charaoui, hjrgrn, pryty26, ramdoys, and syphyr.

Also, our deep thanks to our sponsors for funding the development of Arti!

Snowflake Volunteer, an Android app to help people bypass censorship

2026-08-03T00:00:00Z

Bypassing censorship comes down to two challenges: disguising internet traffic from censors while making an open network easy to reach. Snowflake is particularly effective at tackling both of these challenges. It disguises a user's traffic to look like a video call and routes it through volunteer-run proxies using short-lived connections, making the traffic harder to detect and block.

That's why it's important to have a large and healthy pool of volunteers always available. To achieve that, Snowflake has to be easy to use and deploy, ideally on the devices and with the services they already use.

Up until this point, volunteers could use browser extensions, a website embed, a command-line tool for desktop, and on Android they can use Orbot's Kindness Mode. During the first half of 2026, the Snowflake broker saw an average of approximately 146,000 unique volunteer proxy IP addresses checking in each day¹. Roughly a third of those were associated with Orbot's Kindness Mode. Kindness Mode also makes volunteering tangible by showing users how many connections their proxy has supported.

Seeing how much capacity that feature contributed, Bloco, an Android app studio in Portugal became curious if a standalone app, focused just on volunteering proxies, could reach even more helpers. They reached out to Tor's anti-censorship team which had plans to work on a similar project, but had not yet had the capacity to develop it, yet. So, Bloco took on the task of building such an app.

The motivation grew out of the team's work with OONI (Open Observatory of Network Interference), where they saw how NGOs and activists rely on anti-censorship tools to stay safe and connected. After discovering how easy it was to volunteer a Snowflake proxy, the team members wanted to contribute their skills and expertise to an open-source project they cared about.

A dedicated app for Snowflake volunteers

The Bloco team built on the foundations already developed by the Guardian Project for the mobile Tor ecosystem, including IPtProxy. It's an easy-to-use library that brings together the tools and ongoing pluggable transport work needed to integrate Tor into mobile apps, making it easier to keep censorship-circumvention technology current and reuse it across new apps.

With these libraries already in place, that make it easy to build Tor apps for mobile, Bloco was able to focus their effort on:

Making sure the app runs successfully in the background for as long as possible, while using as little battery as possible.
Getting the user experience right, so everyone understands what the app is for, and can configure it correctly and according to their internet setup and capabilities.
Keep volunteers motivated by showing statistics of how much they're helping across time.

The result is Snowflake Volunteer, a single-purpose app that gives volunteers control over when and how they contribute. Users can allow it to run in the background, restrict it to unmetered networks such as Wi-Fi, choose to run it only while the device is charging, and set a limit on how many people it can help simultaneously. Once enabled, the app automatically connects with people seeking a Snowflake proxy and helps route their connection to the Tor network.

After an initial round of testing and feedback with the Tor community, Snowflake Volunteer was launched publicly in April. In May, we saw an average of approximately 1,300 daily unique proxy IP addresses. By June that had risen to approximately 1,700 per day–an increase of 29% in one month. During this initial period, activity reached a high of more than 2,100 daily proxies. This suggests that a dedicated app can bring additional volunteers into the Snowflake community.

Become a Snowflake volunteer by downloading Snowflake Volunteer

Snowflake Volunteer is available on F-Droid and Google Play. For those who want to tinker with the app, you can also build it from the source code. Helping people bypass internet censorship takes a global community. Tell a friend about this new tool or share this post so more people can learn about this app and provide feedback.

We also would like to thank our community of localizers. Thanks to their efforts, the app is already available in 8 languages (Chinese, English, French, German, Japanese, Portuguese, Turkish and Vietnamese). If you want to expand access to Snowflake Volunteer, consider contributing translations into more languages. Localization is how we reach this global community. Learn more about the process, and get started.

We analyzed 180 available daily Snowflake broker reports covering January 1 through June 30, 2026. Snowflake broker statistics are published as aggregated snowflake-stats descriptors through Tor Metrics’ CollecTor archive ↩

New Release: Tails 7.10

2026-07-23T00:00:00Z

New features

New shutdown procedure

Tails now uses the standard shutdown procedure from GNOME.

The standard shutdown procedure is a bit slower, but better prevents data loss.

For example, the Power Off confirmation dialog informs you if an application needs to be closed or an open document needs to be saved before shutting down.

Even without confirming or saving the open documents, Tails will shut down after 60 seconds.

You can still use the faster emergency shutdown as before.

Celluloid video player

We replaced GNOME Videos with Celluloid , a more modern and reliable video player.

For added security, Celluloid cannot access the network. You can either:

Open online videos, like MP4 and AVI files, in Tor Browser.
Open online streaming addresses, like IPTV and HLS addresses, in VLC , installed as additional software.

Celluloid doesn't work on some computer from 2011 or earlier.

You can use VLC instead, installed as additional software.

Changes and updates

Update Tor Browser to 15.0.19.
Update some firmware packages. This improves support for newer hardware: graphics, Wi-Fi, and so on.

For more details, read our changelog.

Get Tails 7.10

To upgrade your Tails USB stick and keep your Persistent Storage

Automatic upgrades are available from Tails 7.0 or later to 7.10.
If you cannot do an automatic upgrade or if Tails fails to start after an automatic upgrade, please try to do a manual upgrade.

To install Tails 7.10 on a new USB stick

Follow our installation instructions.

The Persistent Storage on the USB stick will be lost if you install instead of upgrading.

To download only

If you don't need installation or upgrade instructions, you can download Tails 7.10 directly:

Support and feedback

For support and feedback, visit the Support section on the Tails website.

New Alpha Release: Tor Browser 16.0a9

2026-07-23T00:00:00Z

Tor Browser 16.0a9 is now available from the Tor Browser download page and also from our distribution directory.

This version includes important security updates to Firefox.

⚠️ Reminder: The Tor Browser Alpha release-channel is for testing only. As such, Tor Browser Alpha is not intended for general use because it is more likely to include bugs affecting usability, security, and privacy.

Moreover, Tor Browser Alphas are now based on Firefox's betas. Please read more about this important change in the Future of Tor Browser Alpha blog post.

If you are an at-risk user, require strong anonymity, or just want a reliably-working browser, please stick with the stable release channel.

It's ESR transition season again!

Well actually, it has been ESR transition season throughout this entire release cycle! As described in the aforementioned Future of Tor Browser Alpha blog post, we have been incrementally rebasing our Alpha channel on Firefox betas since December of last year. As a result, we now stand before you with Tor Browser 16.0a9 which is based on Firefox ESR 153.

We will continue rebasing Tor Browser 17.0 Alpha branches on Firefox betas throughout the remainder of the Tor Browser 16.0 release cycle. However, new feature-work for now must be put on hold for a few reasons:

We must focus our attention on resolving our Bugzilla Audit issues to ensure the features we have inherited from upstream comply Tor Browser's threat model and to patch any changes which do not.
Feature work targeting 16.0 stable would need to be cherry-pick'd onto our 17.0 Alpha branches to ensure we don't lose any work. The more invasive a feature patch is, the harder it will be to port to newer versions. This would also be a potentially error-prone process and there is some risk we would lose patches along the way.
We need to finish stabilizing as soon as possible as we have hard external deadlines which cannot be moved: the end-of-life of Firefox ESR 140 on October 13th and the Google Play Minimum Target API Level requirement on November 1st

Challenges and Triumphs

💍 Sharing the Load

Rebasing the hundreds of Tor Browser patches onto newer versions of Firefox is a challenging task. It is like maintaining the structural stability of sand-castle at high-tide with the waves crashing all around you.

As such, it quickly become clear early in this new process that we would need to do something if we wanted to avoid burning out the few developers typically involved in this work. To mitigate this, we shared the knowledge internally and spread the work out across all eight members of the team. This way, each developer was only responsible for at most two or three rebases throughout the entire release cycle.

🎨 UI Code Churn

Over the past year, Firefox has developed and integrated two major changes to the UI in Firefox: a redesign of about:preferences in Firefox Desktop and a migration from Material 2 to Material 3 in Firefox Android.

Adapting to these types of changes to the frontend are typically rather time-consuming for us, as many (if not the majority) of our patches modify Firefox's UI in some way. For example, we have an entire preferences page on Tor Browser desktop dedicated to configuring how the browser connects to the Tor Network. On Android, we similarly have various additions to the menus, configuration options, and custom UI.

Whenever Mozilla modifies their design systems and Firefox's user interface, we necessarily have to adapt our own custom additions to match. Otherwise, our Tor Browser-specific UI elements would look completely out of place and potentially confuse users (as well as simply looking unprofessional). Therefore, each of these upstream changes requires collaboration with the Tor Project's UX team to update our features' designs and of course development time to implement.

In addition to the time-cost associated with the extra engineering and UX collaboration, very often our old patches simply do not apply cleanly due to the amount of code which has changed. For example, the about:preferences changes on Firefox Desktop are essentially a complete re-write which means we also have to completely re-write our own settings changes without regressing in functionality.

On the plus side, one benefit of our new processes is that we have been able to spread out this work over the entire release cycle. In the past way of doing things, we would have discovered all UX elements which needed to be fixed, updated our designs, and re-implemented in the course of a few months during the old ESR transition season. Under this new way of working, we have been able to incrementally fix things throughout the development cycle.

The benefits of working this way does not just apply to UX of course. It is much easier to find regressions across the entire stack when rebasing between one major Firefox version at a time instead of across 12 or 13. It is also much easier for developers to fix individual regressions one at a time compared to diagnosing, disentangling, and fixing multiple bugs concurrently (divide et impera!).

⚙️ Pending Google Target API Level Requirements

Every year, Google requires new Android app releases to target an updated minimum API level. This means, we would not be able to upload new versions of Tor Browser Stable past a certain date (usually August 1st with an extension to November 1st typically possible) without first updating the app to support the new minimum target API level. Fortunately, we inherit most of the required changes from Mozilla when rebasing to the next major ESR.

However, this requirement does impose a hard deadline for the absolute latest we can responsibly stabilize Tor Browser Alpha and promote it to Stable. We've been fortunate in the past few years to make the deadline with a few days to spare (October 28th for Tor Browser 15, October 22nd for Tor Browser 14, etc). Given how far ahead of the curve we are this year, we are hoping to release about a month earlier in September (fingers crossed!).

🤖 Android APKs too big

The Google Play Store has a strict size limit of about 100 megabytes for Android applications. New functionality added to Firefox Android over the past year means a larger application which results in new headaches for Tor Browser developers. This release cycle was no exception to this rule and we have had to get creative with our size reductions.

In the past, we have been able reduce our package size though various methods including:

Our most recent effort has been the most invasive yet! For some background, the Firefox application consists of (among other things): various shared libraries, the Firefox executable, a library known as 'xul' which contains most of Firefox's natively compiled functionality, and finally a file known as omni.ja. This omni.ja file is a zip archive which contains the JavaScript, HTML, images, and other assets used in Firefox.

This time around, to reduce the size of our Android package we havechanged how this archive is compressed. We modified the Firefox build system to compress this archive with xz and we modified Firefox itself to decompress this archive at runtime. This work did require a few iterations to get right. In the end, we got back about 3 megabytes with these changes and got us once again under Google's imposed size budget.

📉 Even Less Telemetry

Over the years, we have worked to incrementally remove dependencies from Tor Browser Android as part of the aforementioned size reduction work. We of course inherit most of these dependencies from Firefox Android and unfortunately some of them can be labeled as 'trackers'. While we do disable telemetry by default at runtime, the code which implements it remains in the codebase.

We're happy to report that as of Tor Browser 16.0a8, are down to only 1 'tracker' library in the Tor Browser Android codebase: Mozilla Telemetry. Again, this telemetry is disabled at runtime, but this is one more unused dependency which we can hopefully remove in the future (and maybe get some more bytes back!).

Current Status

We have:

incrementally rebased Tor Browser and Tor Browser for Android to Firefox ESR 153 from Firefox ESR 140
updated the build systems with the latest dependencies and fixed a few reproducibility issues
triaged most of the upstream changes from the past year and flagged over 250 issues for further review (triaging of Firefox 153 is in progress)
resolved about half of these triaged issues

For the remainder of this release cycle, we will be focusing on auditing these issues and fixing bugs until the 16.0 alpha series is ready to become Tor Browser Stable 16.0. We are optimistically targeting a September release, which would put us one month ahead of schedule compared to last year.

Known Issues

🦊 Firefox Branding

In some places in the browser there may be Firefox branding (e.g. logos, cute little foxes, etc) instead of Tor Browser branding. We're currently tracking one known instance in tor-browser#44998. If you discover any other instances lurking about, please open an issue!

🌐 All websites marked 'insecure' on Tor Browser Android

Currently, the identity block in the URL bar on Tor Browser Android will always report insecure (e.g. a shield icon with a slash through it). For now, you can tap this icon and verify the certificate manually. This issue is being tracked in tor-browser#45115

Send us your feedback

Now is a great time to become an alpha tester! 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 16.0a8 is:

All Platforms
- Updated NoScript to 13.6.30.90201984
- Bug tor-browser#43819: Show custom security level on android
- Bug tor-browser#44748: Revert Funding the Commons Implementations
- Bug tor-browser#44811: Remove the lock on pdfjs.disable.
- Bug tor-browser#45101: Rebase Tor Browser onto 153.0esr
- Bug tor-browser#45131: Security level is using an unsafe getBoolPref
- Bug tor-browser-build#41831: Update libevent to 2.1.13
Windows + macOS + Linux
- Updated Firefox to 153.0esr
- Bug tor-browser#44439: Remove translate action from urlbar
- Bug tor-browser#44883: Remove urlbar quick action for labs
- Bug tor-browser#45029: Convert connection status settings to new design and config approach
- Bug tor-browser#45055: Rename --color-gray-05 to --color-gray-0
- Bug tor-browser#45081: Use the new "Acorn" icons on desktop
- Bug tor-browser#45110: Disable the settings redesign until ready for us
- Bug tor-browser#45112: Missing CSS border tokens in 153
- Bug tor-browser#45132: nsAppFileLocationProvider.cpp: use of undeclared identifier 'XRE_EXECUTABLE_FILE'
- Bug tor-browser-build#41800: Create a script that adapts the Tor Browser manual HTMLs to work in Tor Browser
macOS
- Bug tor-browser#45108: Artifact generation fails due to missing .DS_Store in the branding directories
Android
- Updated GeckoView to 153.0esr
- Bug tor-browser#43820: Use SecurityLevel integration on android
- Bug tor-browser#44157: Remove secret setting toggle for Tab Management Redesign
- Bug tor-browser#45045: Remove moz asset in Downloads screen
- Bug tor-browser#45103: Disable broken "tab management"
- Bug tor-browser#45109: No value passed for parameter 'jsEnabled'
- Bug tor-browser#45118: Audit and disable Mozilla VPN promo
- Bug tor-browser#45130: Clean up TorHomePage padding
Build System
- All Platforms
  - Bug tor-browser-build#41838: Update personal_access_tokens URL in tools/fetch_changelogs.py
- Windows + Linux + Android
  - Updated Go to 1.26.5
- Windows
  - Bug tor-browser-build#41819: Fix windows-rs URL in projects/firefox/config

New Release: Tor Browser 15.0.19

2026-07-21T00:00:00Z

Tor Browser 15.0.19 is now available from the Tor Browser download page and also from our distribution directory.

This version includes important security updates to Firefox.

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 15.0.18 is:

All Platforms
- Updated NoScript to 13.6.31.1984
- Bug tor-browser#44748: Revert Funding the Commons Implementations
- Bug tor-browser#45117: Rebase Tor Browser stable onto 140.13.0esr
- Bug tor-browser#45124: Backport Security Fixes from Firefox 153
Windows + macOS + Linux
- Updated Firefox to 140.13.0esr
Android
- Updated GeckoView to 140.13.0esr
Build System
- All Platforms
  - Bug tor-browser-build#41838: Update personal_access_tokens URL in tools/fetch_changelogs.py
- Windows
  - Bug tor-browser-build#41819: Fix windows-rs URL in projects/firefox/config

New Release: Tor Browser 15.0.18

2026-07-14T00:00:00Z

Tor Browser 15.0.18 is now available from the Tor Browser download page and also from our distribution directory.

This version includes important security updates to Firefox.

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 15.0.17 is:

All Platforms
- Updated NoScript to 13.6.30.1984
- Bug tor-browser#45111: Cherry-pick latest firefox/esr140 commits on 140.12.0esr
Build System
- All Platforms
  - Bug tor-browser-build#41821: Update gpg subkeys for boklm
- Windows + Linux + Android
  - Updated Go to 1.25.12

New Alpha Release: Tor Browser 16.0a8

2026-07-02T00:00:00Z

Tor Browser 16.0a8 is now available from the Tor Browser download page and also from our distribution directory.

This version includes important security updates to Firefox.

Moreover, Tor Browser Alphas are now based on Firefox's betas. Please read more about this important change in the Future of Tor Browser Alpha blog post.

If you are an at-risk user, require strong anonymity, or just want a reliably-working browser, please stick with the stable release channel.

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 16.0a7 is:

All Platforms
- Updated NoScript to 13.6.25.90301984
- Updated Tor to 0.4.9.11
- Updated OpenSSL to 3.5.7
- Bug tor-browser#44857: Drop browser.display.use_system_colors from our preference list
- Bug tor-browser#44896: Review Mozilla 2030929: Remove unused pref privacy.partition.network_state
- Bug tor-browser#45018: resistfingerprinting not available in appearance.mjs in 152
- Bug tor-browser#45019: ReportBrokenSite startup error in 152
- Bug tor-browser#45047: Cross-site oracle via worklet rejection error in Safer Mode
- Bug tor-browser#45072: Disable XSLT already for 16.0
Windows + macOS + Linux
- Updated Firefox to 152.0a1
- Bug tor-browser#44528: Make sure desktop IP Protection is disabled on desktop
- Bug tor-browser#44795: Revert BB 27604 patch as not needed anymore
- Bug tor-browser#44844: Use new urlbar CSS variables
- Bug tor-browser#44888: Use --button-opacity-disabled for disabled styling.
- Bug tor-browser#44955: Use context-fill for about-wordmark.svg
- Bug tor-browser#44956: Switch colours in letterboxing setting icons to match the tab-alignment icons
- Bug tor-browser#45016: Several errors about EngineProcess.sys.mjs in 152
- Bug tor-browser#45017: Wrong letterboxing background in 152
- Bug tor-browser#45037: Potential runtime errors in the search service when changing JS status
- Bug tor-browser#45043: Re-add missing changes to settings after 151/152 rebase
- Bug tor-browser#45083: Error in about:preferences due to ipprotection missing
macOS
- Bug tor-browser#44728: Bundled fonts are broken on macOS when the GPU process is enabled
Linux
- Bug @ libfontconfig.so.1#45048: Backport Bugzilla 2041887: Crash in after users upgraded to fontconfig 2.18.0 [tor-browser]
Android
- Updated GeckoView to 152.0a1
- Bug tor-browser#43856: Fix onBackPressed() deprecation
- Bug tor-browser#44091: Add frequent regions to tor connection assist for android
- Bug tor-browser#44175: Remove all default browser functionality (Android)
- Bug tor-browser#44769: TBA crash screen has firefox asset as well as a "Send crash report" button
- Bug tor-browser#45052: Initialise Tor modules on android in the same order as desktop
Build System
- All Platforms
  - Bug tor-browser-build#41802: Remove the tor daemon requirement for signing
  - Bug tor-browser-build#41809: Update toolchains for Firefox 152
  - Bug tor-browser-build#41813: Disable build artifacts in make generate_gradle_dependencies_list-geckoview
  - Bug tor-browser-build#41821: Update gpg subkeys for boklm
  - Bug tor-browser-build#41823: Add versions information to the toolchain list update
  - Bug tor-browser-build#41827: Update morgan's keychain with renewed key
- Windows + Linux + Android
  - Updated Go to 1.26.4
- Windows
  - Bug tor-browser-build#41810: Define GetAddrInfoExCancel on mingw
- Android
  - Bug tor-browser#45086: Compress omni.ja with xz on Android
  - Bug tor-browser-build#41830: Update the browser project to change omni.ja.xz

New Release: Tails 7.9.1

2026-07-01T00:00:00Z

Changes and updates

Update Tor Browser to 15.0.17.
Update the Tor client to 0.4.9.11.
Update the Linux kernel to 6.12.94, which fixes CVE-2026-43503 (DirtyClone) and CVE-2026-46331 (PACKET_EDIT_MEME), vulnerabilities that could allow an application in Tails to gain administration privileges.

For example, if an attacker was able to exploit other unknown security vulnerabilities in an application included in Tails, they might then use CVE-2026-46331 to take full control of your Tails and deanonymize you.

This attack is unlikely, but could be performed by a strong attacker, such as a government or a hacking firm. We are not aware of this vulnerability being used in practice until now.

Fixed problems

For more details, read our changelog.

Get Tails 7.9.1

To upgrade your Tails USB stick and keep your Persistent Storage

Automatic upgrades are available from Tails 7.0 or later to 7.9.1.
If you cannot do an automatic upgrade or if Tails fails to start after an automatic upgrade, please try to do a manual upgrade.

To install Tails 7.9.1 on a new USB stick

Follow our installation instructions.

The Persistent Storage on the USB stick will be lost if you install instead of upgrading.

To download only

If you don't need installation or upgrade instructions, you can download Tails 7.9.1 directly:

Support and feedback

For support and feedback, visit the Support section on the Tails website.

Arti 2.5.0 released: Stable Counter Galois Onion

2026-06-30T00:00:00Z

Arti is our ongoing project to create a next-generation Tor implementation in Rust. We're happy to announce the latest release, Arti 2.5.0.

This release marks Counter Galois Onion as a stable feature and includes it in full feature builds. Likewise, Congestion Control is now enabled in default builds of Arti, increasing the overall speed without any further configuration.

Unfortunately, this release also comes with the disclosure of two medium-severity DoS security issues, TROVE-2026-024 as well as TROVE-2026-027, whose fixes are of course included within the release.

Additionally, this release continues our ongoing development towards using Arti as a relay and as a directory authority.

Another noteworthy change is that we've increased our minimum supported Rust version to Rust 1.91, released in October 2025.

Of course, this release also contains a number of bugfixes, cleanups, and improvements throughout various parts of the code base.

For full details on what we've done, including API changes, and for information about many more minor and less-visible changes, please see the CHANGELOG.

For more information on using Arti, see our top-level README, and the documentation for the arti binary.

Thanks to everybody who's contributed to this release, including 5225225, Neel Chauhan, hjrgrn, moumenalaoui, pryty26.

Also, our deep thanks to our sponsors for funding the development of Arti!