NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
905 matching advisories · page 1 of 31Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.7 CVE-2026-126558 OS Command Injection, Incomplete List of Disallowed Inputs vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Win… Broadcom · AutoSys Workload Automation 4 days ago medium4.8 CVE-2026-126557 Out-of-bounds Write vulnerability in Broadcom AutoSys Workload Automation (AutoSys engine (AE) native clients modules) on Windows, Linux allows Overflow Buffer… Broadcom · AutoSys Workload Automation 4 days ago medium5.1 CVE-2026-126556 Invocation of Process Using Visible Sensitive Information, Insufficiently Protected Credentials vulnerability in Broadcom AutoSys Workload Automation (AutoSys … Broadcom · AutoSys Workload Automation 4 days ago medium5.3 CVE-2026-126555 Missing Authorization, Hidden Functionality vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linux all… Broadcom · AutoSys Workload Automation 4 days ago critical9.3 CVE-2026-126553 Deserialization of Untrusted Data vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linux allows Object… Broadcom · AutoSys Workload Automation 4 days ago critical9.3 CVE-2026-126552 Missing Authentication for Critical Function, OS Command Injection vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules… Broadcom · AutoSys Workload Automation 4 days ago critical9.3 CVE-2026-126551 Use of Hard-coded Cryptographic Key vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linux allows Sess… Broadcom · AutoSys Workload Automation 4 days ago high8.6 CVE-2026-126550 Insertion of Sensitive Information into Log File, Insufficiently Protected Credentials vulnerability in Broadcom AutoSys Workload Automation (Workload Control … Broadcom · AutoSys Workload Automation 4 days ago medium5.1 CVE-2026-126549 Insertion of Sensitive Information into Log File vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linu… Broadcom · AutoSys Workload Automation 4 days ago high7.1 CVE-2026-126548 Server-Side Request Forgery (SSRF) vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linux allows Serve… Broadcom · AutoSys Workload Automation 4 days ago high7.8 CVE-2026-126547 Missing Authorization vulnerability in Broadcom AutoSys Workload Automation (Workload Control Center (WCC) modules) on Windows, Linux allows Accessing Function… Broadcom · AutoSys Workload Automation 4 days ago medium5.2 CVE-2026-78116 The Broadcom AFBR-S50 time-of-flight sensor driver double-completes an RTIO submission when sensor data evaluation fails. zephyrproject · zephyr 31 days ago high7.8 CVE-2026-87428 In Brocade ASCG before 3.5.0, a local unauthorized user on the ASCG VM who can issue a request to the SANnav host network namespace can extract stored manageme… broadcom · brocade_active_support_connectivity_gateway 44 days ago medium4.3 CVE-2026-87426 An unauthenticated network-based attacker can query specific internal management endpoints on Brocade ASCG versions before 3.5.0 to enumerate the configuration… broadcom · brocade_active_support_connectivity_gateway 44 days ago medium6.8 CVE-2026-87425 An unauthenticated remote attacker can modify the TLS client trust store in Brocade ASCG versions before 3.5.0. broadcom · brocade_active_support_connectivity_gateway 44 days ago high8.8 CVE-2026-87424 A vulnerability in the SupportLink API authentication component of Brocade ASCG versions prior to 3.5.0 allows an attacker to bypass authentication across depl… broadcom · brocade_active_support_connectivity_gateway 44 days ago high8.8 CVE-2026-85490 When Brocade ASCG before 3.5.0 processes support bundle archives ingested from remote compromised endpoints, the application fails to sanitize path traversal s… broadcom · brocade_active_support_connectivity_gateway 44 days ago high8.8 CVE-2026-85489 An authentication flaw exists in the Brocade ASCG administrative management service component. broadcom · brocade_active_support_connectivity_gateway 44 days ago high7.8 CVE-2026-85488 Brocade ASCG before 3.5.0 has a well-known Brocade default password embedded in a script distributed to every customer. broadcom · brocade_active_support_connectivity_gateway 44 days ago high8.8 CVE-2026-85487 A path traversal vulnerability exists in the HTTP service component of Brocade ASCG versions before 3.5.0. broadcom · brocade_active_support_connectivity_gateway 44 days ago high8.0 CVE-2026-85486 Brocade ASCG before 3.5.0 improperly processes user input by evaluating form data prior to validation. broadcom · brocade_active_support_connectivity_gateway 44 days ago high8.8 CVE-2026-85423 A vulnerability has been identified in the data collection service of Brocade ASCG versions before 3.5.0. broadcom · brocade_active_support_connectivity_gateway 44 days ago high7.8 CVE-2026-85422 A vulnerability in Brocade ASCG version before 3.5.0 could allow an attacker to obtain a static cryptographic key hardcoded into the software binaries to secur… broadcom · brocade_active_support_connectivity_gateway 44 days ago high8.8 CVE-2026-85421 A critical security vulnerability has been identified in Brocade ASCG versions before 3.5.0. broadcom · brocade_active_support_connectivity_gateway 44 days ago medium4.1 CVE-2026-5769 A vulnerability in Brocade SANnav before 3.0.1 can have the Brocade Fabric OS switch admin password captured in plaintext within a memory swap file on the serv… broadcom · brocade_sannav 44 days ago medium5.7 CVE-2026-5049 A path traversal vulnerability affects the The Zone Alias Import flow feature in Brocade SANnav before 3.0.0a. broadcom · brocade_sannav 44 days ago high8.0 CVE-2026-5048 In Brocade SANnav before 3.0.0a, an SQL Injection vulnerability in various external API inventories have a vulnerability that allows an authenticated attacker … broadcom · brocade_sannav 44 days ago medium5.7 CVE-2026-5047 A vulnerability in Brocade SANnav before 2.4.0b and 3.0.0 prints encoded passwords and authentication tokens in log files. broadcom · brocade_sannav 44 days ago medium4.5 CVE-2026-94587 A buffer overflow vulnerability exists in the WebTools administrative interface handling configuration download or file transfer operations of Brocade Fabric O… broadcom · fabric_operating_system 44 days ago medium6.8 CVE-2026-94586 A command injection vulnerability exists in the WebTools administrative interface handling configuration download or file transfer operations of Brocade Fabric… broadcom · fabric_operating_system 44 days ago

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.