dbcve.org
Dx Netops SpectrumApplication · Broadcom

CVE-2025-69276

HIGH · 8.8 CVSS v3.1 Published 2026-01-12
Fix available
A fix is available. Upgrade to 25.4.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Deserialization of Untrusted Data vulnerability in Broadcom DX NetOps Spectrum on Windows, Linux allows Object Injection.This issue affects DX NetOps Spectrum: 24.3.13 and earlier.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A deserialization of untrusted data vulnerability (Java object injection) in Broadcom DX NetOps Spectrum allows remote attackers to execute arbitrary code by sending crafted serialized objects to affected installations. This is a well-established exploitation vector in Java applications where unsafe deserialization bypasses normal authentication controls.

MitigationUpgrade DX NetOps Spectrum to a version newer than 24.3.13. If immediate patching is not feasible, restrict network access to Spectrum management interfaces and implement web application firewall rules to detect deserialization payloads.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dx Netops SpectrumApplication
Affected:< 25.4.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Broadcom DX NetOps Spectrum is installed
    Look for the Spectrum installation directory on the server, typically under /opt/CA/Spectrum on Linux or C:\CA\Spectrum on Windows. Check for the 'Spectrum' application and associated services.
    Affected if The software is found on the system
  2. Determine the installed version of DX NetOps Spectrum
    Check the version file or use the Spectrum command-line tools. On Linux, look for a version file in the installation directory or run 'SpectrumVersion' if available. On Windows, check the installation properties or registry.
    Affected if The installed version is 24.3.13 or earlier, or any version below 25.4.1
  3. Check if the OneClick web interface is enabled and exposed
    The vulnerable deserialization occurs in server-side components. Verify if the OneClick web service (typically on port 8080 or 8443) is running and accessible. Check the status of the 'Spectrum Tomcat' or 'OneClick' service.
    Affected if The OneClick or web management interface is enabled and reachable on the network
  4. Verify if remote management access is allowed
    Review network configuration to determine if Spectrum management ports are open to untrusted networks. Check firewall rules and access control lists restricting access to Spectrum management interfaces.
    Affected if Management interfaces are exposed to networks outside the trusted internal network
  5. Confirm the vulnerability is in a reachable component
    The deserialization flaw is in the server-side processing of network management data. Review which Spectrum services are running and which accept remote connections for management operations.
    Affected if Services that handle serialized data for management operations are active and accessible

A system is affected if Broadcom DX NetOps Spectrum is installed with any version below 25.4.1 and the management interfaces are network-accessible, allowing unauthenticated attackers to send malicious serialized data to the server.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 25.4.1 or later
Fixed in 25.4.1
Interim mitigation

Upgrade DX NetOps Spectrum to a version newer than 24.3.13. If immediate patching is not feasible, restrict network access to Spectrum management interfaces and implement web application firewall rules to detect deserialization payloads.

Recommended fix High confidence

DX NetOps Spectrum 25.4.1 or later

  1. Obtain the DX NetOps Spectrum 25.4.1 (or later) installation package from the Broadcom Support Portal at support.broadcom.com
  2. Review the DX NetOps Spectrum upgrade documentation for version 25.4.1
  3. Ensure you have a complete backup of your current configuration and database
  4. Stop all Spectrum services on the target system(s) before upgrading
  5. Run the upgrade installer for version 25.4.1 or later
  6. Verify all services start correctly after upgrade
  7. Confirm the new version is running by checking the Spectrum version information
  8. Validate that the vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dx Netops Spectrum Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-69276 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-69276 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data