NetSight

Security Dashboard

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

Reset
156 matching advisories · page 2 of 6Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low2.6 CVE-2026-35141 HCL DFXAnalytics is affected by a Login Replay Attack vulnerability. hcltech · dfxanalytics 2026-07-16 low3.0 CVE-2026-35140 HCL DFXAnalytics is affected by a Missing Secure Attribute in Encrypted Session (SSL) Cookie vulnerability. hcltech · dfxanalytics 2026-07-16 low3.1 CVE-2025-62340 HCL iControl was affected by Inadequate Session Timeout vulnerability. hcltech · icontrol 2026-06-17 low3.1 CVE-2025-52611 HCL iControl v4.0.0 was affected by Unhandled Exception - Stack Trace Disclosure vulnerability. hcltech · icontrol 2026-06-04 low3.7 CVE-2025-52609 HCL iControl was affected by Missing Security Headers vulnerability. hcltech · icontrol 2026-06-04 low3.1 CVE-2025-52608 HCL iControl was affected by Missing Cookie Attributes vulnerability. hcltech · icontrol 2026-06-04 low3.7 CVE-2025-31985 HCL BigFix Service Management (SM) is affected by a security misconfiguration due to a missing or insecure “X-Content-Type-Options” header. hcltech · bigfix_service_management 2026-05-20 low3.9 CVE-2025-31974 HCL BigFix Service Management (SM) is susceptible to a Root File System Not Mounted as Read-Only. hcltech · bigfix_service_management 2026-05-06 low3.7 CVE-2025-31984 HCL BigFix Service Management (SM) is affected by a security misconfiguration due to a missing or insecure “X-Content-Type-Options” header. hcltech · bigfix_service_management 2026-05-06 low3.7 CVE-2025-31983 HCL BigFix Service Management (SM) is affected by a security misconfiguration vulnerability due to CSP header. hcltech · bigfix_service_management 2026-05-06 low3.7 CVE-2025-31982 HCL BigFix Service Management (SM) had directories that were not linked or publicly visible but could be accessed directly. hcltech · bigfix_service_management 2026-05-06 low2.6 CVE-2025-31975 HCL BigFix Service Management (SM) is affected by an Information Disclosure – Server Banner issue was identified. hcltech · bigfix_service_management 2026-05-06 low3.5 CVE-2025-31959 HCL BigFix Service Management (SM) application fails to strip EXIF metadata from uploaded images. hcltech · bigfix_service_management 2026-05-06 low2.6 CVE-2025-31957 HHCL BigFix Service Management (SM) is affected by a Cross‑Site Request Forgery (CSRF) vulnerability. hcltech · bigfix_service_management 2026-05-06 low3.1 CVE-2025-59854 HCL DFXAnalytics is affected by an Insecure Security Header Configuration vulnerability where the application utilizes the outdated X-XSS-Protection header, wh… hcltech · dfxanalytics 2026-05-06 low3.1 CVE-2025-59853 HCL DFXAnalytics is affected by an Improper Error Handling vulnerability where the application exposes detailed stack traces in responses, which could allow an… hcltech · dfxanalytics 2026-05-06 low3.7 CVE-2025-59852 HCL DFXAnalytics is affected by an Insufficient Transport Layer Protection vulnerability where data is transmitted over the network without encryption, which c… hcltech · dfxanalytics 2026-05-06 low3.7 CVE-2025-59851 HCL DFXAnalytics is affected by a Using Components with Known Vulnerabilities flaw where the application utilizes unpatched libraries or sub-components, which … hcltech · dfxanalytics 2026-05-06 low3.7 CVE-2025-31958 HCL BigFix Service Management is susceptible to HTTP Request Smuggling. hcltech · bigfix_service_management 2026-04-21 low2.9 CVE-2025-52641 HCL AION is affected by a vulnerability where certain system behaviours may allow exploration of internal filesystem structures. hcltech · aion 2026-04-15 low2.6 CVE-2025-55277 HCL Aftermarket DPC is affected by Use of Vulnerable/Outdated Versions vulnerability using which an attacker may make use of the exploits available across the … hcltech · aftermarket_cloud 2026-03-26 low3.1 CVE-2025-55276 HCL Aftermarket DPC is affected by Internal IP Disclosure vulnerability will give attackers a clearer map of the organization’s network layout. hcltech · aftermarket_cloud 2026-03-26 low3.7 CVE-2025-55275 HCL Aftermarket DPC is affected by Admin Session Concurrency vulnerability using which an attacker can exploit concurrent sessions to hijack or impersonate an … hcltech · aftermarket_cloud 2026-03-26 low2.6 CVE-2025-55274 HCL Aftermarket DPC is affected by Cross-Origin Resource Sharing vulnerability. hcltech · aftermarket_cloud 2026-03-26 low3.1 CVE-2025-55272 HCL Aftermarket DPC is affected by Banner Disclosure vulnerability where attackers gain insights into the system’s software and version details which would all… hcltech · aftermarket_cloud 2026-03-26 low3.1 CVE-2025-55271 HCL Aftermarket DPC is affected by HTTP Response Splitting vulnerability where in depending on how the web application handles the split response, an attacker … hcltech · aftermarket_cloud 2026-03-26 low3.5 CVE-2025-55270 HCL Aftermarket DPC is affected by Improper Input Validation which allows an attacker to inject executable code and can carry out attacks such as XSS, SQL Inje… hcltech · aftermarket_cloud 2026-03-26 low2.7 CVE-2025-31966 HCL Sametime is vulnerable to broken server-side validation. hcltech · sametime 2026-03-17 low1.8 CVE-2025-52649 HCL AION is affected by a vulnerability where certain identifiers may be predictable in nature. hcltech · aion 2026-03-16 low2.2 CVE-2025-52646 HCL AION is affected by a vulnerability where certain offering configurations may permit execution of potentially harmful SQL queries. hcltech · aion 2026-03-16

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.