CVE-2026-34510 Vulnerability Analysis & Exploit Details

CVE-2026-34510
Vulnerability Scoring

5.3
/10
Significant Risk

Security assessments indicate that CVE-2026-34510 presents a notable risk, potentially requiring prompt mitigation.

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-2026-34510 Details

Status: Analyzed

Last updated: 🕖 07 Apr 2026, 19:21 UTC
Originally published on: 🕓 01 Apr 2026, 16:23 UTC

Time between publication and last update: 6 days

CVSS Release: version 3

CVSS3 Source

disclosure@vulncheck.com

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2026-34510 Vulnerability Summary

CVE-2026-34510: OpenClaw before 2026.3.22 contains a path traversal vulnerability in Windows media loaders that accepts remote-host file URLs and UNC-style paths before local-path validation. Attackers can exploit this by providing network-hosted file targets that are treated as local content, bypassing intended access restrictions.

Assessing the Risk of CVE-2026-34510

Access Complexity Graph

The exploitability of CVE-2026-34510 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-2026-34510

With low attack complexity and no required privileges, CVE-2026-34510 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-2026-34510, 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-2026-34510, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2026-34510 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: None
    CVE-2026-34510 poses no threat to data integrity.
  • Availability: None
    CVE-2026-34510 does not impact system availability.

CVE-2026-34510 References

External References

CWE Common Weakness Enumeration

CWE-41

CAPEC Common Attack Pattern Enumeration and Classification

  • Using Leading 'Ghost' Character Sequences to Bypass Input Filters CAPEC-3 Some APIs will strip certain leading characters from a string of parameters. An adversary can intentionally introduce leading "ghost" characters (extra characters that don't affect the validity of the request at the API layer) that enable the input to pass the filters and therefore process the adversary's input. This occurs when the targeted API will accept input data in several syntactic forms and interpret it in the equivalent semantic way, while the filter does not take into account the full spectrum of the syntactic forms acceptable to the targeted API.

Vulnerable Configurations

  • cpe:2.3:a:openclaw:openclaw:0.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:0.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:0.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:0.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:0.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:0.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:0.1.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:0.1.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:1.0.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:1.0.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:1.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:1.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:1.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:1.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:1.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:1.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:1.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:1.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:1.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:1.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2.0.0:beta1:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2.0.0:beta1:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2.0.0:beta2:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2.0.0:beta2:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2.0.0:beta3:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2.0.0:beta3:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2.0.0:beta4:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2.0.0:beta4:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2.0.0:beta5:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2.0.0:beta5:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.11-1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.11-1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.11-2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.11-2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.11-3:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.11-3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.12-2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.12-2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.14-1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.14-1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.16-2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.16-2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.24-1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.24-1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.5-1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.5-1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.5-2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.5-2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.5-3:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.5-3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.11:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.11:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.12:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.12:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.13:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.13:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.15:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.15:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.20:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.20:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.21:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.21:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.22:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.22:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.23:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.23:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.24:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.24:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.29:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.29:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.30:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.30:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.2.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.2.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.2.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.2.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.2.6-1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.2.6-1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.2.6-2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.2.6-2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.2.6-3:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.2.6-3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.2.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.2.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.2.12:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.2.12:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.2.13:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.2.13:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.2.14:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.2.14:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.2.15:-:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.2.15:-:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.2.15:beta1:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.2.15:beta1:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.2.17:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.2.17:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.2.19:beta1:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.2.19:beta1:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2026-34510: 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-8198 – The Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity plugin for WordPress is vulnerable to Authentication Bypass to Inf...
  • CVE-2026-8186 – A vulnerability was detected in Open5GS up to 2.7.7. This affects the function ogs_sbi_client_send_via_scp_or_sepp in the library lib/sbi/client.c ...
  • CVE-2026-8187 – A flaw has been found in Open5GS up to 2.7.7. This impacts the function _gtpv1_u_recv_cb of the file src/upf/gtp-path.c of the component UPF. Execu...
  • CVE-2026-8185 – A security vulnerability has been detected in UGREEN CM933 1.1.59.4319. The impacted element is an unknown function of the component Administrative...
  • CVE-2026-3828 – Some Hikvision switch products (discontinued since December 2023) are vulnerable to authenticated remote command execution due to insufficient inpu...