NetSight

Security Dashboard

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

Reset
86 matching advisories · page 1 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.4 CVE-2026-67105 HCL BigFix Service Management is affected by an Insecure Communication vulnerability, which could allow an attacker with internal network access to intercept u… hcltech · bigfix_service_management 51 days ago high7.2 CVE-2026-56589 HCL BigFix Service Management is affected by a Stored Cross-Site Scripting (XSS) vulnerability, which could allow an attacker to inject and store malicious scr… hcltech · bigfix_service_management 51 days ago high7.6 CVE-2026-67103 HCL BigFix Service Management is affected by Cross-Site Scripting (XSS) vulnerability, which could allow an attacker to inject unsanitized malicious scripts th… hcltech · bigfix_service_management 2026-09-18 high8.1 CVE-2026-67102 HCL BigFix Service Management is affected by a high-severity Broken Access Control vulnerability, which could allow a low-privileged user to gain unauthorized … hcltech · bigfix_service_management 2026-09-18 high7.5 CVE-2023-37507 HCL DevOps Plan is susceptible to an information disclosure that can allow an attacker to focus their attacks based upon the information revealed. hcltech · devops_plan 2026-07-21 high8.2 CVE-2026-35149 HCL DFXServer is affected by an Authentication Bypass vulnerability via server response manipulation. hcltech · dfx_server 2026-07-16 high8.2 CVE-2026-35147 HCL DFXServer is affected by a Broken Authentication vulnerability via direct API access. hcltech · dfx_server 2026-07-16 high7.7 CVE-2023-37524 HCL Traveler for Microsoft Outlook (HTMO) is susceptible to vulnerabilities due to .NET Framework 4.5 being out of service. hcltech · traveler_for_microsoft_outlook 2026-06-27 high8.8 CVE-2026-21837 HCL Digital Experience is affected by an OS command injection vulnerability in the Digital Asset Management API. hcltech · digital_experience, hcltech · digital_experience_compose 2026-06-05 high7.1 CVE-2025-52612 HCL iControl was affected by Export CSV - CSV Injection vulnerability. hcltech · icontrol 2026-06-04 high8.3 CVE-2024-30151 HCL BigFix Service Management (SX) is affected by a Broken Access Control vulnerability leading to privilege escalation. hcltech · bigfix_service_management 2026-05-06 high8.8 CVE-2026-21765 HCL BigFix Platform is affected by insecure permissions on private cryptographic keys. hcltech · bigfix_platform 2026-04-02 high7.3 CVE-2025-55263 HCL Aftermarket DPC is affected by Hardcoded Sensitive Data which allows attacker to gain access to the source code or if it is stored in insecure repositories… hcltech · aftermarket_cloud 2026-03-26 high8.3 CVE-2025-55262 HCL Aftermarket DPC is affected by SQL Injection which allows attacker to exploit this vulnerability to retrieve sensitive information from the database. hcltech · aftermarket_cloud 2026-03-26 high8.1 CVE-2025-55261 HCL Aftermarket DPC is affected by Missing Functional Level Access Control which will allow attacker to escalate his privileges and may compromise the applicat… hcltech · aftermarket_cloud 2026-03-26 high7.6 CVE-2024-42210 A Stored cross-site scripting (XSS) vulnerability affects HCL Unica Marketing Operations v12.1.8 and lower. hcltech · unica 2026-03-19 high7.4 CVE-2025-59870 HCL MyXalytics is affected by improper management of a static JWT signing secret in the web application, where the secret lacks rotation , introducing a securi… hcltech · myxalytics 2026-01-16 high7.5 CVE-2025-51735 CSV formula injection vulnerability in HCL Technologies Ltd. hcltech · unica 2025-11-28 high8.2 CVE-2025-52650 Inline script execution allowed in CSP vulnerability has been identified in HCL AION v2.0 hcltech · aion 2025-10-10 high7.6 CVE-2025-52656 HCL MyXalytics: 6.6. hcltech · dryice_myxalytics 2025-10-03 high7.6 CVE-2025-52653 HCL MyXalytics product is affected by Cross Site Scripting vulnerability in the web application. hcltech · dryice_myxalytics 2025-10-03 high7.6 CVE-2025-31955 HCL iAutomate is affected by a sensitive data exposure vulnerability. hcltech · dryice_iautomate 2025-07-24 high7.1 CVE-2025-31953 HCL iAutomate includes hardcoded credentials which may result in potential exposure of confidential data if intercepted or accessed by unauthorized parties. hcltech · dryice_iautomate 2025-07-24 high7.1 CVE-2025-31952 HCL iAutomate is affected by an insufficient session expiration. hcltech · dryice_iautomate 2025-07-24 high7.1 CVE-2023-37535 Insufficient URI protocol whitelist in HCL Domino Volt and Domino Leap allow script injection through query parameters. hcltech · domino_leap 2025-04-30 high7.1 CVE-2023-37534 Insufficient URI protocol whitelist in HCL Leap allows script injection through query parameters. hcltech · hcl_leap 2025-04-24 high8.1 CVE-2024-42193 HCL BigFix Web Reports' service communicates over HTTPS but exhibits a weakness in its handling of SSL certificate validation. hcltech · bigfix_platform 2025-04-15 high7.2 CVE-2025-0255 HCL DevOps Deploy / HCL Launch could allow a remote privileged authenticated attacker to execute arbitrary commands on the system by sending specially crafted … hcltechsw · hcl_devops_deploy, hcltechsw · hcl_launch 2025-03-24 high7.1 CVE-2024-42169 HCL MyXalytics is affected by insecure direct object references. hcltech · dryice_myxalytics 2025-01-11 high8.9 CVE-2024-42168 HCL MyXalytics is affected by out-of-band resource load (HTTP) vulnerability. hcltech · dryice_myxalytics 2025-01-11

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.