Skip to content
Server Security Center
KEVhigh8.8

CVE-2016-5198: Google Chromium V8 Out-of-Bounds Memory

Google Chromium V8 · listed in the CISA catalog of actively exploited vulnerabilities since 2022-06-08.

CVSS v3.1 (Ubuntu)
8.8
high
EPSS (exploit probability, 30 days)
34%
higher than 98.4% of all CVEs
Added to CISA KEV
2022-06-08
US federal due date 2022-06-22
Ubuntu priority
medium

CVE-2016-5198 explained

CVE-2016-5198 is a flaw in the V8 JavaScript engine used by Google Chrome and Chromium. Incorrect optimisation assumptions let a crafted HTML page perform arbitrary memory reads and writes, leading to code execution. It is listed in the CISA Known Exploited Vulnerabilities catalog, so it has been exploited in real attacks.

Impact

A remote attacker can execute code in the context of the affected browser or V8-based component. The attacker needs no privileges, and the attack complexity is low. A user must open a crafted HTML page. Successful exploitation fully compromises confidentiality, integrity and availability within the affected process. Fixed Chrome versions are 54.0.2840.90 for Linux, 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac.

Who is affected

On Ubuntu 14.04 LTS, chromium-browser is fixed in 58.0.3029.81-0ubuntu0.14.04.1172 and oxide-qt in 1.18.5-0ubuntu0.14.04.1. On Ubuntu 16.04 LTS, chromium-browser is fixed in 55.0.2883.87-0ubuntu0.16.04.1263 and oxide-qt in 1.18.5-0ubuntu0.16.04.1. libv8-3.14 has no fixed version published on Ubuntu 16.04 LTS or Ubuntu 18.04 LTS. Ubuntu 14.04 LTS and 16.04 LTS are end of life. Standard support for Ubuntu 18.04 LTS has ended.

Written with AI from the data on this page and checked against it automatically.

Official description

V8 in Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac included incorrect optimisation assumptions, which allowed a remote attacker to perform arbitrary read/write operations, leading to code execution, via a crafted HTML page.

CISA required action: Apply updates per vendor instructions.

CISA notes

Upstream versions (CVE record)

From the CVE record published by the vendor or CVE numbering authority.

  • Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac
    Affected
    • Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac
    Fixed in
    not stated

    Version statement as published by the CNA (free text).

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

What to do

  1. Update chromium-browser and oxide-qt to the fixed versions or later on Ubuntu 14.04 LTS and 16.04 LTS.
  2. Restart browsers and any applications that use oxide-qt so the patched code is loaded.
  3. Find systems that have libv8-3.14 installed, since no fixed version is published for it.
  4. Plan upgrades from end-of-life Ubuntu 14.04 LTS and 16.04 LTS to a supported release.
  5. Move Ubuntu 18.04 LTS systems to a supported release, or enroll them in Ubuntu Pro (ESM).

libv8-3.14 has no fixed version on Ubuntu 16.04 LTS or 18.04 LTS. Remove the package if nothing depends on it. Otherwise, do not let it process untrusted HTML or JavaScript. Ubuntu 16.04 LTS is end of life and should be upgraded. Ubuntu 18.04 LTS should also move to a supported release, because its standard support has ended.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Run on each Ubuntu or Debian server. Replace oxide-qt with the source package from the table above (this CVE affects 3 source packages).

1. Show installed packages built from the source package, with their versions

dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="oxide-qt"'

2. Compare each installed version with the fixed version for your release from the table (releases with a fixed version only)

I=INSTALLED_VERSION; F=FIXED_VERSION   # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac

3. Install the fix

sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="oxide-qt"{print $1}')

Services keep running the old code until they are restarted – restart the affected service or check with needrestart.

No fixed version yet on one release

Ubuntu 18.04 LTS: no fixed version of the affected packages yet, so every installed version there is affected. Until a fix is published:

  • Follow the vendor's advisory for a mitigation or patch: chromereleases.googleblog.com/2016/11/stable-channel-upda…
  • If the server does not need the package, remove it, or replace it with a maintained alternative.
  • Restrict exposure: keep the affected service off the internet, limit access with a firewall or VPN, and turn off the vulnerable feature where you can.

This page updates automatically when Ubuntu or Debian publish a fix.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-787 Out-of-bounds Write

Questions about CVE-2016-5198

Is this vulnerability exploited in the wild?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-06-08. The required action is to apply updates per vendor instructions. Whether it has been used in ransomware campaigns is unknown.
Do I need to restart anything after updating?
Yes. Running browsers and applications that use oxide-qt keep the old code in memory until they are restarted. Close and reopen them after the update.
Can a user be compromised without doing anything?
No. User interaction is required. The attack works when a user opens a crafted HTML page in an affected browser or V8-based component.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.