NetSight

Security Dashboard

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

Reset
280 matching advisories · page 1 of 10Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.3 CVE-2026-133254 In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 code execution was possible in untrusted projects via the Code Provenance plugin JetBrains · IntelliJ IDEA 2 days ago high7.4 CVE-2026-133253 In JetBrains IntelliJ IDEA before 2026.3 untrusted projects could read files of other open projects via the built-in web server JetBrains · IntelliJ IDEA 2 days ago high7.8 CVE-2026-133198 In JetBrains Junie before 252.819.35, 253.819.35 code execution was possible via terminal environment settings in project files JetBrains · Junie 2 days ago high7.5 CVE-2026-133195 In JetBrains Junie CLI before 26.6.29 files outside the project directory could be modified by agent file tools JetBrains · Junie CLI 2 days ago high7.4 CVE-2026-133097 In JetBrains TeamCity before 2026.2.2, 2026.1.6 agent Push authorization keys were predictable JetBrains · TeamCity 2 days ago high7.1 CVE-2026-133096 In JetBrains TeamCity before 2026.2.2, 2026.1.6 improper authorization allowed queuing builds with personal changes of other users JetBrains · TeamCity 2 days ago high8.1 CVE-2026-133095 In JetBrains TeamCity before 2026.2.2, 2026.1.6 a CSRF attack was possible on the Hub integration settings JetBrains · TeamCity 2 days ago high7.7 CVE-2026-133094 In JetBrains TeamCity before 2026.2.2 missing authorization allowed project developers to read arbitrary HashiCorp Vault secrets JetBrains · TeamCity 2 days ago high7.2 CVE-2026-133093 In JetBrains TeamCity before 2026.2.2, 2026.1.6 code injection in parent project Kotlin DSL was possible via subproject settings JetBrains · TeamCity 2 days ago high8.8 CVE-2026-133092 In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Git submodule URLs JetBrains · TeamCity 2 days ago high8.0 CVE-2026-133091 In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS on the Users page was possible JetBrains · TeamCity 2 days ago high8.1 CVE-2026-133089 In JetBrains TeamCity before 2026.2.2, 2026.1.6 the TFS helper process exposed an unauthenticated command server JetBrains · TeamCity 2 days ago high7.2 CVE-2026-133090 In JetBrains TeamCity before 2026.2.2, 2026.1.6 improper authorization allowed overwriting versioned settings of other projects JetBrains · TeamCity 2 days ago high8.8 CVE-2026-133087 In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via a time zone callback in the Kotlin DSL sandbox JetBrains · TeamCity 2 days ago high7.2 CVE-2026-133088 In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via FreeMarker notification templates JetBrains · TeamCity 2 days ago high8.8 CVE-2026-133086 In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via a URL stream handler in the Kotlin DSL sandbox JetBrains · TeamCity 2 days ago high7.6 CVE-2026-133085 In JetBrains TeamCity before 2026.2.2, 2026.1.6 an XXE was possible in the TFS helper process JetBrains · TeamCity 2 days ago high7.7 CVE-2026-133084 In JetBrains TeamCity before 2026.2.2, 2026.1.6 vCS root credentials could be exposed via change viewer links JetBrains · TeamCity 2 days ago high7.5 CVE-2026-133082 In JetBrains TeamCity before 2026.2.2, 2026.1.6 a DoS attack was possible via unauthenticated multipart requests JetBrains · TeamCity 2 days ago high8.0 CVE-2026-133083 In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS in Server Health reports was possible JetBrains · TeamCity 2 days ago high7.5 CVE-2026-133081 In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Git VCS root URLs JetBrains · TeamCity 2 days ago high7.2 CVE-2026-133079 In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Maven dependencies of Kotlin DSL settings JetBrains · TeamCity 2 days ago high8.8 CVE-2026-133080 In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Maven repository settings JetBrains · TeamCity 2 days ago 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 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-133022 In JetBrains TeamCity before 2026.2.1 remote code execution was possible via the Notification Rules form 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.