Should you update to Brave 1.95.100?
No: install Brave 1.99.55 instead. Brave 1.95.100 is a security update Brave released on 9 Sep 2026 for Mac, Windows and Linux. It fixes 230 security flaws, 5 rated critical and 41 high by Brave.[1] One of them is already being used in attacks.
It has since been replaced by Brave 1.95.102, released 16 Sep 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.95.100, so there’s no reason to stop at this one. Software Update offers the newest version your device can run.
Is Brave 1.95.100 still safe?
Not any more. The 12 updates since, up to Brave 1.99.55, fix 1,142 security flaws that Brave 1.95.100 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 230 security flaws, 5 rated critical and 41 high by Brave.[1] The 46 critical and high ones are:
| Flaw | Severity | What Brave calls it |
|---|---|---|
CVE-2026-87464 | Critical | Use after free in WebGL |
CVE-2026-87488 | Critical | Use after free in WebGL |
CVE-2026-87438 | Critical | Out of bounds write in WebGL |
CVE-2026-87527 | Critical | Buffer overflow in WebGL |
CVE-2026-87628 | Critical | Use after free in Cast |
CVE-2026-87512 | High | Use after free in ANGLE |
CVE-2026-87585 | High | Double free in PDFium |
CVE-2026-87444 | High | Memory corruption in Codecs |
CVE-2026-87447 | High | Incorrect authorization in Network |
CVE-2026-87440 | High | Out of bounds read in Media |
CVE-2026-87633 | High | Use after free in Views |
CVE-2026-87525 | High | Out of bounds read in Chromoting |
CVE-2026-87578 | High | Use after free in Receiver |
CVE-2026-87517 | High | Race condition in Mobile |
CVE-2026-87524 | High | Use after free in Core |
CVE-2026-87569 | High | Missing authorization in Views |
CVE-2026-87554 | High | Race condition in Chromoting |
CVE-2026-87467 | High | Race condition in Updater |
CVE-2026-87492 | High | Incorrect authorization in DevTools |
CVE-2026-87520 | High | Use after free in Dawn |
CVE-2026-87514 | High | Use after free in Views |
CVE-2026-87650 | High | Out of bounds read in WebGL |
CVE-2026-87596 | High | Out of bounds read in ANGLE |
CVE-2026-87654 | High | Buffer overflow in ANGLE |
CVE-2026-87604 | High | Out of bounds read in ANGLE |
CVE-2026-87621 | High | Out of bounds write in ANGLE |
CVE-2026-87647 | High | Uninitialized resource in GPU |
CVE-2026-87646 | High | Use after free in Web Authentication |
CVE-2026-87500 | High | Improper validation of array index in ANGLE |
CVE-2026-87572 | High | Injection in DevTools |
| and 16 more | ||
Used in attacks
This fix closes a flaw that attackers were already using before the update came out, either on CISA’s list of flaws being used in attacks or in Brave’s own words.[2]
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.95.102 or later.
1.94.121 vs 1.95.100
Brave 1.94.121, released 4 Sep 2026, fixed 12 security flaws, one already used in attacks. Brave 1.95.100 fixes 230 security flaws and includes the fixes before it, so going straight to 1.95.100 gets you both.
- Before: Brave 1.94.121, 4 Sep 2026, 12 security flaws
- After: Brave 1.95.102, 16 Sep 2026, 42 security flaws
- Brave updates, every release and the latest version
- Updates, the latest version of everything HARD tracks
References
- ^ Brave. “Brave Release v1.95.100 (Chromium 153.0.8010.37)”, 9 Sep 2026.
- ^ Cybersecurity and Infrastructure Security Agency. “Known Exploited Vulnerabilities Catalog”.