NetSight

Security Dashboard

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

Reset
280 matching advisories · page 7 of 10Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.6 CVE-2025-53959 In JetBrains YouTrack before 2025.2.86069, 2024.3.85077, 2025.1.86199 email spoofing via an administrative API was possible jetbrains · youtrack 2025-07-15 high7.7 CVE-2025-48391 In JetBrains YouTrack before 2025.1.76253 deletion of issues was possible due to missing permission checks in API jetbrains · youtrack 2025-05-20 high8.3 CVE-2025-43015 In JetBrains RubyMine before 2025.1 remote Interpreter overwrote ports to listen on all interfaces jetbrains · rubymine 2025-04-17 high8.3 CVE-2025-43012 In JetBrains Toolbox App before 2.6 command injection in SSH plugin was possible jetbrains · toolbox 2025-04-17 high7.7 CVE-2025-26492 In JetBrains TeamCity before 2024.12.2 improper Kubernetes connection settings could expose sensitive resources jetbrains · teamcity 2025-02-11 high7.8 CVE-2025-23385 In JetBrains ReSharper before 2024.3.4, 2024.2.8, and 2024.1.7, Rider before 2024.3.4, 2024.2.8, and 2024.1.7, dotTrace before 2024.3.4, 2024.2.8, and 2024.1.7… jetbrains · dottrace, jetbrains · etw_host_service, jetbrains · resharper +1 2025-01-28 high7.1 CVE-2025-24458 In JetBrains YouTrack before 2024.3.55417 account takeover was possible via spoofed email and Helpdesk integration jetbrains · youtrack 2025-01-21 high8.0 CVE-2024-54154 In JetBrains YouTrack before 2024.3.51866 system takeover was possible through path traversal in plugin sandbox jetbrains · youtrack 2024-12-04 high8.1 CVE-2024-49579 In JetBrains YouTrack before 2024.3.47197 insecure plugin iframe allowed arbitrary JavaScript execution and unauthorized API requests jetbrains · youtrack 2024-10-17 high7.5 CVE-2024-43114 In JetBrains TeamCity before 2024.07.1 possible privilege escalation due to incorrect directory permissions jetbrains · teamcity 2024-08-06 high7.4 CVE-2024-41827 In JetBrains TeamCity before 2024.07 access tokens could continue working after deletion or expiration jetbrains · teamcity 2024-07-22 high8.1 CVE-2024-36470 In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 authentication bypass was possible in specific edge cases jetbrains · teamcity 2024-05-29 high7.4 CVE-2024-31136 In JetBrains TeamCity before 2024.03 2FA could be bypassed by providing a special URL parameter jetbrains · teamcity 2024-03-28 high7.3 CVE-2024-27199 JetBrains TeamCity Relative Path Traversal VulnerabilityExploited jetbrains · teamcity 2024-03-04 high8.6 CVE-2023-45612 In JetBrains Ktor before 2.3.5 default configuration of ContentNegotiation with XML format was vulnerable to XXE jetbrains · ktor 2023-10-09 high7.5 CVE-2023-35053 In JetBrains YouTrack before 2023.1.10518 a DoS attack was possible via Helpdesk forms jetbrains · youtrack 2023-06-12 high7.5 CVE-2022-48476 In JetBrains Ktor before 2.3.0 path traversal in the `resolveResource` method was possible jetbrains · ktor 2023-04-24 high7.1 CVE-2022-46829 In JetBrains JetBrains Gateway before 2022.3 a client could connect without a valid token if the host consented. jetbrains · jetbrains_gateway 2022-12-08 high7.5 CVE-2022-40978 The installer of JetBrains IntelliJ IDEA before 2022.2.2 was vulnerable to EXE search order hijacking jetbrains · intellij_idea 2022-09-19 high8.7 CVE-2022-29930 SHA1 implementation in JetBrains Ktor Native 2.0.0 was returning the same value. jetbrains · ktor 2022-05-12 high8.4 CVE-2022-28651 In JetBrains IntelliJ IDEA before 2021.3.3 it was possible to get passwords from protected fields jetbrains · intellij_idea 2022-04-05 high7.3 CVE-2022-28650 In JetBrains YouTrack before 2022.1.43700 it was possible to inject JavaScript into Markdown in the YouTrack Classic UI jetbrains · youtrack 2022-04-05 high7.5 CVE-2022-25264 In JetBrains TeamCity before 2021.2.3, environment variables of the "password" type could be logged in some cases. jetbrains · teamcity 2022-02-25 high7.8 CVE-2022-24346 In JetBrains IntelliJ IDEA before 2021.3.1, local code execution via RLO (Right-to-Left Override) characters was possible. jetbrains · intellij_idea 2022-02-25 high7.8 CVE-2022-24345 In JetBrains IntelliJ IDEA before 2021.2.4, local code execution (without permission from a user) upon opening a project was possible. jetbrains · intellij_idea 2022-02-25 high8.8 CVE-2022-24342 In JetBrains TeamCity before 2021.2.1, URL injection leading to CSRF was possible. jetbrains · teamcity 2022-02-25 high7.5 CVE-2022-24341 In JetBrains TeamCity before 2021.2.1, editing a user account to change its password didn't terminate sessions of the edited user. jetbrains · teamcity 2022-02-25 high8.1 CVE-2022-24335 JetBrains TeamCity before 2021.2 was vulnerable to a Time-of-check/Time-of-use (TOCTOU) race-condition attack in agent registration via XML-RPC. jetbrains · teamcity 2022-02-25 high7.5 CVE-2022-24327 In JetBrains Hub before 2021.1.13890, integration with JetBrains Account exposed an API key with excessive permissions. jetbrains · hub 2022-02-25 high7.5 CVE-2021-43182 In JetBrains Hub before 2021.1.13415, a DoS via user information is possible. jetbrains · hub 2021-11-09

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.