NetSight

Security Dashboard

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

Reset
11,260 matching advisories · page 3 of 376Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
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 medium6.4 CVE-2026-120404 The built-in regular expression name finder for latitude and longitude coordinates uses a pattern that is vulnerable to excessive backtracking. Apache Software Foundation · Apache OpenNLP 2 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 medium6.8 CVE-2026-132982 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the build Report Tab dialog was possible JetBrains · TeamCity 3 days ago medium6.8 CVE-2026-132978 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in agent requirements was possible JetBrains · TeamCity 3 days ago medium6.8 CVE-2026-132976 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Inspections (IntelliJ IDEA) build step editor was possible JetBrains · TeamCity 3 days ago medium6.8 CVE-2026-132974 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Promote build dialog for dependent builds was possible JetBrains · TeamCity 3 days ago medium6.8 CVE-2026-132970 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Finish Build Trigger editor was possible JetBrains · TeamCity 3 days ago medium6.8 CVE-2026-132967 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the build Issues tab was possible JetBrains · TeamCity 3 days ago medium5.4 CVE-2026-132968 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Large Build Log health report was possible JetBrains · TeamCity 3 days ago medium5.4 CVE-2026-132966 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in build statistics charts was possible JetBrains · TeamCity 3 days ago medium5.9 CVE-2026-132959 In JetBrains TeamCity before 2026.2 remote code execution on build agents was possible via service message injection in build configuration names JetBrains · TeamCity 3 days ago medium5.4 CVE-2026-132956 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Build Features page was possible JetBrains · TeamCity 3 days ago medium4.8 CVE-2026-132953 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the queued build Overview tab was possible JetBrains · TeamCity 3 days ago medium6.1 CVE-2026-132948 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Build Chains tab was possible JetBrains · TeamCity 3 days ago medium6.1 CVE-2026-132943 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Build Log page was possible JetBrains · TeamCity 3 days ago medium5.3 CVE-2026-132942 In JetBrains TeamCity before 2026.2, 2026.1.4 unauthenticated extraction of build parameter values via a timing attack on build status icons was possible JetBrains · TeamCity 3 days ago medium4.3 CVE-2026-132941 In JetBrains TeamCity before 2026.2, 2026.1.4 missing authorization allowed users to remove all build configuration assignments from an agent JetBrains · TeamCity 3 days ago medium6.1 CVE-2026-132932 In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS in the build log tree view was possible JetBrains · TeamCity 3 days ago medium6.1 CVE-2026-132930 In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS in build problem details was possible JetBrains · TeamCity 3 days ago medium6.1 CVE-2026-132931 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the build feature parameters page was possible JetBrains · TeamCity 3 days ago medium5.4 CVE-2026-132924 In JetBrains TeamCity before 2026.2, 2026.1.4 improper authorization allowed users with the Run build permission to delete Perforce workspaces JetBrains · TeamCity 3 days ago medium4.8 CVE-2026-132923 In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the SSH Agent build feature key chooser was possible JetBrains · TeamCity 3 days ago medium6.5 CVE-2026-2307 The Elementor Website Builder – More Than Just a Page Builder plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and i… elemntor · Elementor Agent Ready Website Builder 3 days ago medium5.3 CVE-2026-132608 A vulnerability was identified in SECUDOCX DMP up to 9.0.0 Build 1027. This affects an unknown... SECUDOCX · DMP 3 days ago medium4.3 CVE-2026-69139 djangocms-moderation provides an approval workflow mechanism for organizations that require content approval before publication. pip · djangocms-moderation 3 days ago medium4.8 CVE-2026-132249 In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS in the Shared Resources build feature was possible JetBrains · TeamCity 3 days ago medium4.3 CVE-2026-132247 In JetBrains TeamCity before 2026.1.3, 2025.11.7 improper authorization allowed viewing build process details via agent stacktraces JetBrains · TeamCity 3 days ago medium4.3 CVE-2026-18045 Mattermost versions 11.11.x <= 11.11.0, 11.7.x <= 11.7.11, 11.10.x <= 11.10.2 fail to enforce the MFA requirement on the update and delete user endpoints, whic… Mattermost · Mattermost 3 days ago medium6.1 CVE-2010-20126 Virtual Keyboard plugin for SquirrelMail through 0.9.1 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject … Daniel K. Imori · Virtual Keyboard plugin for SquirrelMail 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.