NetSight

Security Dashboard

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

Reset
28 matching advisories · page 1 of 1Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.4 CVE-2026-92132 Jenkins Gradle Plugin 2.19.1252.v15196b_5a_6e10 and earlier requests build scan data from the build scan link detected in the build log, even when a Develocity… 2026-09-16 medium6.7 CVE-2026-76228 Renovate versions >=32.124.0 and before 42.68.5 (and Mend renovate-ce/renovate-ee before 13.3.0) contain a command injection vulnerability in Gradle Wrapper ar… Renovate versions >=32.124.0 and 2026-08-19 medium6.7 CVE-2026-53914 In JetBrains Kotlin before 2.4.20 code execution was possible via unsafe deserialization in the build cache metadata maven · org.jetbrains.kotlin:kotlin-gradle-plugin 2026-06-26 medium6.7 GHSA-pfq2-hh62-7m96 Renovate vulnerable to arbitrary command injection via Gradle Wrapper and malicious `distributionUrl` npm · renovate 2026-01-13 medium6.8 CVE-2023-42445 Gradle is a build tool with a focus on build automation and support for multi-language development. gradle · gradle 2023-10-06 medium6.5 CVE-2023-39152 Incorrect control flow in Jenkins Gradle Plugin breaks credentials masking in the build log maven · org.jenkins-ci.plugins:gradle 2023-07-26 medium6.9 CVE-2023-35946 Gradle is a build tool with a focus on build automation and support for multi-language development. gradle · gradle 2023-06-30 medium6.9 CVE-2023-35947 Gradle is a build tool with a focus on build automation and support for multi-language development. gradle · gradle 2023-06-30 medium4.5 CVE-2022-48431 In JetBrains IntelliJ IDEA before 2023.1 in some cases, Gradle and Maven projects could be imported without the “Trust Project” confirmation. jetbrains · intellij_idea 2023-03-29 medium6.6 CVE-2023-26053 Gradle is a build tool with a focus on build automation and support for multi-language development. gradle · gradle 2023-03-02 medium6.3 CVE-2022-22984 Snyk plugins vulnerable to Command Injection npm · snyk, npm · snyk-mvn-plugin, npm · snyk-sbt-plugin +5 2022-11-30 medium6.6 CVE-2022-31156 Gradle is a build tool. gradle · gradle 2022-07-14 medium6.5 CVE-2022-27225 Gradle Enterprise before 2021.4.3 relies on cleartext data transmission in some situations. gradle · enterprise 2022-03-16 medium5.3 CVE-2022-24329 In JetBrains Kotlin before 1.6.0, it was not possible to lock dependencies for Multiplatform Gradle Projects. maven · org.jetbrains.kotlin:kotlin-stdlib 2022-02-25 medium5.3 CVE-2021-41590 In Gradle Enterprise through 2021.3, probing of the server-side network environment can occur via an SMTP configuration test. gradle · enterprise 2021-10-27 medium6.1 CVE-2021-25959 Cross-site Scripting in OpenCRX maven · org.opencrx:opencrx-core, maven · org.opencrx:opencrx-core-models, maven · org.opencrx:opencrx-core-config +2 2021-09-29 medium4.0 CVE-2021-29429 In Gradle before version 7.0, files created with open permissions in the system temporary directory can allow an attacker to access information downloaded by G… gradle · gradle, quarkus · quarkus 2021-04-12 medium6.5 CVE-2021-26719 A directory traversal issue was discovered in Gradle gradle-enterprise-test-distribution-agent before 1.3.2, test-distribution-gradle-plugin before 1.3.2, and … gradle · enterprise_test_distribution_agent, gradle · maven, gradle · test_distribution 2021-02-09 medium6.5 CVE-2020-15773 An issue was discovered in Gradle Enterprise before 2020.2.4. gradle · enterprise 2020-09-18 medium6.8 CVE-2020-15774 An issue was discovered in Gradle Enterprise 2018.5 - 2020.2.4. gradle · enterprise 2020-09-18 medium4.9 CVE-2020-15772 An issue was discovered in Gradle Enterprise 2018.5 - 2020.2.4. gradle · enterprise 2020-09-18 medium5.5 CVE-2020-15770 An issue was discovered in Gradle Enterprise 2018.5. gradle · enterprise 2020-09-18 medium6.1 CVE-2020-15769 An issue was discovered in Gradle Enterprise 2020.2 - 2020.2.4. gradle · enterprise 2020-09-18 medium5.3 CVE-2020-15767 An issue was discovered in Gradle Enterprise before 2020.2.5. gradle · enterprise 2020-09-18 medium6.5 CVE-2020-7599 Exposure of Sensitive Information in Gradle publish plugin maven · com.gradle.publish:plugin-publish-plugin, maven · com.gradle.plugin-publish:com.gradle.plugin-publish.gradle.plugin 2020-03-30 medium5.9 CVE-2019-16370 Use of a weak cryptographic algorithm in Gradle maven · org.gradle:gradle-core 2019-09-16 medium6.5 CVE-2019-10324 A cross-site request forgery vulnerability in Jenkins Artifactory Plugin 3.2.2 and earlier in ReleaseAction#doSubmit, GradleReleaseApiAction#doStaging, MavenRe… maven · org.jenkins-ci.plugins:artifactory 2019-05-31 medium5.9 CVE-2019-11065 Insecure transport protocol in Gradle maven · org.gradle:gradle-core 2019-04-10

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.