Skip to content
Fencer Intel
critical 9.8

CVE-2016-5287 json

A potentially exploitable use-after-free crash during actor destruction with service workers.

published 2018-06-11 8 y ago modified 2026-06-17 4 mo ago also EUVD-2016-6238

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

A potentially exploitable use-after-free crash during actor destruction with service workers. This issue does not affect releases earlier than Firefox 49. This vulnerability affects Firefox < 49.0.2.

Patch / fix

  • Mozilla Firefox 49.0.2
  • firefox Ubuntu 14.04 LTS 49.0.2+build2-0ubuntu0.14.04.1
  • firefox Ubuntu 16.04 LTS 49.0.2+build2-0ubuntu0.16.04.2

ubuntu advisories UBUNTU-CVE-2016-5287

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • firefox-esr openSUSE Tumbleweed 128.5.1-1.1
  • MozillaFirefox openSUSE Tumbleweed 50.1.0-1.1

opensuse advisories openSUSE-SU-2024:14572-1openSUSE-SU-2024:10071-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-5287 updated cvss 9.8

firefox: Crash in nsTArray_base

  • Red Hat Enterprise Linux 5 firefox Red Hat Enterprise Linux 6 firefox Red Hat Enterprise Linux 7 firefox
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.35% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • Mozilla Firefox

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.