NetSight

Security Dashboard

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

Reset
126 matching advisories · page 2 of 5Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.7 CVE-2026-56725 Zammad is a web based open source helpdesk/customer support system. 57 days ago low2.1 CVE-2026-56729 Zammad is a web based open source helpdesk/customer support system. 57 days ago high7.1 CVE-2026-56724 Zammad is a web based open source helpdesk/customer support system. 57 days ago high7.1 CVE-2026-56723 Zammad is a web based open source helpdesk/customer support system. 57 days ago critical GHSA-ghc3-w668-w9gj Malicious code in eslint-plugin-zammad (npm)Malware npm · eslint-plugin-zammad, npm · eslint-plugin-zammad 2026-09-10 high7.1 CVE-2026-13229 Zammad 7.1.0 contains an authenticated improper authorization vulnerability in the ticket article attachment cloning endpoint. 2026-08-04 medium4.3 CVE-2026-34837 Zammad is a web based open source helpdesk/customer support system. zammad · zammad 2026-04-08 medium4.3 CVE-2026-34782 Zammad is a web based open source helpdesk/customer support system. zammad · zammad 2026-04-08 high7.2 CVE-2026-34724 Zammad is a web based open source helpdesk/customer support system. zammad · zammad 2026-04-08 high7.5 CVE-2026-34723 Zammad is a web based open source helpdesk/customer support system. zammad · zammad 2026-04-08 medium4.3 CVE-2026-34722 Zammad is a web based open source helpdesk/customer support system. zammad · zammad 2026-04-08 medium6.5 CVE-2026-34721 Zammad is a web based open source helpdesk/customer support system. zammad · zammad 2026-04-08 medium4.3 CVE-2026-34720 Zammad is a web based open source helpdesk/customer support system. zammad · zammad 2026-04-08 medium4.3 CVE-2026-34719 Zammad is a web based open source helpdesk/customer support system. zammad · zammad 2026-04-08 medium6.1 CVE-2026-34718 Zammad is a web based open source helpdesk/customer support system. zammad · zammad 2026-04-08 medium5.7 CVE-2026-34248 Zammad is a web based open source helpdesk/customer support system. zammad · zammad 2026-04-08 medium4.2 CVE-2025-32360 In Zammad 6.4.x before 6.4.2, there is information exposure. zammad · zammad 2025-04-05 medium4.8 CVE-2025-32359 In Zammad 6.4.x before 6.4.2, there is client-side enforcement of server-side security. zammad · zammad 2025-04-05 medium4.0 CVE-2025-32358 In Zammad 6.4.x before 6.4.2, SSRF can occur. zammad · zammad 2025-04-05 medium4.3 CVE-2025-32357 In Zammad 6.4.x before 6.4.2, an authenticated agent with knowledge base permissions was able to use the Zammad API to fetch knowledge base content that they h… zammad · zammad 2025-04-05 medium4.3 CVE-2024-55578 Zammad before 6.4.1 places sensitive data (such as auth_microsoft_office365_credentials and application_secret) in log files. zammad · zammad 2024-12-09 medium6.7 CVE-2024-36078 In Zammad before 6.3.1, a Ruby gem bundled by Zammad is installed with world-writable file permissions. zammad · zammad 2024-05-19 critical9.1 CVE-2024-33668 An issue was discovered in Zammad before 6.3.0. zammad · zammad 2024-04-26 medium6.5 CVE-2024-33667 An issue was discovered in Zammad before 6.3.0. zammad · zammad 2024-04-26 high8.6 CVE-2024-33666 An issue was discovered in Zammad before 6.3.0. zammad · zammad 2024-04-26 medium4.3 CVE-2023-50457 An issue was discovered in Zammad before 6.2.0. zammad · zammad 2023-12-10 medium5.3 CVE-2023-50456 An issue was discovered in Zammad before 6.2.0. zammad · zammad 2023-12-10 high7.5 CVE-2023-50455 An issue was discovered in Zammad before 6.2.0. zammad · zammad 2023-12-10 medium5.9 CVE-2023-50454 An issue was discovered in Zammad before 6.2.0. zammad · zammad 2023-12-10 medium5.3 CVE-2023-50453 An issue was discovered in Zammad before 6.2.0. zammad · zammad 2023-12-10

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.