NetSight

Security Dashboard

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

Reset
139 matching advisories · page 2 of 5Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2025-59462 An attacker who tampers with the C++ CLI client may crash the UpdateService during file transfers, disrupting updates and availability. sick · tloc100-100_firmware 2025-10-27 high7.6 CVE-2025-59461 A remote unauthenticated attacker may use the unauthenticated C++ API to access or modify sensitive data and disrupt services. sick · tloc100-100_firmware 2025-10-27 high7.5 CVE-2025-59460 The system is deployed in its default state, with configuration settings that do not comply with the latest best practices for restricting access. sick · tloc100-100_firmware 2025-10-27 medium5.5 CVE-2025-59459 An attacker that gains SSH access to an unprivileged account may be able to disrupt services (including SSH), causing persistent loss of availability. sick · tloc100-100_firmware 2025-10-27 medium4.3 CVE-2025-9914 The credentials of the users stored in the system's local database can be used for the log in, making it possible for an attacker to gain unauthorized access. sick · baggage_analytics, sick · logistic_diagnostic_analytics, sick · package_analytics +1 2025-10-06 medium4.5 CVE-2025-9913 JavaScript can be ran inside the address bar via the dashboard "Open in new Tab" Button, making the application vulnerable to session hijacking. sick · baggage_analytics, sick · logistic_diagnostic_analytics, sick · package_analytics +1 2025-10-06 medium6.5 CVE-2025-58591 A remote, unauthorized attacker can brute force folders and files and read them like private keys or configurations, making the application vulnerable for gath… sick · baggage_analytics, sick · logistic_diagnostic_analytics, sick · package_analytics +1 2025-10-06 medium6.5 CVE-2025-58590 It's possible to brute force folders and files, what can be used by an attacker to steal sensitve information. sick · baggage_analytics, sick · logistic_diagnostic_analytics, sick · package_analytics +1 2025-10-06 low2.7 CVE-2025-58589 When an error occurs in the application a full stacktrace is provided to the user. sick · baggage_analytics, sick · logistic_diagnostic_analytics, sick · package_analytics +1 2025-10-06 medium6.5 CVE-2025-58587 The application does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it possible for an … sick · baggage_analytics, sick · enterprise_analytics, sick · logistic_diagnostic_analytics +2 2025-10-06 medium5.3 CVE-2025-58586 For failed login attempts, the application returns different error messages depending on whether the login failed due to an incorrect password or a non-existin… sick · baggage_analytics, sick · enterprise_analytics, sick · logistic_diagnostic_analytics +2 2025-10-06 medium5.3 CVE-2025-58585 Multiple endpoints with sensitive information do not require authentication, making the application susceptible to information gathering. sick · baggage_analytics, sick · logistic_diagnostic_analytics, sick · package_analytics +1 2025-10-06 medium5.3 CVE-2025-58584 In the HTTP request, the username and password are transferred directly in the URL as parameters. sick · baggage_analytics, sick · enterprise_analytics, sick · logistic_diagnostic_analytics +2 2025-10-06 medium5.3 CVE-2025-58583 The application provides access to a login protected H2 database for caching purposes. sick · enterprise_analytics 2025-10-06 medium5.3 CVE-2025-58582 If a user tries to login but the provided credentials are incorrect a log is created. sick · enterprise_analytics 2025-10-06 medium4.3 CVE-2025-58581 When an error occurs in the application a full stacktrace is provided to the user. sick · enterprise_analytics 2025-10-06 medium6.5 CVE-2025-58580 An API endpoint allows arbitrary log entries to be created via POST request. sick · enterprise_analytics 2025-10-06 medium5.3 CVE-2025-58579 Due to a lack of authentication, it is possible for an unauthenticated user to request data from this endpoint, making the application vulnerable for user enum… sick · baggage_analytics, sick · enterprise_analytics, sick · logistic_diagnostic_analytics +2 2025-10-06 low3.8 CVE-2025-58578 A user with the appropriate authorization can create any number of user accounts via an API endpoint using a POST request. sick · enterprise_analytics 2025-10-06 medium6.5 CVE-2025-49200 The created backup files are unencrypted, making the application vulnerable for gathering sensitive information by downloading and decompressing the backup fil… sick · field_analytics 2025-06-12 high8.8 CVE-2025-49199 The backup ZIPs are not signed by the application, leading to the possibility that an attacker can download a backup ZIP, modify and re-upload it. sick · field_analytics 2025-06-12 low3.1 CVE-2025-49198 The Media Server’s authorization tokens have a poor quality of randomness. sick · media_server 2025-06-12 medium6.5 CVE-2025-49197 The application uses a weak password hash function, allowing an attacker to crack the weak password hash to gain access to an FTP user account. sick · media_server 2025-06-12 medium6.5 CVE-2025-49196 A service supports the use of a deprecated and unsafe TLS version. sick · field_analytics 2025-06-12 medium5.3 CVE-2025-49195 The FTP server’s login mechanism does not restrict authentication attempts, allowing an attacker to brute-force user passwords and potentially compromising the… sick · media_server 2025-06-12 high7.5 CVE-2025-49194 The server supports authentication methods in which credentials are sent in plaintext over unencrypted channels. sick · media_server 2025-06-12 medium4.2 CVE-2025-49193 The application fails to implement several security headers. sick · baggage_analytics, sick · field_analytics, sick · logistic_diagnostic_analytics +3 2025-06-12 medium4.3 CVE-2025-49192 The web application is vulnerable to clickjacking attacks. sick · field_analytics, sick · media_server 2025-06-12 medium4.8 CVE-2025-49191 Linked URLs during the creation of iFrame widgets and dashboards are vulnerable to code execution. sick · field_analytics 2025-06-12 medium4.3 CVE-2025-49190 The application is vulnerable to Server-Side Request Forgery (SSRF). sick · field_analytics 2025-06-12

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.