NetSight

Security Dashboard

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

Reset
1,024 matching advisories · page 3 of 35Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.2 CVE-2026-133078 In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via security context spoofing in the Kotlin DSL sandbox JetBrains · TeamCity 2 days ago high7.5 CVE-2026-133076 In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via local repository URLs in Subversion VCS roots JetBrains · TeamCity 2 days ago high7.2 CVE-2026-133077 In JetBrains TeamCity before 2026.2.2, 2026.1.6 privilege escalation to system administrator was possible via Project Import JetBrains · TeamCity 2 days ago low3.5 CVE-2026-133055 In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS on the Failure Conditions page was possible JetBrains · TeamCity 2 days ago low3.5 CVE-2026-133056 In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in implicit agent requirements was possible JetBrains · TeamCity 2 days ago low3.7 CVE-2026-133057 In JetBrains TeamCity before 2026.2.1, 2026.1.5 the TFS helper server was exposed on all network interfaces 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 medium6.8 CVE-2026-133047 In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS on the thread dump page was possible JetBrains · TeamCity 2 days ago medium5.4 CVE-2026-133048 In JetBrains TeamCity before 2026.2.1 improper authorization allowed using AWS connections of other projects in cloud profiles JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133049 In JetBrains TeamCity before 2026.2.1 stored XSS in the Pull Requests health report for VCS roots was possible JetBrains · TeamCity 2 days ago medium6.5 CVE-2026-133043 In JetBrains TeamCity before 2026.2.1 missing authorization allowed reading VCS file contents and patches of other projects JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133045 In JetBrains TeamCity before 2026.2.1 stored XSS in VMware vSphere cloud profile settings was possible JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133039 In JetBrains TeamCity before 2026.2.1 stored XSS in the Pull Requests health report for Space connections was possible JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133041 In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Commit Status Publisher settings was possible JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133042 In JetBrains TeamCity before 2026.2.1 stored XSS in the Amazon EC2 cloud profile editor was possible JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133036 In JetBrains TeamCity before 2026.2.1 stored XSS in the Issue Trackers health report was possible JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133037 In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the GitHub App repository selector was possible JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133038 In JetBrains TeamCity before 2026.2.1 stored XSS in the Maven Build Info project header was possible JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133033 In JetBrains TeamCity before 2026.2.1 stored XSS in Maven Build Info module links was possible JetBrains · TeamCity 2 days ago medium6.4 CVE-2026-133034 In JetBrains TeamCity before 2026.2.1 stored XSS on the Changes page was possible JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133035 In JetBrains TeamCity before 2026.2.1 stored XSS on the change Files tab was possible JetBrains · TeamCity 2 days ago medium6.1 CVE-2026-133032 In JetBrains TeamCity before 2026.2.1 reflected XSS on the Cloud Profiles page was possible JetBrains · TeamCity 2 days ago medium6.8 CVE-2026-133031 In JetBrains TeamCity before 2026.2.1 stored XSS in Git VCS root settings was possible JetBrains · TeamCity 2 days ago medium6.5 CVE-2026-133028 In JetBrains TeamCity before 2026.2.1 missing authorization allowed running modified build steps via pipeline debug runs JetBrains · TeamCity 2 days ago medium6.5 CVE-2026-133030 In JetBrains TeamCity before 2026.2.1 the build parameter editor allowed project settings viewers to recover protected credentials 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.