NetSight

Security Dashboard

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

Reset
556 matching advisories · page 1 of 19Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.4 CVE-2026-133262 In JetBrains YouTrack before 2026.2.19766 improper authorization allowed read-only users to change the visibility of restricted issues via agile boards JetBrains · YouTrack 2 days ago medium5.4 CVE-2026-133261 In JetBrains YouTrack before 2026.2.19840 an HTML injection in email notifications was possible via issue descriptions JetBrains · YouTrack 2 days ago medium6.5 CVE-2026-133260 In JetBrains YouTrack before 2026.2.19840 privilege escalation from project administrator to system administrator was possible via group merging JetBrains · YouTrack 2 days ago medium4.8 CVE-2026-133258 In JetBrains YouTrack before 2026.2.19840 app widgets could perform API requests on behalf of viewing users without their consent JetBrains · YouTrack 2 days ago medium4.3 CVE-2026-133259 In JetBrains YouTrack before 2026.2.19840 improper authorization allowed read-only users to change issue fields via agile boards JetBrains · YouTrack 2 days ago medium5.4 CVE-2026-133257 In JetBrains YouTrack before 2026.2.19840 improper authorization allowed read-only users to modify and delete articles JetBrains · YouTrack 2 days ago medium6.8 CVE-2026-133256 In JetBrains YouTrack before 2026.2.19840 improper authorization allowed project administrators to obtain GitLab tokens of other projects JetBrains · YouTrack 2 days ago medium5.3 CVE-2026-133255 In JetBrains Ktor before 3.6.1 a DoS attack was possible via the CIO engine JetBrains · Ktor 2 days ago medium6.5 CVE-2026-133251 In JetBrains Datalore before 2026.4.1 improper authorization allowed notebook viewers to read attached environment variable values JetBrains · Datalore 2 days ago medium5.0 CVE-2026-133197 In JetBrains Junie CLI before 26.9.22 command injection was possible via file names in code review JetBrains · Junie CLI 2 days ago medium5.3 CVE-2026-133196 In JetBrains Junie CLI before 26.11.1 files outside the project could be overwritten via shell output redirection JetBrains · Junie CLI 2 days ago medium5.6 CVE-2026-133193 In JetBrains Junie GitHub Action before 1.10.0 code execution was possible via path traversal in feedback session markers JetBrains · Junie GitHub Action 2 days ago medium5.6 CVE-2026-133194 In JetBrains Junie GitHub Action before 1.10.0 command injection was possible via the action version input JetBrains · Junie GitHub Action 2 days ago medium4.2 CVE-2026-133192 In JetBrains Junie GitHub Action before 1.10.0 untrusted fork code could be processed in privileged workflow runs JetBrains · Junie GitHub Action 2 days ago medium5.5 CVE-2026-133182 In JetBrains IntelliJ IDEA before 2026.3 the GitHub plugin exposed GitHub access tokens via its public API JetBrains · IntelliJ IDEA 2 days ago medium6.8 CVE-2026-133106 In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS on the Projects Import page was possible JetBrains · TeamCity 2 days ago medium6.4 CVE-2026-133104 In JetBrains TeamCity before 2026.2.2 stored XSS in external change viewer links was possible JetBrains · TeamCity 2 days ago medium6.1 CVE-2026-133105 In JetBrains TeamCity before 2026.2.2, 2026.1.6 reflected XSS on the Edit VCS Root page was possible JetBrains · TeamCity 2 days ago medium4.9 CVE-2026-133102 In JetBrains TeamCity before 2026.2.2, 2026.1.6 out-of-band data exfiltration via DNS resolution was possible in the Kotlin DSL sandbox JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133103 In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS in the enforced settings restriction tooltip was possible JetBrains · TeamCity 2 days ago medium6.5 CVE-2026-133101 In JetBrains TeamCity before 2026.2.2 a CSRF attack was possible on the diagnostic page JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133100 In JetBrains TeamCity before 2026.2.2, 2026.1.6 command injection in Project Import artifact copy scripts was possible JetBrains · TeamCity 2 days ago medium6.5 CVE-2026-133099 In JetBrains TeamCity before 2026.2.2 vCS root passwords could be extracted via the REST API property locator JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133098 In JetBrains TeamCity before 2026.2.2 stored XSS in GitHub issue tracker suggestions was possible JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133052 In JetBrains TeamCity before 2026.2.1, 2026.1.5 a DOM-based XSS in the plugin installation dialog was possible JetBrains · TeamCity 2 days ago medium5.3 CVE-2026-133053 In JetBrains TeamCity before 2026.2.1 arbitrary file read was possible via symlinks in Mercurial subrepositories JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133054 In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Create Project dialog was possible JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133050 In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored and reflected XSS in Space project connection dialogs was possible JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133051 In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the JaCoCo coverage settings was possible JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133046 In JetBrains TeamCity before 2026.2.1 stored XSS in recipe export errors was possible JetBrains · TeamCity 2 days ago

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.