Skip to main content
CVE-2024-10458VulnerabilityPublished Updated

CVE-2024-10458: Mozilla Firefox · Permission leak via embed or object elements

Affects Mozilla FirefoxSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium · fixed in 132 : update Mozilla Firefox when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 132, 128.4, 115.17
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade Mozilla Firefox to 132, 128.4 or 115.17.

Affected software

ProductAffectedFixed in
Mozilla FirefoxAffected
  • <132
  • <128.4
  • <115.17
Fixed in
  • 132
  • 128.4
  • 115.17

AI-suggested

1. Immediately plan to update Mozilla Firefox to version 132 or later and Thunderbird to version 132 or later once patches are officially released. 2. If you cannot patch yet, restrict or monitor the use of embed and object HTML elements in internal web applications and email content, especially from untrusted sources. 3. Implement content security policies (CSP) that limit embedding of external content and enforce strict origin isolation. 4. Educate users about the risks of interacting with suspicious links or embedded content, emphasizing caution with unknown or untrusted sites. 5. Use browser security features such as site isolation and sandboxing to minimize cross-origin permission leaks. 6. Monitor network traffic and logs for unusual activity that could indicate exploitation attempts involving embedded content. 7. Coordinate with IT and security teams to prioritize patch management for browsers and email clients across the organization. 8. Consider deploying endpoint protection solutions that can detect anomalous browser behavior related to permission leaks.

Description

A permission leak could have occurred from a trusted site to an untrusted site via `embed` or `object` elements. This vulnerability affects Firefox < 132, Firefox ESR < 128.4, Firefox ESR < 115.17, Thunderbird < 128.4, and Thunderbird < 132.

References

Community reviews

Loading reviews…