NetSight

Security Dashboard

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

Reset
156 matching advisories · page 1 of 6Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.7 CVE-2026-67172 HCL BigFix Service Management is affected by an Information Disclosure vulnerability the application returns sensitive information in error messages when inval… hcltech · bigfix_service_management 51 days ago low2.2 CVE-2026-56599 HCL BigFix Service Management is affected by an Insecure Cookie Attribute Configuration vulnerability, which could allow an attacker to exploit missing securit… hcltech · bigfix_service_management 51 days ago low3.1 CVE-2026-21806 HCL BigFix Service Management is affected by an Administrative Session Concurrency vulnerability. hcltech · bigfix_service_management 2026-09-18 low3.1 CVE-2026-56597 HCL BigFix Service Management is affected by a Sensitive Information Leakage vulnerability, which could allow an unauthenticated attacker to extract internal I… hcltech · bigfix_service_management 2026-09-18 low3.1 CVE-2026-56595 HCL BigFix Service Management is affected by a CORS Misconfiguration vulnerability due to improperly validated origin headers, which could allow an attacker to… hcltech · bigfix_service_management 2026-09-18 low3.5 CVE-2025-52657 HCL MyXalytics was affected by Potential DOS Vulnerability. hcltech · myxalytics 2026-09-07 low3.5 CVE-2025-52652 HCL MyXalytics was affected by Content Spoofing Vulnerability. hcltech · myxalytics 2026-09-07 low3.5 CVE-2025-52651 HCL MyXalytics was affected by Improper Input validation Vulnerability. hcltech · myxalytics 2026-09-07 low3.7 CVE-2026-56608 HCL iControl is affected by Missing Access Control vulnerability. hcltech · icontrol 2026-08-03 low3.7 CVE-2026-56571 HCL iControl was affected by Improper Error Handling vulnerabilities. hcltech · icontrol 2026-07-31 low3.7 CVE-2026-56570 HCL iControl was affected by Auto complete Enabled vulnerabilities. hcltech · icontrol 2026-07-31 low3.7 CVE-2026-56568 HCL iControl was affected by Information Exposure Through Verbose Client-Side API Error Messages vulnerabilities. hcltech · icontrol 2026-07-31 low3.5 CVE-2026-56538 An endpoint in HCL Connections is vulnerable to information disclosure. hcltech · connections 2026-07-27 low3.5 CVE-2026-56537 HCL Connections is vulnerable to information disclosure which could allow a user to obtain sensitive information they are not entitled to, caused by improper h… hcltech · connections 2026-07-27 low3.1 CVE-2026-56583 HCL MyCloud was affected with Concurrent Login Vulnerability. hcltech · dryice_mycloud 2026-07-21 low3.1 CVE-2026-56582 HCL MyCloud was affected by the SSL/TLS LUCKY13 Vulnerability. hcltech · dryice_mycloud 2026-07-21 low2.6 CVE-2026-56581 HCL MyCloud was affected with Cookie Attribute Path Not Set. hcltech · dryice_mycloud 2026-07-21 low2.2 CVE-2026-56580 HCL MyCloud was affected by Using Components with Known Vulnerability ( IIS Server ). hcltech · dryice_mycloud 2026-07-21 low3.1 CVE-2026-56579 HCL MyCloud was affected with License Key Revealed in HTTP Response. hcltech · dryice_mycloud 2026-07-21 low2.2 CVE-2026-56578 HCL MyCloud was affected by Server Version Disclosure. hcltech · dryice_mycloud 2026-07-21 low3.1 CVE-2026-56577 HCL MyCloud was affected with Weak Password Policy. hcltech · dryice_mycloud 2026-07-21 low3.1 CVE-2026-56586 HCL IEM was affected with X-Content-Type-Options Header Missing. hcltech · intelliops_event_management 2026-07-21 low3.1 CVE-2026-56585 HCL IEM was affected with the Anti Clickjacking XFrame Options Header Missing. hcltech · intelliops_event_management 2026-07-21 low3.7 CVE-2026-56587 HCL IEM was affected with Strict transport security not enforced. hcltech · intelliops_event_management 2026-07-21 low3.7 CVE-2026-56584 HCL IEM was affected with the Information disclosure nginx server. hcltech · intelliops_event_management 2026-07-21 low3.1 CVE-2026-21764 HCL DevOps Loop is affected by insufficient input validation that allows special characters where they should be restricted. hcltech · devops_loop 2026-07-17 low3.7 CVE-2026-21762 HCL DevOps Loop is affected by missing HTTP security headers. hcltech · devops_loop 2026-07-17 low3.1 CVE-2026-35145 HCL DFXAnalytics is affected by a Missing HTTP Strict-Transport-Security Header vulnerability. hcltech · dfxanalytics 2026-07-16 low3.0 CVE-2026-35143 HCL DFXAnalytics is affected by a Missing SameSite Attribute vulnerability. hcltech · dfxanalytics 2026-07-16 low2.6 CVE-2026-35142 HCL DFXAnalytics is affected by an Internal IP Address Disclosure vulnerability. hcltech · dfxanalytics 2026-07-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.