diff --git a/content/notes/state-of-the-tor-uplift.md b/content/notes/state-of-the-tor-uplift.md
index 4d27f22..f2f2bd7 100644
--- a/content/notes/state-of-the-tor-uplift.md
+++ b/content/notes/state-of-the-tor-uplift.md
@@ -9,3 +9,5 @@ The [Tor Uplift project](https://wiki.mozilla.org/Security/Tor_Uplift) is an ini
On , Firefox 102 ESR was released. Today, on , Firefox 91 ESR will lose support. That gave a window of about three months (the duration of three Firefox stable releases) to re-base Tor Browser patches.
The first stable release of the Tor Browser based on ESR 102 hasn't yet shipped (it's close; [an alpha version is available](https://blog.torproject.org/new-alpha-release-tor-browser-120a2/)). Seven years into the Tor uplift, the Tor Project isn't able to keep up with the Firefox ESR release calendar. I don't think the Tor Uplift will succeed at getting the Tor Browser to track Firefox's stable channel; at best, it's keeping the Tor Browser from falling too far behind ESR.
+
+Update : 30 days since Firefox ESR 91 reached end-of-life, the latest stable Tor Browser release (11.5.4) is still based on v91. [Five CVEs fixes from v102 have already been backported](https://blog.torproject.org/new-release-tor-browser-1154/). It's reasonable to assume that v91 has issues of its own that won't be addressed. Until the v102-based 12.x hits stable: if you don't use "safest", you might want to re-consider that with this information in mind.