samsung exynos 2100 firmware

Name: samsung exynos 2100 firmware
Brand: samsung

productUS

cpe:2.3:o:samsung:exynos_2100_firmware:*:*:*:*:*:*:*:*

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

KEV-listed

EPSS ≥ 10%

critical

by severity

0critical11high8medium2low

updated 2026-10-27

vulnerabilities (65)

Related CVEs.

sort

ID	severity	EPSS	exploitable	patched	published	affected
CVE-2025-54328US	—	0.52% (44th)	Exploit	no fix	2026-04-06	—
CVE-2024-56426US	—	0.44% (38th)	Exploit	no fix	2025-11-04	—
CVE-2023-36481US	high7.5	0.63% (50th)	—	no fix	2023-08-28	—
CVE-2025-26782US	—	0.60% (48th)	—	no fix	2025-10-20	—
CVE-2024-55568US	—	0.60% (48th)	—	no fix	2025-10-20	—
CVE-2023-41112US	high7.5	0.59% (48th)	—	no fix	2023-11-08	—
CVE-2023-41111US	high7.5	0.59% (48th)	—	no fix	2023-11-08	—
CVE-2023-37368US	high7.5	0.55% (46th)	—	no fix	2023-09-08	—
CVE-2023-37367US	medium5.3OT elevated	0.53% (44th)	—	no fix	2023-09-08	—
CVE-2025-27891US	—	0.47% (41st)	—	no fix	2025-05-14	—
CVE-2025-62818US	—	0.46% (40th)	—	no fix	2026-04-07	—
CVE-2025-47202US	—	0.44% (38th)	—	no fix	2025-07-07	—
CVE-2025-26783US	—	0.43% (37th)	—	no fix	2025-05-14	—
CVE-2024-55569US	—	0.43% (37th)	—	no fix	2025-05-14	—
CVE-2025-26785US	—	0.43% (37th)	—	no fix	2025-05-14	—
CVE-2025-23102US	—	0.42% (36th)	—	no fix	2025-06-03	—
CVE-2023-50805US	—	0.41% (36th)	—	no fix	2024-07-09	—
CVE-2025-54329US	—	0.41% (36th)	—	no fix	2025-11-04	—
CVE-2024-52924US	—	0.41% (35th)	—	no fix	2025-03-06	—
CVE-2024-52923US	—	0.41% (35th)	—	no fix	2025-03-06	—
CVE-2024-29153US	—	0.41% (35th)	—	no fix	2024-07-09	—
CVE-2024-39890US	—	0.40% (34th)	—	no fix	2024-12-02	—
CVE-2023-49928US	high7.5	0.39% (32nd)	—	no fix	2024-06-05	—
CVE-2024-25074US	—	0.39% (32nd)	—	no fix	2024-09-10	—
CVE-2024-25073US	—	0.39% (32nd)	—	no fix	2024-09-10	—
CVE-2024-27360US	high7.5	0.38% (32nd)	—	no fix	2024-07-09	—
CVE-2024-29152US	high7.5	0.38% (32nd)	—	no fix	2024-06-04	—
CVE-2024-39343US	—	0.37% (31st)	—	no fix	2024-12-02	—
CVE-2025-27807US	—	0.36% (30th)	—	no fix	2026-01-05	—
CVE-2025-22377US	—	0.36% (29th)	—	no fix	2025-05-27	—
CVE-2025-49494US	—	0.36% (29th)	—	no fix	2025-11-04	—
CVE-2025-57834US	—	0.35% (29th)	—	no fix	2026-04-06	—
CVE-2024-46920US	—	0.35% (28th)	—	no fix	2025-01-13	—
CVE-2023-37377US	high7.5	0.34% (28th)	—	no fix	2023-09-08	—
CVE-2023-50803US	medium5.3	0.34% (27th)	—	no fix	2024-06-05	—
CVE-2025-54323US	—	0.32% (25th)	—	no fix	2025-11-04	—
CVE-2024-28818US	high7.5	0.32% (25th)	—	no fix	2024-06-05	—
CVE-2024-46921US	—	0.31% (24th)	—	no fix	2025-01-13	—
CVE-2025-58349US	—	0.31% (23rd)	—	no fix	2026-04-06	—
CVE-2023-50804US	medium5.3	0.31% (23rd)	—	no fix	2024-06-05	—
CVE-2025-53965US	—	0.29% (22nd)	—	no fix	2025-12-03	—
CVE-2024-46919US	—	0.29% (22nd)	—	no fix	2025-01-13	—
CVE-2023-43122US	medium4.6	0.29% (22nd)	—	no fix	2023-12-13	—
CVE-2025-26784US	—	0.28% (21st)	—	no fix	2025-05-14	—
CVE-2025-54324US	—	0.28% (20th)	—	no fix	2026-04-06	—
CVE-2025-59440US	—	0.28% (20th)	—	no fix	2026-04-06	—
CVE-2025-57835US	—	0.28% (20th)	—	no fix	2026-04-06	—
CVE-2024-56427US	—	0.27% (19th)	—	no fix	2025-05-14	—
CVE-2024-28068US	—	0.23% (14th)	—	no fix	2024-07-09	—
CVE-2024-45183US	—	0.23% (13th)	—	no fix	2025-08-04	—

showing 50 of 65

weaknesses (8)

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

CWE-787Out-of-bounds Write17 CVEs
CWE-400Uncontrolled Resource Consumption8 CVEs
CWE-125Out-of-bounds Read5 CVEs
CWE-476NULL Pointer Dereference4 CVEs
CWE-120Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')3 CVEs
CWE-200Exposure of Sensitive Information to an Unauthorized Actor3 CVEs
CWE-416Use After Free3 CVEs
CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer2 CVEs

sources (1)

Which sources assert this record, and when.

USNVD / CVE65 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