NetSight

Security Dashboard

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

Reset
233 matching advisories · page 3 of 8Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.4 CVE-2026-23612 GFI MailEssentials AI versions prior to 22.4 contain a stored cross-site scripting vulnerability in the IP DNS Blocklist configuration page. gfi · mailessentials 2026-02-19 medium5.4 CVE-2026-23611 GFI MailEssentials AI versions prior to 22.4 contain a stored cross-site scripting vulnerability in the IP Blocklist management page. gfi · mailessentials 2026-02-19 medium5.4 CVE-2026-23610 GFI MailEssentials AI versions prior to 22.4 contain a stored cross-site scripting vulnerability in the POP2Exchange configuration endpoint. gfi · mailessentials 2026-02-19 medium5.4 CVE-2026-23609 GFI MailEssentials AI versions prior to 22.4 contain a stored cross-site scripting vulnerability in the Perimeter SMTP Servers configuration page. gfi · mailessentials 2026-02-19 medium5.4 CVE-2026-23608 GFI MailEssentials AI versions prior to 22.4 contain a stored cross-site scripting vulnerability in the Mail Monitoring rule creation endpoint. gfi · mailessentials 2026-02-19 medium5.4 CVE-2026-23607 GFI MailEssentials AI versions prior to 22.4 contain a stored cross-site scripting vulnerability in the Anti-Spam Whitelist management interface. gfi · mailessentials 2026-02-19 medium5.4 CVE-2026-23606 GFI MailEssentials AI versions prior to 22.4 contain a stored cross-site scripting vulnerability in the Advanced Content Filtering rule creation workflow. gfi · mailessentials 2026-02-19 medium5.4 CVE-2026-23605 GFI MailEssentials AI versions prior to 22.4 contain a stored cross-site scripting vulnerability in the Attachment Filtering rule creation workflow. gfi · mailessentials 2026-02-19 medium5.4 CVE-2026-23604 GFI MailEssentials AI versions prior to 22.4 contain a stored cross-site scripting vulnerability in the Keyword Filtering rule creation workflow. gfi · mailessentials 2026-02-19 medium5.3 CVE-2023-37525 A sensitive information disclosure in HCL BigFix Compliance allows a remote attacker to access files under the WEB-INF directory, which may contain Java class … hcltech · bigfix_compliance 2026-01-28 medium4.7 CVE-2025-59849 Improper management of Content Security Policy in HCL BigFix Remote Control Lite Web Portal (versions 10.1.0.0326 and lower) may allow the execution of malicio… hcltechsw · hcl_devops_deploy, hcltechsw · hcl_launch 2025-12-17 medium5.4 CVE-2025-52622 The BigFix SaaS's HTTP responses were missing some security headers. 2025-12-02 medium6.5 CVE-2025-34238 Advantech WebAccess/VPN versions prior to 1.1.5 contain an absolute path traversal via AjaxStandaloneVpnClientsController.ajaxDownloadRoadWarriorConfigFileActi… advantech · webaccess\/vpn 2025-11-06 medium4.2 CVE-2025-52602 HCL BigFix Query is affected by a sensitive information disclosure in the WebUI Query application. 2025-11-05 medium6.5 CVE-2025-0277 HCL BigFix Mobile 3.3 and earlier are vulnerable to certain insecure directives within the Content Security Policy (CSP). hcltech · bigfix_mobile, hcltech · bigfix_modern_client_management 2025-10-16 medium6.5 CVE-2025-0276 HCL BigFix Modern Client Management (MCM) 3.3 and earlier are vulnerable to certain insecure directives within the Content Security Policy (CSP). hcltech · bigfix_mobile, hcltech · bigfix_modern_client_management 2025-10-16 medium5.3 CVE-2025-0275 HCL BigFix Mobile 3.3 and earlier is affected by improper access control. hcltech · bigfix_mobile, hcltech · bigfix_modern_client_management 2025-10-16 medium5.3 CVE-2025-0274 HCL BigFix Modern Client Management (MCM) 3.3 and earlier is affected by improper access control. hcltech · bigfix_mobile, hcltech · bigfix_modern_client_management 2025-10-16 medium6.1 CVE-2025-52647 The BigFix WebUI application responds with HOST information from the HTTP header field making it vulnerable to Host Header Poisoning Attacks. 2025-10-10 medium6.0 CVE-2025-10217 A vulnerability exists in Asset Suite for an authenticated user to manipulate the content of performance related log data or to inject crafted data in logfile … 2025-09-30 medium5.4 CVE-2025-31979 A File Upload Validation Bypass vulnerability has been identified in the HCL BigFix SM, where the application fails to properly enforce file type restrictions … 2025-08-28 medium5.3 CVE-2025-31977 HCL BigFix SM is affected by cryptographic weakness due to weak or outdated encryption algorithms. hcltech · bigfix_service_management 2025-08-28 medium6.5 CVE-2025-31972 HCL BigFix SM is affected by a Sensitive Information Exposure vulnerability where internal connections do not use TLS encryption which could allow an attacker … hcltech · bigfix_service_management 2025-08-28 medium5.3 CVE-2025-52621 HCL BigFix SaaS Authentication Service is vulnerable to cache poisoning. hcltech · bigfix_saas 2025-08-15 medium4.3 CVE-2025-52620 HCL BigFix SaaS Authentication Service is affected by a Cross-Site Scripting (XSS) vulnerability. hcltech · bigfix_saas 2025-08-15 medium5.3 CVE-2025-52619 HCL BigFix SaaS Authentication Service is affected by a sensitive information disclosure. hcltech · bigfix_saas 2025-08-15 medium4.3 CVE-2025-52618 HCL BigFix SaaS Authentication Service is affected by a SQL injection vulnerability. hcltech · bigfix_saas 2025-08-15 medium5.3 CVE-2024-42213 HCL BigFix Compliance is affected by inclusion of temporary files left in the production environment. hcltech · bigfix_compliance 2025-05-05 medium5.4 CVE-2024-42212 HCL BigFix Compliance is affected by an improper or missing SameSite attribute. hcltech · bigfix_compliance 2025-05-05 medium6.5 CVE-2025-34490 GFI MailEssentials prior to version 21.8 is vulnerable to an XML External Entity (XXE) issue. gfi · mailessentials 2025-04-28

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.