Red Hat Firefox 140.17 Updates Fix 43 CVEs

P1 — VALIDATE AND UPDATEMedium to High · 6.1-7.5 (CVSS v3.1; advisory-specific)EXPLOITATION: NOT STATED

Quick Answer

Red Hat issued three Firefox 140.17 errata for supported RHEL extended streams. Inventory exact subscriptions and running browsers, install the matching signed build, restart sessions, validate policy and critical web applications, and retain repository and change evidence.

Confirm Scope And Apply The Supported Remediation

What to do now: Inventory RHEL 8.6, 9.2 and 10.0 extended-stream systems with Firefox, exact packages, repositories, active users, enterprise policy, owners, and maintenance windows. Match every host to its RHSA and subscription stream; do not install a build from another RHEL branch or infer exploitation from the grouped CVE list. Install the matching signed firefox-140.17.0-1 package from the subscribed Red Hat repository and restart active browser processes. Confirm installed and running versions, test authentication, certificates, proxies, extensions and critical sites, monitor regressions, and retain evidence.

Open the authoritative advisory

Last verified: 2026-10-30 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeFirefox 140.17 on RHEL 8.6, 9.2, and 10.0 extended-support streams
AdvisoryRHSA-2026:92228 / RHSA-2026:92227 / RHSA-2026:92226
CVEsCVE-2026-100756, CVE-2026-100757, CVE-2026-100758, CVE-2026-100759, CVE-2026-100762, CVE-2026-100766, CVE-2026-100767, CVE-2026-100769, CVE-2026-100770, CVE-2026-100771, CVE-2026-100772, CVE-2026-100773, CVE-2026-100774, CVE-2026-100775, CVE-2026-100776, CVE-2026-100777, CVE-2026-100778, CVE-2026-100779, CVE-2026-100780, CVE-2026-100781, CVE-2026-100782, CVE-2026-100783, CVE-2026-100784, CVE-2026-100785, CVE-2026-100786, CVE-2026-100788, CVE-2026-100789, CVE-2026-100790, CVE-2026-100791, CVE-2026-100792, CVE-2026-100794, CVE-2026-100797, CVE-2026-100801, CVE-2026-100803, CVE-2026-100807, CVE-2026-100811, CVE-2026-100818, CVE-2026-100819, CVE-2026-100820, CVE-2026-100821, CVE-2026-100832, CVE-2026-92035, CVE-2026-96869
Authoritative release date2026-10-29 18:29:13 UTC
Authority revision date2026-10-30 00:54:02 UTC
Affected versionsAdvisory-listed packages on Red Hat Enterprise Linux AppStream AUS (v.8.6); Red Hat Enterprise Linux AppStream E4S (v.9.2); Red Hat Enterprise Linux AppStream EUS (v. 10.0); Red Hat Enterprise Linux AppStream EUS EXTENSION (v.8.6), before the exact fixed builds in the corresponding RHSA.
Fixed versionfirefox-0:140.17.0-1.el10_0.src; firefox-0:140.17.0-1.el8_6.src; firefox-0:140.17.0-1.el9_2.src
CVSS base score6.1-7.5 (CVSS v3.1; advisory-specific)
CVSS severityMedium to High
Exploitation statusRed Hat does not state that these vulnerabilities are being maliciously exploited.; no exploitation claim is inferred.

What Changed

Three errata update Firefox to 140.17 on the listed extended-support streams. Red Hat rates the grouped errata Important; individual CVSS scores and prerequisites differ by CVE.

What To Validate Now

  1. Inventory. Inventory RHEL 8.6, 9.2 and 10.0 extended-stream systems with Firefox, exact packages, repositories, active users, enterprise policy, owners, and maintenance windows.
  2. Establish applicability. Match every host to its RHSA and subscription stream; do not install a build from another RHEL branch or infer exploitation from the grouped CVE list.
  3. Remediate. Install the matching signed firefox-140.17.0-1 package from the subscribed Red Hat repository and restart active browser processes.
  4. Validate. Confirm installed and running versions, test authentication, certificates, proxies, extensions and critical sites, monitor regressions, and retain evidence.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

A package update does not replace already running browser processes. Coordinate sessions and preserve the correct extended-support repository boundary.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.