microsoft access

Name: microsoft access
Brand: microsoft

productUS

cpe:2.3:a:microsoft:access:*:*:*:*:*:*:*:*

A product tracked in the threat graph; the vulnerabilities below are known to affect it.

critical

by severity

0critical21high2medium0low

updated 2026-10-27

vulnerabilities (38)

Related CVEs.

sort

ID	severity	EPSS	exploitable	patched	published	affected
CVE-2007-0671US	high9.3OT critical	43.2% (99th)	KEV	no fix	2007-02-03	3 versions
CVE-2003-0665US	high7.5	30.1% (98th)	Exploit	no fix	2003-10-20	3 versions
CVE-2010-0814US	high9.3	22.9% (98th)	—	no fix	2010-07-15	2 versions
CVE-2000-0419US	high7.5	21.4% (98th)	—	no fix	2000-05-11	= 2000
CVE-2018-8312US	high7.8	21.3% (98th)	—	no fix	2018-07-11	2 versions
CVE-2010-1881US	high9.3	20.3% (97th)	—	no fix	2010-07-15	= 2003
CVE-2013-3155US	high9.3	20.2% (97th)	—	no fix	2013-09-11	3 versions
CVE-2013-3156US	high9.3	20.0% (97th)	—	no fix	2013-09-11	3 versions
CVE-2013-3157US	high9.3	18.7% (97th)	—	no fix	2013-09-11	3 versions
CVE-2008-3068US	high7.5	17.4% (97th)	—	no fix	2008-07-07	= 2007
CVE-2015-2503US	high9.3	16.5% (97th)	—	no fix	2015-11-11	4 versions
CVE-2018-0903US	high7.8	16.0% (97th)	—	no fix	2018-03-14	3 versions
CVE-2007-6357US	medium5.8	16.0% (97th)	—	no fix	2007-12-15	—
CVE-2006-3877US	high9.3	13.4% (96th)	—	no fix	2006-10-10	3 versions
CVE-2008-1200US	high9.3	12.0% (96th)	—	no fix	2008-03-06	= 2000
CVE-2020-0760US	high8.8	8.82% (95th)	—	no fix	2020-04-15	3 versions
CVE-2000-0788US	high10.0OT elevated	8.42% (95th)	—	no fix	2000-10-20	= 2000
CVE-1999-0364US	high10.0OT elevated	5.19% (92nd)	—	no fix	1999-01-01	= 97
CVE-2020-1582US	medium6.8	2.68% (86th)	—	no fix	2020-08-17	3 versions
CVE-2025-21186US	—	1.19% (68th)	—	no fix	2025-01-14	= 2016
CVE-2025-21366US	—	1.15% (67th)	—	no fix	2025-01-14	= 2016
CVE-2024-49142US	—	1.10% (65th)	—	no fix	2024-12-12	= 2016
CVE-2025-21395US	—	1.06% (64th)	—	no fix	2025-01-14	= 2016
CVE-2025-26630US	—	0.97% (62nd)	—	no fix	2025-03-11	= 2016
CVE-2026-69614US	high8.8	0.86% (58th)	—	no fix	2026-09-08	= 2016
CVE-2026-69778US	high8.8	0.82% (57th)	—	no fix	2026-09-08	= 2016
CVE-2026-69529US	high8.8	0.82% (57th)	—	no fix	2026-09-08	= 2016
CVE-2025-26642US	—	0.80% (56th)	—	no fix	2025-04-08	= 2016
CVE-2025-59235US	—	0.65% (51st)	—	no fix	2025-10-14	= 2016
CVE-2025-62552US	—	0.60% (48th)	—	no fix	2025-12-09	= 2016
CVE-2025-59232US	—	0.48% (42nd)	—	no fix	2025-10-14	= 2016
CVE-2026-64920US	—	0.47% (40th)	—	no fix	2026-08-11	= 2016
CVE-2026-64919US	—	0.47% (40th)	—	no fix	2026-08-11	= 2016
CVE-2026-64914US	—	0.47% (40th)	—	no fix	2026-08-11	= 2016
CVE-2026-64912US	—	0.47% (40th)	—	no fix	2026-08-11	= 2016
CVE-2026-64908US	—	0.47% (40th)	—	no fix	2026-08-11	= 2016
CVE-2026-64906US	—	0.47% (40th)	—	no fix	2026-08-11	= 2016
CVE-2026-69477US	high7.3	0.43% (37th)	—	no fix	2026-09-08	= 2016

weaknesses (8)

The flaw types (CWEs) most of these CVEs share.

CWE-122Heap-based Buffer Overflow9 CVEs
CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer7 CVEs
CWE-94Improper Control of Generation of Code ('Code Injection')5 CVEs
CWE-416Use After Free4 CVEs
CWE-121Stack-based Buffer Overflow3 CVEs
CWE-125Out-of-bounds Read3 CVEs
CWE-20Improper Input Validation3 CVEs
CWE-200Exposure of Sensitive Information to an Unauthorized Actor2 CVEs

sources (1)

Which sources assert this record, and when.

USNVD / CVE38 CVEs

scry

Products carry known vulnerabilities once they are exposed to the internet. See what is exposed on your perimeter with a free passive scan.

Free scan