CVE-2025-62526 Vulnerability Analysis & Exploit Details

CVE-2025-62526
Vulnerability Scoring

7.9
/10
Very High Risk

Highly exploitable, CVE-2025-62526 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2025-62526 Details

Status: Analyzed

Last updated: 🕔 30 Oct 2025, 17:21 UTC
Originally published on: 🕒 22 Oct 2025, 15:16 UTC

Time between publication and last update: 8 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2025-62526 Vulnerability Summary

CVE-2025-62526: OpenWrt Project is a Linux operating system targeting embedded devices. Prior to version 24.10.4, ubusd contains a heap buffer overflow in the event registration parsing code. This allows an attacker to modify the head and potentially execute arbitrary code in the context of the ubus daemon. The affected code is executed before running the ACL checks, all ubus clients are able to send such messages. In addition to the heap corruption, the crafted subscription also results in a bypass of the listen ACL. This is fixed in OpenWrt 24.10.4. There are no workarounds.

Assessing the Risk of CVE-2025-62526

Access Complexity Graph

The exploitability of CVE-2025-62526 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-62526

CVE-2025-62526 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

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-62526, 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-62526, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2025-62526 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2025-62526 may cause minor changes to data without severely impacting its accuracy.
  • Availability: High
    CVE-2025-62526 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2025-62526 References

External References

CWE Common Weakness Enumeration

CWE-122

CAPEC Common Attack Pattern Enumeration and Classification

  • Forced Integer Overflow CAPEC-92 This attack forces an integer variable to go out of range. The integer variable is often used as an offset such as size of memory allocation or similarly. The attacker would typically control the value of such variable and try to get it out of range. For instance the integer in question is incremented past the maximum possible value, it may wrap to become a very small, or negative number, therefore providing a very incorrect value which can lead to unexpected behavior. At worst the attacker can execute arbitrary code.

Vulnerable Configurations

  • cpe:2.3:o:openwrt:openwrt:-:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:-:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:15.05.1:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:15.05.1:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:17.01.0:-:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:17.01.0:-:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:17.01.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:17.01.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:17.01.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:17.01.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:17.01.1:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:17.01.1:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:17.01.2:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:17.01.2:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:17.01.3:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:17.01.3:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:17.01.4:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:17.01.4:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:17.01.5:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:17.01.5:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:17.01.6:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:17.01.6:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:17.01.7:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:17.01.7:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:18.06.0:-:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:18.06.0:-:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:18.06.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:18.06.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:18.06.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:18.06.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:18.06.1:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:18.06.1:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:18.06.2:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:18.06.2:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:18.06.3:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:18.06.3:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:18.06.4:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:18.06.4:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:18.06.5:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:18.06.5:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:18.06.6:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:18.06.6:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:18.06.7:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:18.06.7:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:18.06.8:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:18.06.8:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:18.06.9:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:18.06.9:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:19.07.0:-:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:19.07.0:-:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:19.07.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:19.07.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:19.07.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:19.07.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:19.07.1:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:19.07.1:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:19.07.2:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:19.07.2:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:19.07.3:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:19.07.3:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:19.07.4:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:19.07.4:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:19.07.5:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:19.07.5:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:19.07.6:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:19.07.6:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:19.07.7:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:19.07.7:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:19.07.8:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:19.07.8:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:19.07.9:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:19.07.9:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:19.07.10:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:19.07.10:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:21.02:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:21.02:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:21.02.0:-:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:21.02.0:-:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:21.02.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:21.02.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:21.02.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:21.02.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:21.02.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:21.02.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:21.02.0:rc4:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:21.02.0:rc4:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:21.02.1:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:21.02.1:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:21.02.2:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:21.02.2:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:21.02.3:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:21.02.3:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:21.02.4:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:21.02.4:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:21.02.5:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:21.02.5:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:21.02.6:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:21.02.6:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:21.02.7:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:21.02.7:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:22.03.0:-:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:22.03.0:-:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:22.03.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:22.03.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:22.03.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:22.03.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:22.03.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:22.03.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:22.03.0:rc4:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:22.03.0:rc4:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:22.03.0:rc5:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:22.03.0:rc5:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:22.03.0:rc6:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:22.03.0:rc6:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:22.03.1:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:22.03.1:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:22.03.2:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:22.03.2:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:22.03.3:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:22.03.3:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:22.03.4:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:22.03.4:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:22.03.5:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:22.03.5:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:22.03.6:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:22.03.6:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:22.03.7:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:22.03.7:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:23.05.0:-:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:23.05.0:-:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:23.05.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:23.05.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:23.05.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:23.05.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:23.05.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:23.05.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:23.05.0:rc4:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:23.05.0:rc4:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:23.05.1:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:23.05.1:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:23.05.2:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:23.05.2:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:23.05.3:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:23.05.3:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:23.05.4:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:23.05.4:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:23.05.5:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:23.05.5:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:23.05.6:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:23.05.6:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:24.10.0:-:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:24.10.0:-:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:24.10.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:24.10.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:24.10.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:24.10.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:24.10.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:24.10.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:24.10.0:rc4:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:24.10.0:rc4:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:24.10.0:rc5:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:24.10.0:rc5:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:24.10.0:rc6:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:24.10.0:rc6:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:24.10.0:rc7:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:24.10.0:rc7:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:24.10.1:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:24.10.1:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:24.10.2:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:24.10.2:*:*:*:*:*:*:*
  • cpe:2.3:o:openwrt:openwrt:24.10.3:*:*:*:*:*:*:*
    cpe:2.3:o:openwrt:openwrt:24.10.3:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-62526: 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-2025-13735 – Out-of-bounds Read vulnerability in ASR1903、ASR3901 in ASR Lapwing_Linux on Linux (nr_fw modules). This vulnerability is associated with program fi...
  • CVE-2025-9558 – There is a potential OOB Write vulnerability in the gen_prov_start function in pb_adv.c. The full length of the received data is copied into the li...
  • CVE-2025-9557 – ‭An out-of-bound write can lead to an arbitrary code execution. Even on devices with some form of memory protection, this can still lead to‬ ‭a cra...
  • CVE-2025-59820 – In KDE Krita before 5.2.13, loading a manipulated TGA file could result in a heap-based buffer overflow in plugins/impex/tga/kis_tga_import.cpp (ak...
  • CVE-2025-55174 – In KDE Skanpage before 25.08.0, an attempt at file overwrite can result in the contents of the new file at the beginning followed by the partial co...