NetSight

Security Dashboard

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

Reset
39 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2026-70550 An authorization weakness in JFrog Artifactory Composer repository handling may allow an authenticated user, under specific conditions, to read package metadat… 2026-08-25 medium4.3 CVE-2026-70547 An authenticated user without repository read permission may access package metadata under specific conditions. jfrog · artifactory 2026-08-12 medium5.9 CVE-2026-69107 An unauthenticated user may access restricted artifacts in JFrog Artifactory under specific conditions. jfrog · artifactory 2026-08-12 medium6.5 CVE-2026-68758 A low-privileged authenticated user may access restricted support information under specific conditions. jfrog · artifactory 2026-08-12 medium6.7 CVE-2026-66016 Under specific self-hosted Helm configurations, generated TLS private keys may be retained in rendered manifests accessible to highly privileged local users. jfrog · artifactory 2026-08-12 medium5.3 CVE-2026-68760 An unauthenticated user may bypass authentication under specific cache conditions. jfrog · artifactory 2026-08-12 medium6.6 CVE-2026-68756 A party with write access to stored session data may affect JFrog Artifactory under specific conditions. jfrog · artifactory 2026-08-12 medium4.3 CVE-2026-68755 A bundle writer may create misleading release promotion information under specific conditions. jfrog · artifactory 2026-08-12 medium6.5 CVE-2026-68754 A repository publisher without delete permission may modify protected package content under specific conditions. jfrog · artifactory 2026-08-12 medium5.3 CVE-2026-68753 An unauthenticated user may access restricted Artifactory content when a credentialed remote repository is configured in a specific way. jfrog · artifactory 2026-08-12 medium4.3 CVE-2026-66382 An authenticated user may write files outside the intended Artifactory work directory under specific conditions. jfrog · artifactory 2026-08-12 medium5.3 CVE-2026-66381 A repository reader with cache-deploy permission may access content outside a configured upstream path under specific conditions. jfrog · artifactory 2026-08-12 medium4.3 CVE-2026-66380 An authenticated user without repository read permission may access private OCI referrer metadata under specific conditions. jfrog · artifactory 2026-08-12 medium4.3 CVE-2026-66379 An authenticated user may view private Puppet module metadata without repository read access. jfrog · artifactory 2026-08-12 medium4.3 CVE-2026-66378 An authenticated user without repository read permission may access private NuGet metadata under specific conditions. jfrog · artifactory 2026-08-12 medium5.3 CVE-2026-66377 An unauthenticated user may access restricted repository information under specific conditions. jfrog · artifactory 2026-08-12 medium4.2 CVE-2026-66376 Credentials for a deleted user may remain valid for a short period under specific conditions. jfrog · artifactory 2026-08-12 medium5.3 CVE-2026-66384 JFrog Artifactory Improper Limitation of a Pathname to a Restricted Directory VulnerabilityExploited JFrog · Artifactory, jfrog · artifactory 2026-08-12 medium6.5 CVE-2026-66018 Build readers can access another repository's environment properties. jfrog · artifactory 2026-07-27 medium6.5 CVE-2026-65925 A user with JFrog Artifactory Cargo remote repository read access could make Artifactory request unintended URLs and return the response. jfrog · artifactory 2026-07-27 medium6.5 CVE-2026-65924 JFrog Artifactory support for Terraform remote repositories was found to be susceptible to Server-Side Request Forgery (SSRF). jfrog · artifactory 2026-07-27 medium6.8 CVE-2026-65923 A URL validation weakness in JFrog Artifactory Ansible repository handling could allow a user, under specific repository access conditions, to cause unintended… jfrog · artifactory 2026-07-27 medium6.5 CVE-2026-65618 Improper URL validation when handling specific URLs, allows an attacker, under certain conditions, to make unauthorized requests from JFrog Artifactory, potent… jfrog · artifactory 2026-07-27 medium4.9 CVE-2025-14830 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in JFrog Artifactory (Workers) allows Cross-Site Scri… Artifactory (Workers): from >=7.94.0 through 2026-01-04 medium6.4 CVE-2024-2248 A Header Injection vulnerability in the JFrog platform in versions below 7.85.0 (SaaS) and 7.84.7 (Self-Hosted) may allow threat actors to take over the end us… 2024-05-15 medium4.3 CVE-2024-3505 JFrog Artifactory Self-Hosted versions below 7.77.3, are vulnerable to sensitive information disclosure whereby a low-privileged authenticated user can read th… jfrog · artifactory 2024-04-15 medium6.6 CVE-2023-42509 JFrog Artifactory later than version 7.17.4 but prior to version 7.77.0 is vulnerable to an issue whereby a sequence of improperly handled exceptions in reposi… jfrog · artifactory 2024-03-07 medium6.5 CVE-2023-42508 JFrog Artifactory prior to version 7.66.0 is vulnerable to specific endpoint abuse with a specially crafted payload, which can lead to unauthenticated users be… jfrog · artifactory 2023-10-03 medium5.3 CVE-2022-0668 JFrog Artifactory prior to 7.37.13 is vulnerable to Authentication Bypass, which can lead to Privilege Escalation when a specially crafted request is sent by a… jfrog · artifactory 2023-01-08 medium4.9 CVE-2021-46687 JFrog Artifactory prior to version 7.31.10 and 6.23.38 is vulnerable to Sensitive Data Exposure through the Project Administrator REST API. jfrog · artifactory 2022-07-06

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.