CVE-2025-69274VulnerabilityPublished 12 Jan 2026

CVE-2025-69274: Broadcom DX NetOps Spectrum · Insecure Direct Object Reference

Affects Broadcom DX NetOps SpectrumSource CVE Database V5

Not known to be exploited · CVSS 2.3 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

2.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: Low
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
BroadcomDX NetOps Spectrum	Affected =24.3.10 and earlier	Fixed in–

AI-suggested

European organizations should implement the following specific mitigations: 1) Conduct an immediate audit of user privileges within DX NetOps Spectrum to ensure least privilege principles are enforced, limiting access to trusted administrators only. 2) Monitor logs and network activity for unusual access patterns or privilege escalations related to DX NetOps Spectrum. 3) Restrict network access to the DX NetOps Spectrum management interfaces using network segmentation and firewall rules to reduce exposure. 4) Engage with Broadcom support to obtain information on patch availability and apply updates promptly once released. 5) Implement compensating controls such as multi-factor authentication for administrative access to the product. 6) Review and harden configuration settings related to authorization keys or tokens within the product. 7) Prepare incident response plans specific to potential misuse of network management tools. These steps go beyond generic advice by focusing on privilege auditing, access restriction, and proactive monitoring tailored to the nature of this vulnerability.

Description

CVE-2025-69274 is an authorization bypass vulnerability in Broadcom DX NetOps Spectrum versions 24.3.10 and earlier. It allows a user with limited privileges to escalate their privileges by exploiting a user-controlled key that bypasses authorization checks. The vulnerability affects both Windows and Linux deployments of the product. Although the CVSS score is low (2.3), the issue could lead to unauthorized privilege escalation within affected environments. No known exploits are currently in the wild, and no patches have been linked yet. The vulnerability stems from CWE-639, which involves authorization bypass through improper validation of user-controlled keys. European organizations using DX NetOps Spectrum for network monitoring and management should be aware of this risk, especially those with complex network infrastructures.

Impact

For European organizations, the impact of CVE-2025-69274 primarily involves potential unauthorized privilege escalation within network monitoring and management environments. Since DX NetOps Spectrum is used to monitor and manage complex network infrastructures, an attacker exploiting this vulnerability could gain elevated privileges, potentially allowing them to manipulate network monitoring data, disable alerts, or interfere with network operations. This could lead to reduced visibility into network health, delayed incident response, and increased risk of further compromise. While the CVSS score is low, the strategic importance of network management tools means that even limited privilege escalation could have cascading effects on operational security. Critical sectors such as telecommunications, finance, energy, and government in Europe that rely on Broadcom’s network management solutions could face increased risk of targeted attacks aiming to disrupt or surveil network operations. The lack of known exploits reduces immediate risk, but the vulnerability should be addressed proactively to prevent future exploitation.

Summary

CVE-2025-69274 is an authorization bypass vulnerability categorized under CWE-639, affecting Broadcom DX NetOps Spectrum versions 24.3.10 and earlier on both Windows and Linux platforms. The vulnerability arises because the software improperly validates a user-controlled key, allowing an attacker with limited privileges to bypass authorization mechanisms and escalate their privileges within the system. This flaw could enable an attacker to gain unauthorized access to sensitive network management functions or data, potentially compromising the integrity and confidentiality of network operations. The vulnerability does not require user interaction and can be exploited remotely (AV:N), but it does require the attacker to have some level of privileges (PR:L) and authentication (AT:P). The CVSS 4.0 vector indicates low complexity (AC:L), no user interaction (UI:N), and no impact on confidentiality or availability, but a limited impact on integrity (VI:L) and scope (SI:L). No public exploits or patches are currently available, which suggests the vulnerability is newly disclosed and not yet actively exploited. The root cause is an improper authorization check that trusts a user-controlled key, a common issue in authorization bypass vulnerabilities. Organizations using DX NetOps Spectrum should prioritize assessing their exposure and prepare to deploy patches once Broadcom releases them.

CWE-639Authorization Bypass Through User-Controlled Key (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #24OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design · Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.1.2 (opens in a new tab)
V4.2.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/36756 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Jan 2026, 07:45 UTC

WeaknessesCWE-639

Technical details

References

Community reviews

Related threats