NetSight

Security Dashboard

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

Reset
277 matching advisories · page 1 of 10Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2026-42006 An attacker can cause uncontrolled memory usage with excessive bracing over IMAP. dovecot · dovecot, open-xchange · dovecot 2026-05-12 low3.1 CVE-2026-40020 Attacker can use the IMAP SETACL command to inject the anyone permission to user's dovecot-acl file even if imap_acl_allow_anyone=no. dovecot · dovecot, open-xchange · dovecot 2026-05-12 medium5.3 CVE-2026-40016 Attacker can upload a malicious Sieve script over ManageSieve service (or locally) to bypass configured CPU time limits for Sieve up to 130 times of the config… dovecot · dovecot, open-xchange · dovecot 2026-05-12 medium6.8 CVE-2026-33603 Attacker can use a specially crafted base64 exchange between Dovecot and Client to fake SCRAM TLS channel binding. dovecot · dovecot, open-xchange · dovecot 2026-05-12 high7.4 CVE-2026-27851 When safe filter is used with variable expansion, all following pipelines on the same string are incorrectly interpreted as safe too, enabling unsafe data to b… dovecot · dovecot, open-xchange · dovecot 2026-05-12 low3.7 CVE-2026-27860 If auth_username_chars is empty, it is possible to inject arbitrary LDAP filter to Dovecot's LDAP authentication. dovecot · dovecot, open-xchange · dovecot 2026-03-27 medium5.3 CVE-2026-27859 A mail message containing excessive amount of RFC 2231 MIME parameters causes LMTP to use too much CPU. dovecot · dovecot, open-xchange · dovecot 2026-03-27 high7.5 CVE-2026-27858 Attacker can send a specifically crafted message before authentication that causes managesieve to allocate large amount of memory. dovecot · dovecot, open-xchange · dovecot 2026-03-27 medium4.3 CVE-2026-27857 Sending "NOOP (((...)))" command with 4000 parenthesis open+close results in ~1MB extra memory usage. dovecot · dovecot, open-xchange · dovecot 2026-03-27 high7.4 CVE-2026-27856 Doveadm credentials are verified using direct comparison which is susceptible to timing oracle attack. dovecot · dovecot, open-xchange · dovecot 2026-03-27 medium6.8 CVE-2026-27855 Dovecot OTP authentication is vulnerable to replay attack under specific conditions. dovecot · dovecot, open-xchange · dovecot 2026-03-27 high7.7 CVE-2026-24031 Dovecot SQL based authentication can be bypassed when auth_username_chars is cleared by admin. dovecot · dovecot, open-xchange · dovecot 2026-03-27 medium5.3 CVE-2026-0394 When dovecot has been configured to use per-domain passwd files, and they are placed one path component above /etc, or slash has been added to allowed characte… dovecot · dovecot, open-xchange · dovecot 2026-03-27 high7.5 CVE-2025-59032 ManageSieve AUTHENTICATE command crashes when using literal as SASL initial response. dovecot · dovecot, open-xchange · dovecot 2026-03-27 medium4.3 CVE-2025-59031 Dovecot has provided a script to use for attachment to text conversion. dovecot · dovecot, open-xchange · dovecot 2026-03-27 medium5.3 CVE-2025-59028 When sending invalid base64 SASL data, login process is disconnected from the auth server, causing all active authentication sessions to fail. dovecot · dovecot, open-xchange · dovecot 2026-03-27 high8.8 CVE-2024-4367 PDF.js vulnerable to arbitrary JavaScript execution upon opening a malicious PDF npm · pdfjs-dist 2024-05-07 medium5.3 CVE-2024-23193 E-Mails exported as PDF were stored in a cache that did not consider specific session information for the related user account. open-xchange · ox_app_suite 2024-05-06 medium6.5 CVE-2024-23187 Content-ID based embedding of resources in E-Mails could be abused to trigger client-side script code when using the "show more" option. open-xchange · ox_app_suite 2024-05-06 medium6.5 CVE-2024-23186 E-Mail containing malicious display-name information could trigger client-side script execution when using specific mobile devices. open-xchange · ox_app_suite 2024-05-06 medium5.4 CVE-2023-41708 References to the "app loader" functionality could contain redirects to unexpected locations. open-xchange · open-xchange_appsuite 2024-02-12 medium6.5 CVE-2023-41707 Processing of user-defined mail search expressions is not limited. open-xchange · open-xchange_appsuite 2024-02-12 medium6.5 CVE-2023-41706 Processing time of drive search expressions now gets monitored, and the related request is terminated if a resource threshold is reached. open-xchange · open-xchange_appsuite 2024-02-12 medium6.5 CVE-2023-41705 Processing of user-defined DAV user-agent strings is not limited. open-xchange · open-xchange_appsuite 2024-02-12 high7.1 CVE-2023-41704 Processing of CID references at E-Mail can be abused to inject malicious script code that passes the sanitization engine. open-xchange · open-xchange_appsuite 2024-02-12 medium6.1 CVE-2023-41703 User ID references at mentions in document comments were not correctly sanitized. open-xchange · open-xchange_appsuite 2024-02-12 medium5.4 CVE-2023-41710 User-defined script code could be stored for a upsell related shop URL. open-xchange · ox_app_suite 2024-01-08 medium5.4 CVE-2023-29052 Users were able to define disclaimer texts for an upsell shop dialog that would contain script code that was not sanitized correctly. open-xchange · ox_app_suite 2024-01-08 high8.1 CVE-2023-29051 User-defined OXMF templates could be used to access a limited part of the internal OX App Suite Java API. open-xchange · ox_app_suite 2024-01-08 high7.6 CVE-2023-29050 The optional "LDAP contacts provider" could be abused by privileged users to inject LDAP filter strings that allow to access content outside of the intended hi… open-xchange · ox_app_suite 2024-01-08

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.