CVE-2025-35451 Vulnerability Analysis & Exploit Details

CVE-2025-35451
Vulnerability Scoring

9.8
/10
Critical Risk

As a catastrophic security flaw, CVE-2025-35451 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-35451 Details

Status: Analyzed

Last updated: 🕞 14 Jan 2026, 15:33 UTC
Originally published on: 🕕 05 Sep 2025, 18:15 UTC

Time between publication and last update: 130 days

CVSS Release: version 3

CVSS3 Source

9119a7d8-5eab-497f-8521-727c672e3725

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-35451 Vulnerability Summary

CVE-2025-35451: PTZOptics and possibly other ValueHD-based pan-tilt-zoom cameras use hard-coded, default administrative credentials. The passwords can readily be cracked. Many cameras have SSH or telnet listening on all interfaces. The passwords cannot be changed by the user, nor can the SSH or telnet service be disabled by the user.

Assessing the Risk of CVE-2025-35451

Access Complexity Graph

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

With low attack complexity and no required privileges, CVE-2025-35451 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-35451, 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-35451, 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-35451 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2025-35451 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2025-35451 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2025-35451 References

External References

CWE Common Weakness Enumeration

CWE-798

CAPEC Common Attack Pattern Enumeration and Classification

  • Read Sensitive Constants Within an Executable CAPEC-191 An adversary engages in activities to discover any sensitive constants present within the compiled code of an executable. These constants may include literal ASCII strings within the file itself, or possibly strings hard-coded into particular routines that can be revealed by code refactoring methods including static and dynamic analysis.
  • Try Common or Default Usernames and Passwords CAPEC-70 An adversary may try certain common or default usernames and passwords to gain access into the system and perform unauthorized actions. An adversary may try an intelligent brute force using empty passwords, known vendor default credentials, as well as a dictionary of common usernames and passwords. Many vendor products come preconfigured with default (and thus well-known) usernames and passwords that should be deleted prior to usage in a production environment. It is a common mistake to forget to remove these default login credentials. Another problem is that users would pick very simple (common) passwords (e.g. "secret" or "password") that make it easier for the attacker to gain access to the system compared to using a brute force attack or even a dictionary attack using a full dictionary.

Vulnerable Configurations

  • cpe:2.3:o:ptzoptics:pt12x-sdi-xx-g2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt12x-sdi-xx-g2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pt12x-sdi-xx-g2_firmware:6.3.34:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt12x-sdi-xx-g2_firmware:6.3.34:*:*:*:*:*:*:*
  • cpe:2.3:h:ptzoptics:pt12x-sdi-xx-g2:-:*:*:*:*:*:*:*
    cpe:2.3:h:ptzoptics:pt12x-sdi-xx-g2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pt12x-ndi-xx_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt12x-ndi-xx_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pt12x-ndi-xx_firmware:6.3.34:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt12x-ndi-xx_firmware:6.3.34:*:*:*:*:*:*:*
  • cpe:2.3:h:ptzoptics:pt12x-ndi-xx:-:*:*:*:*:*:*:*
    cpe:2.3:h:ptzoptics:pt12x-ndi-xx:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pt12x-usb-xx-g2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt12x-usb-xx-g2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pt12x-usb-xx-g2_firmware:6.2.81:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt12x-usb-xx-g2_firmware:6.2.81:*:*:*:*:*:*:*
  • cpe:2.3:h:ptzoptics:pt12x-usb-xx-g2:-:*:*:*:*:*:*:*
    cpe:2.3:h:ptzoptics:pt12x-usb-xx-g2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pt20x-sdi-xx-g2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt20x-sdi-xx-g2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pt20x-sdi-xx-g2_firmware:6.3.20:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt20x-sdi-xx-g2_firmware:6.3.20:*:*:*:*:*:*:*
  • cpe:2.3:h:ptzoptics:pt20x-sdi-xx-g2:-:*:*:*:*:*:*:*
    cpe:2.3:h:ptzoptics:pt20x-sdi-xx-g2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pt20x-ndi-xx_firmware:6.3.20:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt20x-ndi-xx_firmware:6.3.20:*:*:*:*:*:*:*
  • cpe:2.3:h:ptzoptics:pt20x-ndi-xx:-:*:*:*:*:*:*:*
    cpe:2.3:h:ptzoptics:pt20x-ndi-xx:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pt20x-usb-xx-g2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt20x-usb-xx-g2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pt20x-usb-xx-g2_firmware:6.2.73:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt20x-usb-xx-g2_firmware:6.2.73:*:*:*:*:*:*:*
  • cpe:2.3:h:ptzoptics:pt20x-usb-xx-g2:-:*:*:*:*:*:*:*
    cpe:2.3:h:ptzoptics:pt20x-usb-xx-g2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pt30x-sdi-xx-g2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt30x-sdi-xx-g2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pt30x-sdi-xx-g2_firmware:6.3.30:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt30x-sdi-xx-g2_firmware:6.3.30:*:*:*:*:*:*:*
  • cpe:2.3:h:ptzoptics:pt30x-sdi-xx-g2:-:*:*:*:*:*:*:*
    cpe:2.3:h:ptzoptics:pt30x-sdi-xx-g2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pt30x-ndi-xx_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt30x-ndi-xx_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pt30x-ndi-xx_firmware:6.3.30:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt30x-ndi-xx_firmware:6.3.30:*:*:*:*:*:*:*
  • cpe:2.3:h:ptzoptics:pt30x-ndi-xx:-:*:*:*:*:*:*:*
    cpe:2.3:h:ptzoptics:pt30x-ndi-xx:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pt12x-zcam_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt12x-zcam_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pt12x-zcam_firmware:7.2.76:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt12x-zcam_firmware:7.2.76:*:*:*:*:*:*:*
  • cpe:2.3:h:ptzoptics:pt12x-zcam:-:*:*:*:*:*:*:*
    cpe:2.3:h:ptzoptics:pt12x-zcam:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pt20x-zcam_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt20x-zcam_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pt20x-zcam_firmware:7.2.82:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pt20x-zcam_firmware:7.2.82:*:*:*:*:*:*:*
  • cpe:2.3:h:ptzoptics:pt20x-zcam:-:*:*:*:*:*:*:*
    cpe:2.3:h:ptzoptics:pt20x-zcam:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:ptvl-zcam_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:ptvl-zcam_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:ptvl-zcam_firmware:7.2.79:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:ptvl-zcam_firmware:7.2.79:*:*:*:*:*:*:*
  • cpe:2.3:h:ptzoptics:ptvl-zcam:-:*:*:*:*:*:*:*
    cpe:2.3:h:ptzoptics:ptvl-zcam:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pteptz-zcam-g2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pteptz-zcam-g2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pteptz-zcam-g2_firmware:8.1.81:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pteptz-zcam-g2_firmware:8.1.81:*:*:*:*:*:*:*
  • cpe:2.3:h:ptzoptics:pteptz-zcam-g2:-:*:*:*:*:*:*:*
    cpe:2.3:h:ptzoptics:pteptz-zcam-g2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:pteptz-ndi-zcam-g2_firmware:8.1.81:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:pteptz-ndi-zcam-g2_firmware:8.1.81:*:*:*:*:*:*:*
  • cpe:2.3:h:ptzoptics:pteptz-ndi-zcam-g2:-:*:*:*:*:*:*:*
    cpe:2.3:h:ptzoptics:pteptz-ndi-zcam-g2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:vl_fixed_camera_firmware:7.2.94:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:vl_fixed_camera_firmware:7.2.94:*:*:*:*:*:*:*
  • cpe:2.3:h:ptzoptics:vl_fixed_camera:-:*:*:*:*:*:*:*
    cpe:2.3:h:ptzoptics:vl_fixed_camera:-:*:*:*:*:*:*:*
  • cpe:2.3:o:ptzoptics:ndi_fixed_camera_firmware:7.2.94:*:*:*:*:*:*:*
    cpe:2.3:o:ptzoptics:ndi_fixed_camera_firmware:7.2.94:*:*:*:*:*:*:*
  • cpe:2.3:h:ptzoptics:ndi_fixed_camera:-:*:*:*:*:*:*:*
    cpe:2.3:h:ptzoptics:ndi_fixed_camera:-:*:*:*:*:*:*:*
  • cpe:2.3:o:multicam-systems:mcamii_ptz_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:multicam-systems:mcamii_ptz_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:multicam-systems:mcamii_ptz:*:*:*:*:*:*:*:*
    cpe:2.3:h:multicam-systems:mcamii_ptz:*:*:*:*:*:*:*:*
  • cpe:2.3:o:smtav:ba30s_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:smtav:ba30s_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:smtav:ba30s:*:*:*:*:*:*:*:*
    cpe:2.3:h:smtav:ba30s:*:*:*:*:*:*:*:*
  • cpe:2.3:o:smtav:ba20s_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:smtav:ba20s_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:smtav:ba20s:*:*:*:*:*:*:*:*
    cpe:2.3:h:smtav:ba20s:*:*:*:*:*:*:*:*
  • cpe:2.3:o:smtav:bv20s_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:smtav:bv20s_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:smtav:bv20s:*:*:*:*:*:*:*:*
    cpe:2.3:h:smtav:bv20s:*:*:*:*:*:*:*:*
  • cpe:2.3:o:smtav:bx30s_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:smtav:bx30s_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:smtav:bx30s:*:*:*:*:*:*:*:*
    cpe:2.3:h:smtav:bx30s:*:*:*:*:*:*:*:*
  • cpe:2.3:o:smtav:bx20n_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:smtav:bx20n_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:smtav:bx20n:*:*:*:*:*:*:*:*
    cpe:2.3:h:smtav:bx20n:*:*:*:*:*:*:*:*
  • cpe:2.3:o:smtav:bx20uhd-n_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:smtav:bx20uhd-n_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:smtav:bx20uhd-n:*:*:*:*:*:*:*:*
    cpe:2.3:h:smtav:bx20uhd-n:*:*:*:*:*:*:*:*
  • cpe:2.3:o:smtav:bx20uhd_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:smtav:bx20uhd_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:smtav:bx20uhd:*:*:*:*:*:*:*:*
    cpe:2.3:h:smtav:bx20uhd:*:*:*:*:*:*:*:*
  • cpe:2.3:o:smtav:ba30-n_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:smtav:ba30-n_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:smtav:ba30-n:*:*:*:*:*:*:*:*
    cpe:2.3:h:smtav:ba30-n:*:*:*:*:*:*:*:*
  • cpe:2.3:o:smtav:ba20-n_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:smtav:ba20-n_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:smtav:ba20-n:*:*:*:*:*:*:*:*
    cpe:2.3:h:smtav:ba20-n:*:*:*:*:*:*:*:*
  • cpe:2.3:o:smtav:ba12-n_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:smtav:ba12-n_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:smtav:ba12-n:*:*:*:*:*:*:*:*
    cpe:2.3:h:smtav:ba12-n:*:*:*:*:*:*:*:*
  • cpe:2.3:o:smtav:hd17h-n_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:smtav:hd17h-n_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:smtav:hd17h-n:*:*:*:*:*:*:*:*
    cpe:2.3:h:smtav:hd17h-n:*:*:*:*:*:*:*:*
  • cpe:2.3:o:smtav:bx20s-sh_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:smtav:bx20s-sh_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:smtav:bx20s-sh:*:*:*:*:*:*:*:*
    cpe:2.3:h:smtav:bx20s-sh:*:*:*:*:*:*:*:*
  • cpe:2.3:o:smtav:hd17h_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:smtav:hd17h_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:smtav:hd17h:*:*:*:*:*:*:*:*
    cpe:2.3:h:smtav:hd17h:*:*:*:*:*:*:*:*
  • cpe:2.3:o:smtav:bv30s_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:smtav:bv30s_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:smtav:bv30s:*:*:*:*:*:*:*:*
    cpe:2.3:h:smtav:bv30s:*:*:*:*:*:*:*:*
  • cpe:2.3:o:smtav:ba12s_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:smtav:ba12s_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:smtav:ba12s:*:*:*:*:*:*:*:*
    cpe:2.3:h:smtav:ba12s:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:vx90_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:vx90_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:vx90:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:vx90:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:vx720l_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:vx720l_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:vx720l:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:vx720l:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:vx752ag_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:vx752ag_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:vx752ag:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:vx752ag:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:vx752a_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:vx752a_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:vx752a:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:vx752a:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:vx751ba_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:vx751ba_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:vx751ba:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:vx751ba:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:vx630al_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:vx630al_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:vx630al:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:vx630al:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:vx61asl_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:vx61asl_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:vx61asl:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:vx61asl:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:vx61basl_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:vx61basl_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:vx61basl:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:vx61basl:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:vx60asl_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:vx60asl_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:vx60asl:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:vx60asl:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:vx61al_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:vx61al_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:vx61al:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:vx61al:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:vx60al_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:vx60al_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:vx60al:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:vx60al:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:vx701ra_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:vx701ra_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:vx701ra:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:vx701ra:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:vx701ta_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:vx701ta_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:vx701ta:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:vx701ta:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:vx800i2_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:vx800i2_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:vx800i2:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:vx800i2:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:v61w_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:v61w_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:v61w:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:v61w:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:v63xl_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:v63xl_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:v63xl:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:v63xl:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:v60xl_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:v60xl_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:v60xl:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:v60xl:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:vx70uvs_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:vx70uvs_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:vx70uvs:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:vx70uvs:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:vx71uvs_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:vx71uvs_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:vx71uvs:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:vx71uvs:*:*:*:*:*:*:*:*
  • cpe:2.3:o:valuehd:v71uvs_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:valuehd:v71uvs_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:valuehd:v71uvs:*:*:*:*:*:*:*:*
    cpe:2.3:h:valuehd:v71uvs:*:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2025-35451: 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-23039 – In the Linux kernel, the following vulnerability has been resolved: drm/gud: fix NULL fb and crtc dereferences on USB disconnect On disconnect dr...
  • CVE-2026-23038 – In the Linux kernel, the following vulnerability has been resolved: pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node() In nfs4_ff_a...
  • CVE-2026-23037 – In the Linux kernel, the following vulnerability has been resolved: can: etas_es58x: allow partial RX URB allocation to succeed When es58x_alloc_...
  • CVE-2026-23036 – In the Linux kernel, the following vulnerability has been resolved: btrfs: release path before iget_failed() in btrfs_read_locked_inode() In btrf...
  • CVE-2026-23035 – In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv mlx5e_priv is ...