Zero-Day & Vulnerability Intelligence Hub
Echtzeit-Tracking mit EPSS Exploit-Wahrscheinlichkeiten, Angriffsvektor-Decodern und KI-Patch-Anleitungen.
📊 Historien-Charts — Criticals-Trend · Vendors · EPSS-Verteilung
| Tier | CVEs | Anteil | Δ 7 T |
|---|---|---|---|
| ≥90 % | 795 | 0,2 % | +8 |
| ≥50 % | 3.561 | 0,9 % | +3 |
| ≥10 % | 13.177 | 3,2 % | +12 |
| <10 % | 397.844 | 95,8 % | +1.738 |
⚙️ Advanced Researcher Filters (Lifecycle, Scores, EPSS, Exploit, Sort, Dynamics, Source, CWE) 2 aktiv
🗂️ …
CVE-2026-102884 | Connaisseur is an admission controller that integrates container image signature verification into a Kubernetes cluster. Prior to 3.11.1, the Cosign validator counts valid signature layers rather than distinct trust roots for trustRoot: "*" policies using an explicit threshold or an implicit require-all policy. An attacker who controls one configured trust root's signing key and can attach multiple signatures to an image can satisfy a threshold intended to r
Connaisseur is an admission controller that integrates container image signature verification into a Kubernetes cluster. Prior to 3.11.1, the Cosign validator counts valid signature layers rather than distinct trust roots for trustRoot: "*"
CVE-2026-133498 | A flaw has been found in mozilla-ai llamafile up to .0.10.5. This issue affects the function llamafile_open_zip of the file llamafile/llamafile.c of the component Container Parser. This manipulation of the argument size causes out-of-bounds read. The attack is possible to be carried out remotely. Upgrading to version 0.10.6 is capable of addressing this issue. Patch name: 5ac1c4dbb76737fee71a54922df95342c667ba6f. It is advisable to upgrade the affected compo
A flaw has been found in mozilla-ai llamafile up to .0.10.5. This issue affects the function llamafile_open_zip of the file llamafile/llamafile.c of the component Container Parser. This manipulation of the argument size causes out-of-bounds
CVE-2026-110779 | Netatalk is a Free and Open Source file server suite for Unix-like operating systems. From 3.1.0 until 4.5.2, sl_createCNIDArray in etc/afpd/spotlight.c assumes every element of kMDQueryItemArray points to an eight-byte uint64_t and copies sizeof(uint64_t) bytes from the indexed p->dd_talloc_array element without validating the element's talloc type or allocation size. An authenticated AFP client with access to a Spotlight-enabled volume can use FPSpotlightR
Netatalk is a Free and Open Source file server suite for Unix-like operating systems. From 3.1.0 until 4.5.2, sl_createCNIDArray in etc/afpd/spotlight.c assumes every element of kMDQueryItemArray points to an eight-byte uint64_t and copies
CVE-2026-129422 | Joomla Extension - joomlatools.com - Unauthenticated blind server-side request forgery in FILEman extension < 6.1.4 - The frontend file view did not restrict requested files to their container and passed URLs to the framework URL fetch, allowing unauthenticated attackers to make the server issue requests to arbitrary addresses, including internal network resources.
Joomla Extension - joomlatools.com - Unauthenticated blind server-side request forgery in FILEman extension < 6.1.4 - The frontend file view did not restrict requested files to their container and passed URLs to the framework URL fetch, all
CVE-2026-131242 | In Splunk SOAR versions below 8.8.0, a user that holds a role with the containers:view permission could access automation history for containers outside the label or tenant scope assigned to the user. This could expose action parameters, connector result summaries, and other investigation and response activity. The vulnerability is possible because the Splunk SOAR Representational State Transfer (REST) API checks the permission to view containers but does no
In Splunk SOAR versions below 8.8.0, a user that holds a role with the containers:view permission could access automation history for containers outside the label or tenant scope assigned to the user. This could expose action parameters, co
CVE-2026-131275 | In Splunk SOAR versions below 8.8.0, a user with container edit permission could supply timestamps when creating containers and artifacts through the Representational State Transfer (REST) API. This could alter the timeline shown to analysts and cause configured data retention strategies to delete affected records earlier than intended. The vulnerability is possible because the REST API accepts client-supplied values for timestamps that Splunk SOAR uses to o
In Splunk SOAR versions below 8.8.0, a user with container edit permission could supply timestamps when creating containers and artifacts through the Representational State Transfer (REST) API. This could alter the timeline shown to analyst
CVE-2026-131257 | In Splunk SOAR versions below 8.8.0, a user with permission to view and edit containers and at least one container label could set misleading user and app provenance on containers that the user creates and learn whether user IDs and installed app identifiers exist. The vulnerability is possible because the Representational State Transfer (REST) API accepts client-supplied values for server-managed container fields.
In Splunk SOAR versions below 8.8.0, a user with permission to view and edit containers and at least one container label could set misleading user and app provenance on containers that the user creates and learn whether user IDs and install
CVE-2026-131250 | In Splunk SOAR versions below 8.8.0, a user with permission to edit containers for an allowed label could forge the author attribution of container pins and access limited user details outside the expected authorization boundary. The Container Pin Representational State Transfer (REST) API does not prevent caller-provided author fields from reaching generic model binding, which lets the request reassign a pin author or query user-related data outside the exp
In Splunk SOAR versions below 8.8.0, a user with permission to edit containers for an allowed label could forge the author attribution of container pins and access limited user details outside the expected authorization boundary. The Contai
CVE-2026-131273 | In Splunk SOAR versions below 8.8.0, an authenticated user who holds a role with permission to view system settings but not assets could view asset, app, and container-label metadata in Ingestion filters. The vulnerability is possible because Splunk SOAR returns Ingestion filter metadata without applying asset authorization and tenant restrictions. For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/
In Splunk SOAR versions below 8.8.0, an authenticated user who holds a role with permission to view system settings but not assets could view asset, app, and container-label metadata in Ingestion filters. The vulnerability is possible becau
CVE-2026-131251 | In Splunk SOAR versions below 8.8.0, a user with permission to view and modify containers with an allowed label could add artifacts to containers that the user cannot view or modify. The vulnerability is possible because the Representational State Transfer (REST) API artifact-creation workflow does not preserve the authorization boundary for the selected container.
In Splunk SOAR versions below 8.8.0, a user with permission to view and modify containers with an allowed label could add artifacts to containers that the user cannot view or modify. The vulnerability is possible because the Representationa
CVE-2026-131247 | In Splunk SOAR versions below 8.8.0, an authenticated Splunk SOAR user with permission to edit and run playbooks could read action status and callback state from a playbook run outside the authorized container-label or tenant scope for that user. The vulnerability is possible because the playbook API uses mutable runtime context to identify a playbook run instead of preserving the server-provided context.
In Splunk SOAR versions below 8.8.0, an authenticated Splunk SOAR user with permission to edit and run playbooks could read action status and callback state from a playbook run outside the authorized container-label or tenant scope for that
CVE-2026-131241 | In Splunk SOAR versions below 8.8.0, a user with edit permission for containers on only a subset of container labels could modify container pins outside the container labels that the role permits. The vulnerability is possible because the Container Pin Representational State Transfer (REST) API does not enforce the container label authorization boundary when handling requests. For more information see Manage roles and permissions in Splunk SOAR (On-premises)
In Splunk SOAR versions below 8.8.0, a user with edit permission for containers on only a subset of container labels could modify container pins outside the container labels that the role permits. The vulnerability is possible because the C