CVE-2025-62818 Vulnerability Analysis & Exploit Details

CVE-2025-62818
Vulnerability Scoring

9.8
/10
Critical Risk

As a catastrophic security flaw, CVE-2025-62818 has severe implications, demanding immediate intervention.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2025-62818 Details

Status: Analyzed

Last updated: 🕞 13 Apr 2026, 15:31 UTC
Originally published on: 🕒 07 Apr 2026, 15:17 UTC

Time between publication and last update: 6 days

CVSS Release: version 3

CVSS3 Source

134c704f-9b21-4f2e-91b3-4a467353bcc0

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2025-62818 Vulnerability Summary

CVE-2025-62818: An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 1580, 2500, 9110, W920, W930, W1000, Modem 5123, Modem 5300, and Modem 5400. An out-of-bounds write occurs due to a mismatch between the TP-UDHI and UDL values when processing an SMS TP-UD packet.

Assessing the Risk of CVE-2025-62818

Access Complexity Graph

The exploitability of CVE-2025-62818 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2025-62818

With low attack complexity and no required privileges, CVE-2025-62818 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2025-62818, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2025-62818, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2025-62818 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2025-62818 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2025-62818 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2025-62818 References

External References

CWE Common Weakness Enumeration

CWE-787

Vulnerable Configurations

  • cpe:2.3:o:samsung:exynos_990_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_990_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_990:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_990:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_980_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_980_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_980:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_980:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_850_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_850_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_850:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_850:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_1080_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_1080_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_1080:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_1080:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_1280_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_1280_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_1280:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_1280:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_1330_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_1330_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_1330:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_1330:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_1380_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_1380_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_1380:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_1380:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_1480_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_1480_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_1480:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_1480:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_1580_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_1580_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_1580:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_1580:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_9110_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_9110_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_9110:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_9110:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_2100_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_2100_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_2100:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_2100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_2200_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_2200_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_2200:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_2200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_2400_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_2400_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_2400:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_2400:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_2500_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_2500_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_2500:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_2500:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_w930_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_w930_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_w930:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_w930:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_w920_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_w920_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_w920:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_w920:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_w1000_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_w1000_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_w1000:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_w1000:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_modem_5400_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_modem_5400_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_modem_5400:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_modem_5400:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_modem_5300_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_modem_5300_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_modem_5300:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_modem_5300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:samsung:exynos_modem_5123_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:samsung:exynos_modem_5123_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:samsung:exynos_modem_5123:-:*:*:*:*:*:*:*
    cpe:2.3:h:samsung:exynos_modem_5123:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-62818: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-6193 – A security flaw has been discovered in PHPGurukul Daily Expense Tracking System 1.1. Affected is an unknown function of the file /register.php. The...
  • CVE-2026-6192 – A vulnerability was identified in uclouvain openjpeg up to 2.5.4. This impacts the function opj_pi_initialise_encode in the library src/lib/openjp2...
  • CVE-2026-6191 – A vulnerability was determined in itsourcecode Construction Management System 1.0. This affects an unknown function of the file /equipments.php. Ex...
  • CVE-2026-6190 – A vulnerability was found in itsourcecode Construction Management System 1.0. The impacted element is an unknown function of the file /employees.ph...
  • CVE-2026-6189 – A vulnerability has been found in SourceCodester Pharmacy Sales and Inventory System 1.0. The affected element is an unknown function of the file /...