NetSight

Security Dashboard

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

Reset
1,976 matching advisories · page 7 of 66Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2025-64148 Jenkins Publish to Bitbucket Plugin is missing a permissions check maven · org.jenkins-ci.plugins:publish-to-bitbucket 2025-10-29 medium4.3 CVE-2025-64147 Jenkins Curseforge Publisher Plugin does not mask API Keys displayed on the job configuration form maven · org.jenkins-ci.plugins:curseforge-publisher 2025-10-29 medium4.3 CVE-2025-64146 Jenkins Curseforge Publisher Plugin stores API Keys unencrypted in job config.xml files maven · org.jenkins-ci.plugins:curseforge-publisher 2025-10-29 medium4.3 CVE-2025-64145 Jenkins ByteGuard Build Actions Plugin does not mask API tokens displayed on the job configuration form maven · io.jenkins.plugins:byteguard-build-actions 2025-10-29 medium4.3 CVE-2025-64144 Jenkins ByteGuard Build Actions Plugin stores API tokens unencrypted in job config.xml files maven · io.jenkins.plugins:byteguard-build-actions 2025-10-29 medium4.3 CVE-2025-64143 Jenkins OpenShift Pipeline Plugin stores authorization tokens unencrypted in job config.xml files maven · com.openshift.jenkins:openshift-pipeline 2025-10-29 medium4.3 CVE-2025-64142 Jenkins Nexus Task Runner Plugin is missing a permission check maven · org.jenkins-ci.plugins:nexus-task-runner 2025-10-29 medium4.3 CVE-2025-64141 Jenkins Nexus Task Runner Plugin vulnerable to cross-site request forgery maven · org.jenkins-ci.plugins:nexus-task-runner 2025-10-29 high8.8 CVE-2025-64140 Jenkins Azure CLI Plugin does not restrict the commands it executes maven · org.jenkins-ci.plugins:azure-cli 2025-10-29 medium4.3 CVE-2025-64139 Jenkins Start Windocks Containers Plugin is missing a permission check maven · org.jenkins-ci.plugins:windocks-start-container 2025-10-29 medium4.3 CVE-2025-64138 Jenkins Start Windocks Containers Plugin vulnerable to cross-site request forgery maven · org.jenkins-ci.plugins:windocks-start-container 2025-10-29 medium4.3 CVE-2025-64137 Jenkins Themis Plugin is missing a permission check maven · org.jenkins-ci.plugins:themis 2025-10-29 medium4.3 CVE-2025-64136 Jenkins Themis Plugin vulnerable to cross-site request forgery maven · org.jenkins-ci.plugins:themis 2025-10-29 medium5.9 CVE-2025-64135 Jenkins Eggplant Runner Plugin protection mechanism disabled maven · io.jenkins.plugins:eggplant-runner 2025-10-29 high7.1 CVE-2025-64134 Jenkins JDepend Plugin vulnerable to XML external entity attacks maven · org.jenkins-ci.plugins:jdepend 2025-10-29 medium5.4 CVE-2025-64133 Jenkins Extensible Choice Parameter Plugin vulnerable to cross-site request forgery maven · jp.ikedam.jenkins.plugins:extensible-choice-parameter 2025-10-29 medium5.4 CVE-2025-64132 Jenkins MCP Server Plugin does not perform permission checks in multiple MCP tools maven · io.jenkins.plugins:mcp-server 2025-10-29 high7.5 CVE-2025-64131 Jenkins SAML Plugin does not implement a replay cache maven · org.jenkins-ci.plugins:saml 2025-10-29 medium5.3 CVE-2025-59476 Jenkins has a log message injection vulnerability maven · org.jenkins-ci.main:jenkins-core 2025-09-17 medium4.3 CVE-2025-59475 Jenkins is missing a permission check in the authenticated users' profile menu maven · org.jenkins-ci.main:jenkins-core 2025-09-17 medium5.3 CVE-2025-59474 Jenkins has a missing permission check, allowing users to obtain agent names maven · org.jenkins-ci.main:jenkins-core 2025-09-17 medium4.2 CVE-2025-58460 Jenkins OpenTelemetry Plugin missing permission check allows capturing credentials maven · io.jenkins.plugins:opentelemetry 2025-09-03 medium4.3 CVE-2025-58459 Jenkins global-build-stats Plugin missing permission check can result in graph IDs being enumerated maven · org.jenkins-ci.plugins:global-build-stats 2025-09-03 medium4.3 CVE-2025-58458 Jenkins Git client Plugin file system information disclosure vulnerability maven · org.jenkins-ci.plugins:git-client 2025-09-03 critical GHSA-69jc-24mh-wxg4 Malware in jenkins-for-jira-uiMalware npm · jenkins-for-jira-ui 2025-07-17 medium4.3 CVE-2025-53743 Jenkins Applitools Eyes Plugin vulnerability does not mask API keys on its job configuration form maven · org.jenkins-ci.plugins:applitools-eyes 2025-07-09 medium4.3 CVE-2025-53742 Jenkins Applitools Eyes Plugin vulnerability exposes unencrypted keys to certain authenticated users maven · org.jenkins-ci.plugins:applitools-eyes 2025-07-09 medium6.5 CVE-2025-53678 Jenkins User1st uTester Plugin vulnerability exposes unencrypted token to authenticated users maven · io.jenkins.plugins:user1st-utester 2025-07-09 medium4.3 CVE-2025-53677 Jenkins Xooa Plugin vulnerability does not mask its Xooa Deployment Token maven · io.jenkins.plugins:xooa 2025-07-09 medium4.3 CVE-2025-53676 Jenkins Xooa Plugin vulnerability exposes unencrypted tokens to authenticated users maven · io.jenkins.plugins:xooa 2025-07-09

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.