Should you update to Brave 1.91.172?
No: install Brave 1.99.55 instead. Brave 1.91.172 is a security update Brave released on 12 Jun 2026 for Mac, Windows and Linux. It fixes 27 security flaws, 5 rated critical and 22 high by Brave.[1] None of them is known to be used in attacks.
It has since been replaced by Brave 1.91.175, released 17 Jun 2026, which includes all of its fixes. If you’re on an older version, install that instead.
Should you update?
No: install Brave 1.99.55 instead. Brave 1.99.55 came out on 4 Nov 2026 and includes every fix in Brave 1.91.172, so there’s no reason to stop at this one. Software Update offers the newest version your device can run.
Is Brave 1.91.172 still safe?
Not any more. The 30 updates since, up to Brave 1.99.55, fix 2,728 security flaws that Brave 1.91.172 doesn’t, and each became public the day its fix shipped. Installing it is safe: get it only from Brave’s own About Brave page, never from a link in an email, text or pop-up.
What it fixes
Brave lists 27 security flaws, 5 rated critical and 22 high by Brave.[1] The 27 critical and high ones are:
| Flaw | Severity | What Brave calls it |
|---|---|---|
CVE-2026-12007 | Critical | Use after free Core |
CVE-2026-12008 | Critical | Use after free DigitalCredentials |
CVE-2026-12009 | Critical | Insufficient validation of untrusted input Accessibility |
CVE-2026-12010 | Critical | Heap buffer overflow GPU |
CVE-2026-12011 | Critical | Use after free WebMIDI |
CVE-2026-12012 | High | Use after free Network |
CVE-2026-12014 | High | Use after free Cast |
CVE-2026-12015 | High | Use after free Autofill |
CVE-2026-12016 | High | Insufficient validation of untrusted input DevTools |
CVE-2026-12017 | High | Insufficient validation of untrusted input Extensions |
CVE-2026-12018 | High | Inappropriate implementation Mojo |
CVE-2026-12019 | High | Out of bounds write Codecs |
CVE-2026-12020 | High | Use after free Autofill |
CVE-2026-12022 | High | Race Safe Browsing |
CVE-2026-12023 | High | Use after free GPU |
CVE-2026-12024 | High | Insufficient policy enforcement DevTools |
CVE-2026-12025 | High | Insufficient validation of untrusted input Network |
CVE-2026-12026 | High | Out of bounds read Video |
CVE-2026-12027 | High | Insufficient policy enforcement Headless |
CVE-2026-12028 | High | Use after free GPU |
CVE-2026-12029 | High | Use after free Video |
CVE-2026-12030 | High | Heap buffer overflow GPU |
CVE-2026-12031 | High | Inappropriate implementation Views |
CVE-2026-12032 | High | Inappropriate implementation Passwords |
CVE-2026-12033 | High | Out of bounds read VideoCapture |
CVE-2026-12034 | High | Insufficient validation of untrusted input Linux Toolkit Theming |
CVE-2026-12035 | High | Use after free Views |
How to update, and how long it takes
A minute or two. Brave restarts and reopens your tabs.
- Open Brave and click the ☰ menu at the top right.Choose About Brave. Brave looks for the update and downloads it by itself.
- Click Relaunch.Brave closes and opens again with the same tabs.
To check it worked: ☰ menu → About Brave: it shows the version, like 1.84.135, and the Chromium it’s built on. It should say 1.91.175 or later.
1.91.171 vs 1.91.172
Brave 1.91.171, released 9 Jun 2026, fixed 74 security flaws, one already used in attacks. Brave 1.91.172 fixes 27 security flaws and includes the fixes before it, so going straight to 1.91.172 gets you both.
- Before: Brave 1.91.171, 9 Jun 2026, 74 security flaws
- After: Brave 1.91.175, 17 Jun 2026, 33 security flaws
- Brave updates, every release and the latest version
- Updates, the latest version of everything HARD tracks
References
- ^ Brave. “Brave Release v1.91.172 (Chromium 149.0.7827.115)”, 12 Jun 2026.