How do I check whether I am affected by CVE-2026-117875?

- Run `firefox --version` or check Help > About Firefox and compare with `159` or `153.6` for ESR - unknown for other checks, the sources do not say

What is the fix for CVE-2026-117875?

- Update Firefox to `159` or later - Update Firefox ESR to `153.6` or later

Who is not affected by CVE-2026-117875?

Not affected if: firefox-159-or-later, firefox-esr-153.6-or-later.

Live › vulnerability › CVE-2026-117875

Go to dashboard

unknownRuntime

Firefox: use-after-free in scrolling and overflow layout code

A use-after-free bug in Firefox's Layout Scrolling and Overflow component lets memory be reused after it is freed. The sources do not say what an attacker can achieve with it beyond memory corruption.

Summary written from the sources below. Check the originals before acting.

Known so far

3/6

unknown

no CVSS yet; severity from the sources

known so far3 of 6

missing: versions, primary source, exploitation

First public: Oct 27, 2026 UTC
Last modified: Oct 27, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-27 14:32 UTC. All times on this page are UTC.

Why it is unknown, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: Not known from the sources.
Needs a special setup: Not known from the sources.
Reachable from: Not known from the sources.
Worst case: Unknown, memory corruption in the browser.
CVSS said: No score. The facts above say medium; we keep the sources' unknown until an analyst looks.

Who is affected

Anyone running Firefox builds older than version 159 or ESR builds older than 153.6 is affected. The sources do not say whether any configuration or page interaction is needed to trigger it.

Know the next one before it finds you.

Add to Slack

Live › vulnerability › CVE-2026-117875

Go to dashboard

unknownRuntime

Firefox: use-after-free in scrolling and overflow layout code

Summary written from the sources below. Check the originals before acting.

Known so far

3/6

unknown

no CVSS yet; severity from the sources

known so far3 of 6

missing: versions, primary source, exploitation

First public: Oct 27, 2026 UTC
Last modified: Oct 27, 2026
Status: open
Known exploitation: None reported
Public exploit: None on GitHub
EPSS: not scored

First seen by InfraStack 2026-10-27 14:32 UTC. All times on this page are UTC.

Why it is unknown, and not just CVSS

Likelihood → · Impact ↓

critical

high

medium

high

medium

low

medium

low

Exploited: No reports yet.
Needs login: Not known from the sources.
Needs a special setup: Not known from the sources.
Reachable from: Not known from the sources.
Worst case: Unknown, memory corruption in the browser.
CVSS said: No score. The facts above say medium; we keep the sources' unknown until an analyst looks.

Who is affected

Anyone running Firefox builds older than version 159 or ESR builds older than 153.6 is affected. The sources do not say whether any configuration or page interaction is needed to trigger it.

Know the next one before it finds you.

Add to Slack

Firefox: use-after-free in scrolling and overflow layout code

Why it is unknown, and not just CVSS

Who is affected

Know the next one before it finds you.

Firefox: use-after-free in scrolling and overflow layout code

Why it is unknown, and not just CVSS

Who is affected

Know the next one before it finds you.

How to check

The fix

Who had it, and when

What the sources say, verbatim

Sources