A remote code execution vulnerability exists when the Windows Jet Database Engine improperly handles objects in memory, aka 'Jet Database E…

published 2019-03-05 7y ago modified 2026-06-17 4mo ago also EUVD-2019-1363

cvss: 7.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 16.1%; EPSS 16.1% chance of exploitation in 30 days, percentile 96%
public exploits: 0; none known

A remote code execution vulnerability exists when the Windows Jet Database Engine improperly handles objects in memory, aka 'Jet Database Engine Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-0595, CVE-2019-0596, CVE-2019-0598, CVE-2019-0599, CVE-2019-0625.

Patch / fix

links 1

portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0597 advisory

Is CVE-2019-0597 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

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

CVSS scores

assigned by	version	score	vector
NVD	3.0	7.8	CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	9.3	AV:N/AC:M/Au:N/C:C/I:C/A:C

Affected products

Microsoft Windows
Microsoft Windows Server

References

portal.msrc.microsoft.com /en-US/security-guidance/advisory/CVE-2019-0597
patch, vendor-advisory
securityfocus.com /bid/106923
vdb-entry, third-party-advisory

Sources

CVE List CVE-2019-0597
NVD CVE-2019-0597

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.