SUSE · Security update for mozjs128
Affects SUSESource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 4.3 Medium.
Data as of 16 Nov 2026, 00:35 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 27 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 15 Nov 2026.
What to do
AI-suggested
A security update is available that addresses these vulnerabilities in mozjs128. Users and administrators should apply the update to versions 128.11.0 through 128.14.0 as provided by their vendor or distribution to mitigate these issues. No additional mitigation steps are specified beyond applying the official fixes.
Description
This security update for mozjs128 addresses multiple vulnerabilities across several components including the JavaScript engine, Graphics Canvas2D, Audio/Video GMP component, and others. The fixes cover issues such as sandbox escapes, same-origin policy bypasses, uninitialized memory usage, memory safety bugs, use-after-free, and potential local code execution. The update includes multiple versions (128.11.0 through 128.14.0) with various CVEs fixed in each. These vulnerabilities affect Firefox ESR, Thunderbird ESR, and Firefox and Thunderbird standard releases.
References
- suse.com/support/security/rating/ (opens in a new tab)
- ftp.suse.com/pub/projects/security/csaf/2025/opensuse-su-2025_20135-1.json (opens in a new tab)
- bugzilla.suse.com/1248162 (opens in a new tab)
- suse.com/security/cve/CVE-2025-5263/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-5264/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-5265/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-5266/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-5267/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-5268/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-5269/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-5283/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-6424/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-6425/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-6426/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-6429/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-6430/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-8027/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-8028/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-8029/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-8030/ (opens in a new tab)