How severe is CVE-2021-25369?

CVE-2021-25369 has a CVSS score of 6.2/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2021-25369?

Affected package information for CVE-2021-25369 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2021-25369?

No fixed release is recorded for CVE-2021-25369 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2021-25369 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2021-25369 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2021-25369 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2021-25369, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2021-25369?

CVE-2021-25369 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2021-25369 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2021-25369 (Samsung Mobile Devices Improper Access Control Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-11-08. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-11-29. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2021-25369?

CVE-2021-25369 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-25369 published, and has it been updated?

CVE-2021-25369 was published on March 26, 2021 and was last updated on October 21, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

MEDIUM severity

CVE-2021-25369

MEDIUM

CVE-2021-25369 is a medium-severity (CVSS 6.2) Information Exposure vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-11-08) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

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

Published

Mar 26, 2021

Updated

Oct 21, 2025

Affected

1 product

Patched

See advisory

Exploits

2 known

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-11-08. Federal agencies were required to remediate by 2022-11-29.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2021-25369.

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk-0.04%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-25369 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Description

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

Affected Products

1 product · 47 configurations

androidsamsung

4 versions

8.08.19.010.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An improper access control vulnerability in sec_log file prior to SMR MA…

security.samsungmobile.comGoogle-sheetDec 2020

An improper access control vulnerability in sec_log file prior to SMR MA…

cisa.govCISANov 2022

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2021-25369 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2021-25369 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.2/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-200Information Exposure

Weaponization

No known public exploit tooling found.

Timeline

First exploit

Dec 10, 2020

Disclosed

Mar 26, 2021

KEV added

Nov 8, 2022

Last updated

Oct 21, 2025

Identifiers

CVE-2021-25369

References

Websecurity.samsungmobile.com Websecurity.samsungmobile.com Webcisa.gov

Related vulnerabilities

This CVE is medium severity, in line with the other 8 CVEs with CWE-200.

CVE-2026-77362CVE-2026-77364CVE-2026-112953CVE-2026-112952CVE-2026-112948CVE-2026-112954CVE-2026-112947CVE-2026-111769Browse all CWE-200

Provenance

Sources

OSV.devNVDCISA KEVFIRST.org (EPSS)

Last verifiedOct 21, 2025

CVE-2021-25369

Exploitation Status

Actively exploited in the wild

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2021-25369 in your dependencies?