How severe is CVE-2021-25369?

CVE-2021-25369 has a CVSS 3.x base score of 6.2, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2021-25369 being actively exploited?

Yes. CVE-2021-25369 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2022-11-08, which means active exploitation has been confirmed. It should be prioritised for remediation.

What products are affected by CVE-2021-25369?

CVE-2021-25369 primarily affects Samsung Android. In total, 47 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2021-25369?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.

Does CVE-2021-25369 have an EU (EUVD) identifier?

Yes. CVE-2021-25369 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2021-12265. It is also flagged as exploited in the EUVD (since 2022-11-08).

When was CVE-2021-25369 published?

CVE-2021-25369 was published on 2021-03-26 and last updated on 2026-06-17.

CVE-2021-25369

CVE-2021-25369 is a medium-severity vulnerability in Samsung Android with a CVSS 3.x base score of 6.2. It is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming it has been exploited in the wild (added 2022-11-08). The underlying weakness is classified as CWE-200.

Key facts

Severity: Medium (CVSS 3.x base score 6.2)
CVSS v2: 2.1
EPSS exploit prediction: 1% (62nd percentile)
Actively exploited: Yes — listed in CISA KEV (added 2022-11-08)
EU (EUVD) id: EUVD-2021-12265
EU exploitation: Flagged exploited in the ENISA EU Vulnerability Database (since 2022-11-08)
Weakness: CWE-200
Affected product: Samsung Android
Published: 2021-03-26
Last modified: 2026-06-17

Description

An improper access control vulnerability in sec_log file prior to SMR MAR-2021 Release 1 exposes sensitive kernel information to userspace.

Frequently asked questions

What is CVE-2021-25369?: An improper access control vulnerability in sec_log file prior to SMR MAR-2021 Release 1 exposes sensitive kernel information to userspace.
How severe is CVE-2021-25369?: CVE-2021-25369 has a CVSS 3.x base score of 6.2, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2021-25369 being actively exploited?: Yes. CVE-2021-25369 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2022-11-08, which means active exploitation has been confirmed. It should be prioritised for remediation.
What products are affected by CVE-2021-25369?: CVE-2021-25369 primarily affects Samsung Android. In total, 47 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2021-25369?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.
Does CVE-2021-25369 have an EU (EUVD) identifier?: Yes. CVE-2021-25369 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2021-12265. It is also flagged as exploited in the EUVD (since 2022-11-08).
When was CVE-2021-25369 published?: CVE-2021-25369 was published on 2021-03-26 and last updated on 2026-06-17.

References

Affected products (47)

cpe:2.3:o:samsung:android:8.0:-:*:*:*:*:*:*
cpe:2.3:o:samsung:android:8.1:-:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-apr-2019-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-apr-2020-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-aug-2019-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-aug-2020-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-dec-2018-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-dec-2019-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-dec-2020-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-feb-2019-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-feb-2020-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-feb-2021-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-jan-2019-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-jan-2020-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-jan-2021-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-jul-2019-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-jul-2020-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-jun-2019-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-jun-2020-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-mar-2019-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-mar-2020-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-may-2019-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-may-2020-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-nov-2018-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-nov-2019-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-nov-2020-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-oct-2018-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-oct-2019-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-oct-2020-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-sep-2019-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:9.0:smr-sep-2020-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:10.0:smr-apr-2020-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:10.0:smr-aug-2020-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:10.0:smr-dec-2019-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:10.0:smr-dec-2020-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:10.0:smr-feb-2020-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:10.0:smr-feb-2021-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:10.0:smr-jan-2020-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:10.0:smr-jan-2021-r1:*:*:*:*:*:*
cpe:2.3:o:samsung:android:10.0:smr-jul-2020-r1:*:*:*:*:*:*

More vulnerabilities in Samsung Android

CVE-2023-21456 — Critical (CVSS 9.0): Path traversal vulnerability in Galaxy Themes Service prior to SMR Mar-2023 Release 1 allows attacker to access…
CVE-2025-21043 — High (CVSS 8.8): Out-of-bounds write in libimagecodec.quram.so prior to SMR Sep-2025 Release 1 allows remote attackers to execute…
CVE-2025-21042 — High (CVSS 8.8): Out-of-bounds write in libimagecodec.quram.so prior to SMR Apr-2025 Release 1 allows remote attackers to execute…
CVE-2025-20936 — High (CVSS 8.8): Improper access control in HDCP trustlet prior to SMR Apr-2025 Release 1 allows local attackers with shell privilege to…
CVE-2023-21480 — High (CVSS 8.5): Improper input validation vulnerability in CertByte prior to SMR Apr-2023 Release 1 allows local attackers to launch…
CVE-2023-30692 — High (CVSS 8.5): Improper input validation vulnerability in Evaluator prior to SMR Oct-2023 Release 1 allows local attackers to launch…

All CVEs affecting Samsung Android →

Other CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) vulnerabilities

CVE-2026-27604 — Critical (CVSS 10.0): FOSSBilling is a free, open-source billing and client management system. Starting in version 0.5.4 and prior to version…
CVE-2026-40965 — Critical (CVSS 10.0): Cloud Foundry UAA versions v76.12.0 through v78.12.0 are vulnerable to a private key exposure. The server contains a…
CVE-2026-42826 — Critical (CVSS 10.0): Exposure of sensitive information to an unauthorized actor in Azure DevOps allows an unauthorized attacker to disclose…
CVE-2025-29270 — Critical (CVSS 10.0): Incorrect access control in the realtime.cgi endpoint of Deep Sea Electronics devices DSE855 v1.1.0 to v1.1.26 allows…
CVE-2025-61481 — Critical (CVSS 10.0): An issue in MikroTik RouterOS v.7.14.2 and SwOS v.2.18 exposes the WebFig management interface over cleartext HTTP by…
CVE-2025-53624 — Critical (CVSS 10.0): The Docusaurus gists plugin adds a page to your Docusaurus instance, displaying all public gists of a GitHub user.…

Browse all CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) vulnerabilities →