vciy

CVE-2024-6607

INDEX BUILT · 2026-10-18

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Leaving pointerlock by pressing the escape key could be prevented

CVE-2024-66074 of 4 sources documented this
4

rank 4 = 0 + 0 + 0 + 4 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00563  ·  without this subject the record ranks 4

What it costs you if it fires

NVD CVSS base score, then the CNA's own

no CVSS held by anyone  ·  without this subject the record ranks 4

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 4

How much of the world it touches

NVD CPE configurations

2 products in the CPE ranges  ·  without this subject the record ranks 0

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 4

Hindsight · the state

0.00563EPSSNOT IN KEVas of 2026-10-18
Severitynot scored
Harmnot stated
Exploitationnone in held sources
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2024-07-10, 707 days at 0.01, as of 2026-06-17. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Which product do you run? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Choose your product above to watch it.

Set up a watchlist (free with an account: one stack of three products)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

Patch by…

Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

ReachNo CVSS vector in held sources, so no reach or impact can be stated.
Weakness classCWE-763 Release of Invalid Pointer or Referencereceipt
Published consequencesCWE-763: Integrity, Availability, Confidentiality: Modify Memory, DoS: Crash, Exit, or Restart, Execute Unauthorized Code or Commandscwe-consequences@4.20

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in128receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
BOD 26-04 deadlineIf the system is reachable from the internet: 14 days. If not: fix at the next system upgrade.derived
Show full BOD 26-04 deadline

CISA has not scored it, so the directive's own defaults apply: automatable no, technical impact total. Calendar days from the KEV listing or from when you find it on a system, whichever is first. Federal agencies are bound from 7 Dec 2026, and contracts often carry it to suppliers. The directive and its table

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

Exploit probability0.00563 · top 54% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned bymozillareceipt
Recorded changes21 · last 18 Oct 2026derived

Affected & Fixed Versions as published

Affected productMozilla Firefox; Mozilla Thunderbirdreceipt
Published rangesmozilla firefox < 128.0; mozilla thunderbird < 128.0receipt
Fixed in128receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

It was possible to prevent a user from exiting pointerlock when pressing escape and to overlay customValidity notifications from a `&lt;select&gt;` element over certain permission prompts. This could be used to confuse a user into giving a site unintended permissions. This vulnerability affects Firefox < 128 and Thunderbird < 128. receipt

NVD's analysis a second authority

weakness
CWE-763
affected versions
mozilla firefox < 128.0; mozilla thunderbird < 128.0
also scored by
8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

check it yourself bugzilla.mozilla.org mozilla.org mozilla.org receipt

Movement the material steps

10 Jul 20240.00043
17 Mar 20250.00183 · scoring model v2025.03.14
15 Jun 20260.00531 · scoring model v2026.06.15
17 Jun 20260.00563

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 21 observations
10 Jul 20240.00043
17 Jul 20240.00045
17 Mar 20250.00183
25 Mar 20250.00206
29 Mar 20250.00657
30 Mar 20250.00206
4 Apr 20250.0023
15 Apr 20250.00051
25 Apr 20250.00056
5 May 20250.00066
17 Jul 20250.00071
16 Aug 20250.00076
17 Aug 20250.00707
18 Aug 20250.00687
20 Aug 20250.00707
2 Sep 20250.00687
18 Nov 20250.00423
21 Nov 20250.00687
28 Nov 20250.00932
15 Jun 20260.00531
17 Jun 20260.00563

21 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00563Published2024-07-09Index as of2026-06-17

Exploit probability more than doubled between 2025-08-16 and 2025-08-17 (0.00076 → 0.00707) and the record had been public for 1 year, 11 months when this index was last written.

Published 2024-07-09 receipt · Index as of 2026-06-17 derived

Siblings and hubs

Records related to this one

Its defect family

mozilla firefox

Of the 4 records in this family that state one, this holds the highest EPSS percentile: 0.44653.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2024-6607.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.