What is the CVSS score of CVE-2025-23099?

CVE-2025-23099 has a CVSS 3.1 base score of 9.1 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H. EPSS exploitation probability: 0.1%.

How to fix or mitigate CVE-2025-23099?

Within 24 hours: Identify and document all affected devices in your environment (Samsung devices with Exynos 1480/2400 processors). Within 7 days: Implement device restrictions (disable untrusted app installations, enforce MDM policies, restrict network access if feasible). Within 30 days: Monitor Samsung security advisories for firmware patches and establish an expedited deployment plan once available; escalate communications with affected device users.

Exynos 1480 Firmware CVE-2025-23099

EUVD-2025-16677 CRITICAL

Out-of-bounds Write (CWE-787)

2025-06-02 cve@mitre.org

Buffer Overflow Samsung Exynos 1480 Firmware Exynos 2400 Firmware

9.1

CVSS 3.1 · NVD

View

Vulnerability Assessment

Weakness	CWE CWE-787 OWASP Top 10:2025 A06:2021 - Vulnerable and Outdated Components ASVS 5.0 V15 - Secure Coding and Architecture Bounds checking, write limits MITRE ATT&CK 2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Impact	CVSS 9.1.
Exploit ScenarioDerived	Trigger OOB write for privilege escalation.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.

No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 14, 2026

OOB write in Samsung Exynos 1480/2400 processors.

Earlier versions of this analysis (1)

v1 Mar 14, 2026 - 16:47 CVSS 9.1

OOB write in Samsung Exynos.

RemediationAI

Apply Samsung security update.

Affected VersionsENISA

n/a n/a

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-787 missing length check.

Know when Exynos 1480 Firmware gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 9.1 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

High

DescriptionCVE.org

An issue was discovered in Samsung Mobile Processor Exynos 1480 and 2400. The lack of a length check leads to out-of-bounds writes.

Executive ViewAI

Why It Matters

A critical vulnerability in Samsung's Exynos mobile processors (1480 and 2400) allows remote attackers to execute arbitrary code through memory corruption. This affects Samsung Galaxy devices and potentially other OEM devices using these processors, requiring immediate inventory assessment and containment measures.

Business Impact: High

Compensating Controls

No vendor patch currently available. Interim mitigations: (1) Enforce Mobile Device Management (MDM) policies to restrict sideloading and untrusted app sources; (2) Isolate affected devices to trusted networks only; (3) Disable or restrict processor-intensive or low-level system operations if available through device settings; (4) Implement network segmentation to limit lateral movement potential; (5) Monitor for exploitation indicators in device logs and network traffic; (6) Maintain heightened alert posture for any unusual device behavior; (7) Prepare for rapid patch deployment once Samsung releases firmware updates.

Threat Intelligence Overview

EPSS Score

0.1%

Top 72% exploitable

Data Quality

4 sources

Confidence: Medium

EUVD

NVD

CVE.org

EPSS

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity CRITICAL

CISA KEV No

Public POC No

EPSS 0.1%

Patch available No

Active threat No

Deciding rule

CRITICAL severity

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Scheduled

Exploitation· derived

None

System Exposure· derived

Open

Automatable· derived

Yes

Human Impact

High

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +46

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Buffer Overflow HIGH

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.