NetSight

Security Dashboard

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

Reset
44 matching advisories · page 1 of 2Index updated 12 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.1 CVE-2026-119129 ZITADEL 3.0.0 through 3.4.15 and 4.0.0 before 4.19.5 contains a missing authorization vulnerability in Login V2 that allows attackers to approve OAuth 2.0 devi… ZITADEL, 4.0.0 23 days ago high8.6 CVE-2026-119127 ZITADEL 4.0.0 before 4.19.5 contains a host header injection vulnerability in the Login V2 UI that allows unauthenticated attackers to poison password-reset, i… zitadel · zitadel 23 days ago high8.1 CVE-2026-109373 ZITADEL 3.0.0 before 4.19.2 contains an authentication bypass vulnerability in the Login V2 UI that allows unauthenticated attackers to obtain other users' ses… ZITADEL 40 days ago high8.7 CVE-2026-109372 ZITADEL 4.x before 4.19.2 and 3.x through 3.4.15 contains an authentication bypass in the SAML identity-provider intent callback, which verifies the assertion … ZITADEL, 3.x 40 days ago high8.2 CVE-2026-109371 ZITADEL 3.0.0 before 4.18.0 contains a missing authentication vulnerability in the hosted Login V1 UI, where the change-username handler acts on the account bo… ZITADEL 40 days ago high8.2 CVE-2026-105213 ZITADEL 4.x before 4.17.1 does not check an organization's inactive state during Login V2 authentication, verifying only the individual user's status. ZITADEL 48 days ago high7.5 CVE-2026-105212 ZITADEL 3.x before 3.4.14 and 4.x before 4.16.2 contains an authentication bypass in the hosted Login V1 and Login V2 UIs that accepts passkey or other authent… ZITADEL, 4.x 48 days ago high8.1 CVE-2026-105211 ZITADEL before 4.17.1 contains an authentication bypass vulnerability in Login V2 that allows unauthenticated attackers to take over accounts by obtaining OTP … ZITADEL 48 days ago high8.2 CVE-2026-105210 ZITADEL 3.x before 3.4.15 and 4.x before 4.17.1 contains a missing authentication flaw in the hosted Login V1 UI, whose second-factor enrollment and initializa… ZITADEL, 4.x 48 days ago high7.7 CVE-2026-105208 ZITADEL 4.x before 4.17.3 and 3.x through 3.4.15 protects IdP intent tokens with unauthenticated, malleable encryption, allowing authenticated users to tamper … ZITADEL, 3.x 48 days ago high8.7 CVE-2026-85057 ZITADEL: Actions V1 sandbox escape: host file read via require() go · github.com/zitadel/zitadel 58 days ago high8.2 CVE-2026-85056 ZITADEL is an open source identity management platform. go · github.com/zitadel/zitadel 58 days ago high8.2 CVE-2026-54693 ZITADEL is an open source identity management platform. go · github.com/zitadel/zitadel 2026-07-29 high8.1 CVE-2026-56668 ZITADEL: Unauthorized Token Privilege Escalation in OAuth2 Token Exchange go · github.com/zitadel/zitadel 2026-07-10 high7.3 CVE-2026-56667 ZITADEL is an open source identity management platform. ZITADEL is an open source identity management platform. 2026-07-10 high7.4 CVE-2026-55672 ZITADEL: Missing client_id binding in OIDC authorization code exchange and refresh token flows (RFC 6749 Section 4.1.3 violation) go · github.com/zitadel/zitadel 2026-06-18 high7.5 CVE-2026-44671 ZITADEL is an open source identity management platform. go · github.com/zitadel/zitadel 2026-05-08 high7.4 CVE-2026-32132 ZITADEL is an open source identity management platform. zitadel · zitadel 2026-03-11 high7.7 CVE-2026-32131 ZITADEL is an open source identity management platform. zitadel · zitadel 2026-03-11 high7.5 CVE-2026-32130 ZITADEL is an open source identity management platform. zitadel · zitadel 2026-03-11 high7.7 CVE-2026-29192 ZITADEL: Stored XSS via Default URI Redirect Leads to Account Takeover go · github.com/zitadel/zitadel/v2, go · github.com/zitadel/zitadel 2026-03-04 high8.2 CVE-2026-29193 ZITADEL: Login V2 UI Policy Bypass Allows Unauthorized Self-Registration and Authentication go · github.com/zitadel/zitadel/v2, go · github.com/zitadel/zitadel 2026-03-04 high8.2 CVE-2026-27946 ZITADEL Users Can Self-Verify Email/Phone via UpdateHumanUser API go · github.com/zitadel/zitadel 2026-02-26 high8.0 CVE-2025-67495 ZITADEL Vulnerable to Account Takeover via DOM-Based XSS in Zitadel V2 Login go · github.com/zitadel/zitadel, go · github.com/zitadel/zitadel/v2 2025-12-08 high8.1 CVE-2026-29067 ZITADEL Vulnerable to Account Takeover Due to Improper Instance Validation in V2 Login go · github.com/zitadel/zitadel, go · github.com/zitadel/zitadel/v2 2025-12-08 high8.7 CVE-2025-64431 IDOR Vulnerabilities in ZITADEL's Organization API allows Cross-Tenant Data Tempering go · github.com/zitadel/zitadel 2025-11-05 high8.1 CVE-2025-64101 ZITADEL Vulnerable to Account Takeover via Malicious Forwarded Header Injection go · github.com/zitadel/zitadel/v2 2025-10-29 high8.8 CVE-2025-53895 ZITADEL is an open source identity management system. zitadel · zitadel 2025-07-15 high8.1 CVE-2025-48936 ZITADEL Allows Account Takeover via Malicious X-Forwarded-Proto Header Injection go · github.com/zitadel/zitadel, go · github.com/zitadel/zitadel/v2 2025-05-28 high8.0 CVE-2025-46815 ZITADEL Allows IdP Intent Token Reuse go · github.com/zitadel/zitadel 2025-05-06

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.