NetSight

Security Dashboard

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

Reset
79 matching advisories · page 3 of 3Index updated 14 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high6.8 CVE-2024-47060 ZITADEL Allows Unauthorized Access After Organization or Project Deactivation go · github.com/zitadel/zitadel/v2 2024-09-19 high8.1 CVE-2024-47000 ZITADEL's Service Users Deactivation not Working go · github.com/zitadel/zitadel/v2 2024-09-19 high7.3 CVE-2024-46999 ZITADEL's User Grant Deactivation not Working go · github.com/zitadel/zitadel/v2 2024-09-19 medium4.3 CVE-2024-41953 ZITADEL has improper HTML sanitization in emails and Console UI go · github.com/zitadel/zitadel 2024-07-31 medium5.3 CVE-2024-41952 ZITADEL "ignoring unknown usernames" vulnerability go · github.com/zitadel/zitadel 2024-07-31 medium5.3 GHSA-qc6v-5g5m-8cw2 ZITADEL Go's GRPC example code vulnerability - GO-2024-2687 HTTP/2 CONTINUATION flood in net/http go · github.com/zitadel/zitadel-go/v3 2024-07-15 medium5.7 CVE-2024-39683 ZITADEL Vulnerable to Session Information Leakage go · github.com/zitadel/zitadel 2024-07-03 medium5.3 CVE-2024-32967 Zitadel exposing internal database user name and host information go · github.com/zitadel/zitadel 2024-05-01 high6.5 CVE-2024-32868 ZITADEL's Improper Lockout Mechanism Leads to MFA Bypass go · github.com/zitadel/zitadel 2024-04-25 high6.1 CVE-2024-29892 ZITADEL's actions can overload reserved claims go · github.com/zitadel/zitadel 2024-03-27 high8.7 CVE-2024-29891 ZITADEL's Improper Content-Type Validation Leads to Account Takeover via Stored XSS + CSP Bypass go · github.com/zitadel/zitadel 2024-03-27 high8.1 CVE-2024-28855 Improper HTML sanitization in ZITADEL go · github.com/zitadel/zitadel 2024-03-18 high7.5 CVE-2024-28197 Account Takeover via Session Fixation in Zitadel [Bypassing MFA] go · github.com/zitadel/zitadel 2024-03-11 high8.1 CVE-2023-49097 ZITADEL Account Takeover via Malicious Host Header Injection go · github.com/zitadel/zitadel 2023-11-29 high7.3 CVE-2023-47111 ZITADEL race condition in lockout policy execution go · github.com/zitadel/zitadel 2023-11-08 high8.7 CVE-2023-46238 ZITADEL is an identity infrastructure management system. zitadel · zitadel 2023-10-26 medium5.3 CVE-2023-44399 ZITADEL's password reset does not respect the "Ignoring unknown usernames" setting go · github.com/zitadel/zitadel 2023-10-10 medium5.9 CVE-2023-22492 Zitadel RefreshToken invalidation vulnerability go · github.com/zitadel/zitadel 2023-01-11 high8.7 CVE-2022-36051 Broken Authorization in ZITADEL Actions go · github.com/zitadel/zitadel 2022-08-30

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.