Firefox Users Beware: Expiring Certificate Threatens Add-Ons and DRM Services
At a glance
- Mozilla’s Expiring Certificate: A Mozilla root certificate used to sign add-ons and other content expired on March 14, 2025.
- Pervasive Impact: Anyone running Firefox older than version 128, or ESR older than 115.13, could lose add-ons and DRM video playback.
- Critical Response Needed: The fix is simple: update Firefox.
- Broader Security Implications: Old browsers also stop getting security fixes, so an update is overdue anyway.
Update Firefox or lose your add-ons
Mozilla warned Firefox users in early March 2025 that a root certificate used to sign add-ons and other Mozilla content would expire on March 14. Users on older versions risked having their extensions disabled and DRM-protected streaming break. Newer versions were fine. They already include the replacement certificate, so the problem is outdated browsers, not a flaw in Firefox itself.
What the certificate does
Mozilla uses this root certificate to verify that add-ons and some other content come from Mozilla and haven’t been tampered with. It’s a signature check.
Once the old certificate expired, Firefox versions that didn’t have the new one could no longer verify signed add-ons and related components. Mozilla said Firefox 128 or later, and ESR 115.13 or later, include the updated certificate, and anyone still on an older build has also been missing months of security fixes that close holes attackers already know how to use.
Get the 5-Minute Weekday Cyber Brief
The cyber stories worth paying attention to, filtered from 100+ trusted sources and explained fast.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
What breaks without the update
Mozilla listed these effects for outdated versions:
- Add-Ons Disruption: Installed add-ons can be disabled and new ones can’t be installed, because Firefox can’t verify their signatures.
- DRM-Related Challenges: DRM-protected streaming on video and music services can stop working.
Who has to do what
The fix falls on a few groups:
- Mozilla Corporation: Rolled out the new certificate in recent versions and warned users ahead of the deadline.
- Service Providers: Streaming services and add-on developers may need to point affected users to an update.
- Cybersecurity Experts: IT teams should check for old Firefox installs, including ESR builds on managed machines.
Why certificates expire
Certificates expire on purpose. That limits how long a stolen or weakened key can be abused, and expiry only causes trouble when software isn’t updated to trust the replacement.
How to fix it
Users and administrators should take these steps:
Know what matters before your first meeting.
Weekday mornings. Five minutes. What changed in security, why it matters.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
- Immediate Certificate Renewal: Update to Firefox 128 or later, or ESR 115.13 or later, through Help > About Firefox.
- Public Awareness Campaigns: Help less technical relatives and coworkers check their browser version.
- Certificate Tracking: Companies need to track certificate expirations across their own systems so they get ahead of similar deadlines.
A five-minute fix
Firefox’s expiring certificate is a minor event with an easy fix. Update the browser and the add-ons come back. The bigger lesson is for IT teams, because certificate expirations are predictable and should be on a calendar long before they break something users depend on.
Newer CyberExperts coverage on this topic
This article still works as background. If you want the current picture, start with the freshest related coverage below and today's brief.
Citrix NetScaler CVE-2026-19490: The Auth Bypass That Went From PoC to Probes in a Day
CVE-2026-19490 is a CVSS 9.3 NetScaler Gateway/AAA auth bypass. A public PoC on Sept 2 was followed by live probes within a...
PaperCut NG/MF: The Print Server That Learned Remote Code Execution Again
CVE-2026-81578 and CVE-2026-82078 chain to pre-auth RCE on PaperCut Application Server. Confirm Emergency Patch Release 2, restrict admin exposure, and hunt like...
JFrog Artifactory CVE-2026-82329: Empty Join Key, Full Admin Token, Busy Scanners
CVE-2026-82329 lets attackers forge Artifactory admin tokens via a deterministic empty join key. Mass scanning peaked near 406,000 attempts; patch fixed builds...
Monday’s brief: Ivanti’s last VPN fix is due today, then WordPress update attacks, a fake Claude Code extension and Drupal stores
The fastest way to catch up on what changed after this article was published.
Start your morning with the signal that matters.
Get the biggest cybersecurity developments, why they matter, and where to go deeper on CyberExperts.
By subscribing you agree to our Privacy Policy.
Free. Weekdays. Built for operators.