Skip to main content
Mallory
MediumVulnerability

CVE-2019-13752: Out-of-Bounds Read in Chromium SQLite FTS3

Published Dec 10, 2019 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.5Medium · v3.1
EPSS1.7%78th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
GoogleDebian ProjectRed HatFedora ProjectCanonical
IdentifiersCVE-2019-13752CWE-125 · Out-of-bounds Read

CVE-2019-13752 is an out-of-bounds read in the SQLite component used by Google Chrome and Chromium prior to version 79.0.3945.79. The flaw affects FTS3 processing, specifically the fts3NodeAddTerm path, where insufficient detection of FTS3 shadow-table corruption can result in reads outside the intended memory bounds. A crafted HTML page can trigger the vulnerable SQLite processing.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A remote attacker can cause disclosure of potentially sensitive data from the affected browser process memory. The documented CVSS v3 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, indicating high confidentiality impact without integrity or availability impact.

Mitigation

If you can’t patch tonight, do this now.

Until updates can be deployed, reduce exposure to untrusted web content and prevent users from opening attacker-controlled HTML pages in vulnerable browser versions. Apply browser isolation or sandboxing controls where available; these measures may reduce exposure but do not correct the underlying out-of-bounds read.

Remediation

Patch, then assume compromise.

Update Google Chrome or Chromium to version 79.0.3945.79 or later, or install the vendor-provided security update incorporating the SQLite FTS3 shadow-table corruption-detection fix. For Red Hat Enterprise Linux 8, apply the SQLite security update provided by RHSA-2020:1810. Red Hat Enterprise Linux 6 Supplementary Chromium users should apply RHSA-2019:4238 and restart Chromium after updating.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
CanonicalUbuntu Linuxoperating_system
Debian ProjectDebian Linuxoperating_system
Fedora ProjectFedoraoperating_system
GoogleChromeapplication
Red HatEnterprise Linux Desktopoperating_system
Red HatEnterprise Linux For Scientific Computingoperating_system
Red HatEnterprise Linux Serveroperating_system
Red HatEnterprise Linux Workstationoperating_system
FAQ

Frequently asked questions

Is CVE-2019-13752 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2019-13752 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2019-13752?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2019-13752.
Is there a patch for CVE-2019-13752?
Update Google Chrome or Chromium to version 79.0.3945.79 or later, or install the vendor-provided security update incorporating the SQLite FTS3 shadow-table corruption-detection fix. For Red Hat Enterprise Linux 8, apply the SQLite security update provided by RHSA-2020:1810.
What products are affected by CVE-2019-13752?
Google Chrome, Debian Project Debian Linux, Red Hat Enterprise Linux Desktop, Red Hat Enterprise Linux For Scientific Computing, Red Hat Enterprise Linux Server, and 3 more.
How severe is CVE-2019-13752?
CVE-2019-13752 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 1.7% (78th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.