NetSight

Security Dashboard

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

Reset
55 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-wg33-999f-mvvm Malicious code in cloudera-manager-client (npm)Malware npm · cloudera-manager-client 2026-09-04 critical GHSA-gw92-w32h-w3jg Malicious code in cloudera-poc (npm)Malware npm · cloudera-poc 2026-09-04 critical GHSA-52qc-xjj8-gfhh Malicious code in cloudera (npm)Malware npm · cloudera 2026-09-04 high7.5 CVE-2025-3884 Cloudera Hue Ace Editor Directory Traversal Information Disclosure Vulnerability. cloudera · hue 2025-05-22 high8.7 CVE-2024-54660 A JNDI injection issue was discovered in Cloudera JDBC Connector for Hive before 2.6.26 and JDBC Connector for Impala before 2.6.35. Cloudera JDBC Connector for Hive, JDBC Connector for Impala 2025-01-16 medium5.3 CVE-2021-32483 Cloudera Manager 7.2.4 has Incorrect Access Control, allowing Escalation of Privileges to view the restricted Dashboard. cloudera · cloudera_manager 2021-11-08 critical9.8 CVE-2021-30132 Cloudera Manager 7.2.4 has Incorrect Access Control, allowing Escalation of Privileges. cloudera · cloudera_manager 2021-11-08 medium6.1 CVE-2021-32482 Cloudera Manager 5.x, 6.x, 7.1.x, 7.2.x, and 7.3.x allows XSS via the path parameter. cloudera · cloudera_manager 2021-11-08 medium6.1 CVE-2021-32481 Cloudera Hue 4.6.0 allows XSS via the type parameter. cloudera · hue 2021-11-08 medium6.1 CVE-2021-29994 Cloudera Hue 4.6.0 allows XSS. cloudera · hue 2021-11-08 medium6.1 CVE-2021-29243 Cloudera Manager 5.x, 6.x, 7.1.x, 7.2.x, and 7.3.x allows XSS. cloudera · cloudera_manager 2021-11-08 medium6.5 CVE-2021-3167 In Cloudera Data Engineering (CDE) 1.3.0, JWT authentication tokens are exposed to administrators in virtual cluster server logs. cloudera · data_engineering 2021-03-15 high8.8 CVE-2020-26936 Cloudera Data Engineering (CDE) before 1.1 was vulnerable to a CSRF attack. cloudera · data_engineering 2020-11-26 medium5.4 CVE-2019-14449 An issue was discovered in Cloudera Manager 5.x before 5.16.2, 6.0.x before 6.0.2, and 6.1.x before 6.1.1. cloudera · cloudera_manager 2019-11-26 high8.3 CVE-2019-7319 An issue was discovered in Cloudera Hue 6.0.0 through 6.1.0. cloudera · cdh 2019-11-26 high8.3 CVE-2018-20090 An issue was discovered in Cloudera Data Science Workbench (CDSW) 1.4.0 through 1.4.2. cloudera · data_science_workbench 2019-11-26 high8.8 CVE-2017-7399 Cloudera Manager 5.8.x before 5.8.5, 5.9.x before 5.9.2, and 5.10.x before 5.10.1 allows a read-only Cloudera Manager user to discover the usernames of other u… cloudera · cloudera_manager 2019-11-26 medium5.4 CVE-2016-9271 Cloudera Manager 5.7.x before 5.7.6, 5.8.x before 5.8.4, and 5.9.x before 5.9.1 allows XSS in the help search feature. cloudera · cloudera_manager 2019-11-26 high7.2 CVE-2018-17860 Cloudera CDH has Insecure Permissions because ALL cannot be revoked.This affects 5.x through 5.15.1 and 6.x through 6.0.1. cloudera · cdh 2019-11-26 medium5.4 CVE-2015-4457 Multiple cross-site scripting (XSS) vulnerabilities in the Cloudera Manager UI before 5.4.3 allow remote authenticated users to inject arbitrary web script or … cloudera · cloudera_manager 2019-11-26 medium6.5 CVE-2016-6353 Cloudera Search in CDH before 5.7.0 allows unauthorized document access because Solr Queries by document id can bypass Sentry document-level security via the R… cloudera · cdh 2019-11-26 high7.5 CVE-2016-5724 Cloudera CDH before 5.9 has Potentially Sensitive Information in Diagnostic Support Bundles. cloudera · cdh 2019-11-26 high8.8 CVE-2016-4572 In Cloudera CDH before 5.7.1, Impala REVOKE ALL ON SERVER commands do not revoke all privileges. cloudera · cdh 2019-11-26 medium6.5 CVE-2016-3192 Cloudera Manager 5.x before 5.7.1 places Sensitive Data in cleartext Readable Files. cloudera · cloudera_manager 2019-11-26 medium6.5 CVE-2016-3131 Cloudera CDH before 5.6.1 allows authorization bypass via direct internal API calls. cloudera · cdh 2019-11-26 high8.8 CVE-2015-7831 In Cloudera Hue, there is privilege escalation by a read-only user when CDH 5.x brefore 5.4.9 is used. cloudera · cdh 2019-11-26 high7.5 CVE-2015-6495 There is Sensitive Information in Cloudera Manager before 5.4.6 Diagnostic Support Bundles. cloudera · cloudera_manager 2019-11-26 high8.1 CVE-2018-11744 Cloudera Manager through 5.15 has Incorrect Access Control. cloudera · cloudera_manager 2019-07-11 medium6.5 CVE-2017-9327 Secret data of processes managed by CM is not secured by file permissions. cloudera · cloudera_manager 2019-07-03 high7.5 CVE-2017-9326 The keystore password for the Spark History Server may be exposed in unsecured files under the /var/run/cloudera-scm-agent directory managed by Cloudera Manage… cloudera · cloudera_manager 2019-07-03

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.