NetSight

Security Dashboard

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

Reset
1,024 matching advisories · page 4 of 35Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2026-133029 In JetBrains TeamCity before 2026.2.1 missing authorization allowed guests to push VCS labels using stored VCS credentials JetBrains · TeamCity 2 days ago high8.8 CVE-2026-133027 In JetBrains TeamCity before 2026.2.1, 2026.1.5 privilege escalation was possible via username handling in token authentication JetBrains · TeamCity 2 days ago high7.7 CVE-2026-133025 In JetBrains TeamCity before 2026.2.1 missing authorization allowed project viewers to download project settings JetBrains · TeamCity 2 days ago high7.2 CVE-2026-133026 In JetBrains TeamCity before 2026.2.1, 2026.1.5 code injection in generated Kotlin DSL was possible via matrix build parameters JetBrains · TeamCity 2 days ago high7.5 CVE-2026-133024 In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via personal builds with versioned settings JetBrains · TeamCity 2 days ago high7.2 CVE-2026-133023 In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Kotlin DSL compiler arguments JetBrains · TeamCity 2 days ago high7.5 CVE-2026-133022 In JetBrains TeamCity before 2026.2.1 remote code execution was possible via the Notification Rules form JetBrains · TeamCity 2 days ago high7.4 CVE-2026-133020 In JetBrains TeamCity before 2026.1.5 untrusted build approval for GitHub fork pull requests could be bypassed JetBrains · TeamCity 2 days ago high7.5 CVE-2026-133021 In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Mercurial subrepository paths JetBrains · TeamCity 2 days ago high8.8 CVE-2026-133019 In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via a context parameters callback in the Kotlin DSL sandbox JetBrains · TeamCity 2 days ago high8.8 CVE-2026-133018 In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via a UI patches callback in the Kotlin DSL sandbox JetBrains · TeamCity 2 days ago high8.0 CVE-2026-133017 In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Git VCS root settings JetBrains · TeamCity 2 days ago high8.8 CVE-2026-133016 In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via script definitions in the Kotlin DSL settings repository JetBrains · TeamCity 2 days ago high8.8 CVE-2026-133015 In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via boot classpath libraries in the Kotlin DSL sandbox JetBrains · TeamCity 2 days ago high7.2 CVE-2026-133014 In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via public reflection in the Kotlin DSL sandbox JetBrains · TeamCity 2 days ago low2.7 CVE-2026-132996 In JetBrains TeamCity before 2026.2 mute and unmute operations via XML-RPC could be attributed to other users JetBrains · TeamCity 3 days ago low3.5 CVE-2026-132995 In JetBrains TeamCity before 2026.2 stored XSS on the build step settings page was possible JetBrains · TeamCity 3 days ago low2.7 CVE-2026-132994 In JetBrains TeamCity before 2026.2 the REST API exposed details of users not visible in the UI JetBrains · TeamCity 3 days ago low3.1 CVE-2026-132992 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the agent info popup was possible JetBrains · TeamCity 3 days ago low3.7 CVE-2026-132993 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the notification rules editor was possible JetBrains · TeamCity 3 days ago low3.5 CVE-2026-132989 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the SSH Keys page was possible JetBrains · TeamCity 3 days ago low3.1 CVE-2026-132990 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in Change Log revision tooltips was possible JetBrains · TeamCity 3 days ago low3.1 CVE-2026-132991 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Slack connection test page was possible JetBrains · TeamCity 3 days ago low2.7 CVE-2026-132988 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 the Cloud Profiles page disclosed cloud profiles of projects the user could not access JetBrains · TeamCity 3 days ago medium4.8 CVE-2026-132987 In JetBrains TeamCity before 2026.2 server certificates were not verified in the SVN integration JetBrains · TeamCity 3 days ago medium5.3 CVE-2026-132986 In JetBrains TeamCity before 2026.2 password parameters containing a caret were not masked in build logs on Windows JetBrains · TeamCity 3 days ago medium4.9 CVE-2026-132985 In JetBrains TeamCity before 2026.2 project administrators could read OAuth connection secrets of ancestor projects JetBrains · TeamCity 3 days ago medium6.8 CVE-2026-132983 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Report Tabs settings page was possible JetBrains · TeamCity 3 days ago medium5.4 CVE-2026-132984 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the project Report Tab dialog was possible JetBrains · TeamCity 3 days ago medium4.8 CVE-2026-132981 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Versioned Settings page was possible JetBrains · TeamCity 3 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.