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.837 | 95,8 % | +1.738 |
⚙️ Erweiterte Forscher-Filter (Lifecycle, Scores, EPSS, Exploit, Sortierung, Dynamik, Quelle, CWE) 1 aktiv
🗂️ …
CVE-2026-131253 | In Splunk SOAR versions below 8.8.0, an authenticated user that holds a role with the Apps edit, Containers edit, and Playbooks execute permissions could use the App Wizard to execute arbitrary code as the user account that runs Splunk SOAR. This could compromise the confidentiality, integrity, and availability of the Splunk SOAR instance. The vulnerability exists because the App Wizard does not validate user-supplied identifiers before incorporating them in
In Splunk SOAR versions below 8.8.0, an authenticated user that holds a role with the Apps edit, Containers edit, and Playbooks execute permissions could use the App Wizard to execute arbitrary code as the user account that runs Splunk SOAR
CVE-2026-131287 | In Splunk SOAR versions below 8.8.0, a user that holds a role with the Playbooks view, edit, execute, and delete permissions could cause existing cross-repository playbook references to run attacker-controlled playbook code. The vulnerability is possible because Splunk SOAR can bind existing cross-repository playbook references to a different source control repository when a deleted repository name is reused.
In Splunk SOAR versions below 8.8.0, a user that holds a role with the Playbooks view, edit, execute, and delete permissions could cause existing cross-repository playbook references to run attacker-controlled playbook code. The vulnerabili
CVE-2026-131297 | In Splunk SOAR versions below 8.8.0, an operator of a configured identity provider could authenticate as an existing user associated with another configured identity provider. If that account has the "Administrator" Splunk SOAR role, the operator could control the Splunk SOAR deployment. Splunk SOAR does not bind external user accounts to the identity provider that provisions them and authenticates accounts by username without verifying provider ownership. T
In Splunk SOAR versions below 8.8.0, an operator of a configured identity provider could authenticate as an existing user associated with another configured identity provider. If that account has the "Administrator" Splunk SOAR role, the op
CVE-2026-131295 | In Splunk SOAR versions below 8.8.0, an authenticated user with permission to create and run playbooks could start child playbooks on containers outside the authorized label, or repository scope for that user. This could expose container data and affect automation outside that scope. The vulnerability is possible because Splunk SOAR does not bind the identity used to authorize the child playbook run to the parent playbook execution context.
In Splunk SOAR versions below 8.8.0, an authenticated user with permission to create and run playbooks could start child playbooks on containers outside the authorized label, or repository scope for that user. This could expose container da
CVE-2026-131271 | In Splunk SOAR versions below 8.8.0, an authenticated user with permission to view and edit containers for one label could use a slash command through the Representational State Transfer (REST) API to access sensitive product data and credentials outside the authorized container scope. The vulnerability is possible because Splunk SOAR does not enforce authorization for related objects that slash commands access from an authorized artifact.
In Splunk SOAR versions below 8.8.0, an authenticated user with permission to view and edit containers for one label could use a slash command through the Representational State Transfer (REST) API to access sensitive product data and crede
CVE-2026-131270 | In Splunk SOAR versions below 8.8.0, an authenticated user with repository edit access could cause Splunk SOAR to write files outside the configured repository, which lets the user modify files that the user account running Splunk SOAR can write to. The vulnerability is possible because Splunk SOAR does not require source control repository paths to remain inside the configured repository.
In Splunk SOAR versions below 8.8.0, an authenticated user with repository edit access could cause Splunk SOAR to write files outside the configured repository, which lets the user modify files that the user account running Splunk SOAR can
CVE-2026-131269 | In Splunk SOAR versions below 8.8.0, a user that holds a role with the Apps edit permission could cause Splunk SOAR to execute arbitrary code on the host when the user validates an installed app. The vulnerability is possible because the app validation workflow does not isolate untrusted code from the trusted environment.
In Splunk SOAR versions below 8.8.0, a user that holds a role with the Apps edit permission could cause Splunk SOAR to execute arbitrary code on the host when the user validates an installed app. The vulnerability is possible because the ap
CVE-2026-131263 | In Splunk SOAR versions below 8.8.0, a user that holds a role with only the apps:edit permission could install a connector app that causes Splunk SOAR to write attacker-controlled files outside the app directory. This could let the user modify files used by Splunk SOAR and execute arbitrary code as the user account that runs Splunk SOAR. The vulnerability is possible because Splunk SOAR constructs the dependency installation command from app-supplied metadat
In Splunk SOAR versions below 8.8.0, a user that holds a role with only the apps:edit permission could install a connector app that causes Splunk SOAR to write attacker-controlled files outside the app directory. This could let the user mod
CVE-2026-131261 | In Splunk SOAR versions below 8.8.0, a user that holds a role with the Apps edit permission could execute arbitrary code as the user account that runs Splunk SOAR by installing a malicious app. The vulnerability is possible because Splunk SOAR does not restrict app dependencies to validated binary packages before installing them.
In Splunk SOAR versions below 8.8.0, a user that holds a role with the Apps edit permission could execute arbitrary code as the user account that runs Splunk SOAR by installing a malicious app. The vulnerability is possible because Splunk S
CVE-2026-131252 | In Splunk SOAR versions below 8.8.0, a user that holds a role with the Assets edit or delete permission and access to one or more tenants could change or delete assets assigned to other tenants through the Representational State Transfer (REST) API. With this access, the user could redirect connector traffic and expose the credentials and operational data associated with an asset, or disrupt integrations and data ingestion for other tenants. The vulnerabilit
In Splunk SOAR versions below 8.8.0, a user that holds a role with the Assets edit or delete permission and access to one or more tenants could change or delete assets assigned to other tenants through the Representational State Transfer (R
CVE-2026-131246 | In Splunk SOAR versions below 8.8.0, an authenticated user with edit permission for the container label on a pending approval could read an external-prompt capability through an Approval details Representational State Transfer (REST) API response and use it to view the prompt content, change the pending approval decision, and modify its action parameters. The vulnerability is possible because an Approval details response exposes the external-prompt capabilit
In Splunk SOAR versions below 8.8.0, an authenticated user with edit permission for the container label on a pending approval could read an external-prompt capability through an Approval details Representational State Transfer (REST) API re
CVE-2026-131293 | In Splunk SOAR versions below 8.8.0, an authenticated user with permission to edit and run playbooks could read or overwrite persisted data for playbook runs outside the authorized label, or ownership scope for that user. The affected data can include playbook inputs, prompt and block results, outputs, and secrets that playbooks save in run data. Overwriting the data could corrupt results that paused, scheduled, or parent playbook runs later use. The vulnera
In Splunk SOAR versions below 8.8.0, an authenticated user with permission to edit and run playbooks could read or overwrite persisted data for playbook runs outside the authorized label, or ownership scope for that user. The affected data
CVE-2026-131282 | In Splunk SOAR versions below 8.8.0, a user who holds the "Observer" Splunk SOAR role could access a password-reset credential in a diagnostic log bundle and reset the password for an active local account. The vulnerability is possible because Splunk SOAR does not redact password-reset email bodies before it logs communications between product processes.
In Splunk SOAR versions below 8.8.0, a user who holds the "Observer" Splunk SOAR role could access a password-reset credential in a diagnostic log bundle and reset the password for an active local account. The vulnerability is possible beca
CVE-2026-131266 | In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission could cause Splunk SOAR to send a stored Elasticsearch password to a host that the user controls. The vulnerability is possible because Splunk SOAR reuses a stored Elasticsearch password for a changed Search Settings endpoint without requiring a replacement password.
In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission could cause Splunk SOAR to send a stored Elasticsearch password to a host that the user controls. The vulnerability is possible because S
CVE-2026-131243 | In Splunk SOAR versions below 8.8.0, an authenticated user with permission to view an affected container could query the Representational State Transfer (REST) API for approvals to retrieve a live external prompt link belonging to another user. Using this link, the user could read the approval prompt without authentication and submit a response, potentially disrupting or altering the automated workflow governed by that approval. The vulnerability is possible
In Splunk SOAR versions below 8.8.0, an authenticated user with permission to view an affected container could query the Representational State Transfer (REST) API for approvals to retrieve a live external prompt link belonging to another u
CVE-2026-131255 | In Splunk SOAR versions below 8.8.0, an unauthenticated user could gain administrator privileges through a user account that receives an unintended role. A user that holds a role with permission to create or modify users and assign roles must assign the target account a role with a numeric name through the user-management Representational State Transfer (REST) API. The vulnerability is possible because the API resolves a numeric role name as a role identifie
In Splunk SOAR versions below 8.8.0, an unauthenticated user could gain administrator privileges through a user account that receives an unintended role. A user that holds a role with permission to create or modify users and assign roles mu
CVE-2026-131272 | In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission could use the Automation Dependency Wheel Representational State Transfer (REST) API to write arbitrary files outside the intended directory, which could lead to arbitrary code execution. The vulnerability is possible because Splunk SOAR does not restrict uploaded automation dependency wheel filenames to the intended storage directory.
In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission could use the Automation Dependency Wheel Representational State Transfer (REST) API to write arbitrary files outside the intended direct
CVE-2026-131268 | In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission could use a customer automation dependency to execute arbitrary code as the user account that runs Splunk SOAR. The vulnerability is possible because Splunk SOAR does not properly separate customer automation dependencies from trusted product code.
In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission could use a customer automation dependency to execute arbitrary code as the user account that runs Splunk SOAR. The vulnerability is poss
CVE-2026-131260 | In Splunk SOAR versions below 8.8.0, a user with the containers:edit permission could import a container that includes a malicious Hypertext Markup Language (HTML) note. When another user views the imported note, Splunk SOAR could run unauthorized JavaScript in the browser of that user, exposing data and allowing actions available to that user. The vulnerability is possible because Splunk SOAR does not sanitize HTML note content during container import befor
In Splunk SOAR versions below 8.8.0, a user with the containers:edit permission could import a container that includes a malicious Hypertext Markup Language (HTML) note. When another user views the imported note, Splunk SOAR could run unaut
CVE-2026-131258 | In Splunk SOAR versions below 8.8.0, a user with edit permission for a container or workbook task could store attacker-controlled Hypertext Markup Language (HTML) in a note. When another user with view permission for the affected container and its notes opens the affected note in Mission Control, the note could run unauthorized JavaScript code in the browser of that user, expose data available through the authenticated session, and perform actions available
In Splunk SOAR versions below 8.8.0, a user with edit permission for a container or workbook task could store attacker-controlled Hypertext Markup Language (HTML) in a note. When another user with view permission for the affected container
CVE-2026-131256 | In Splunk SOAR versions below 8.8.0, an authenticated user that holds a role with the System Settings edit permission could execute arbitrary code on the host that runs Splunk SOAR. The vulnerability is possible because the Representational State Transfer (REST) API accepts package references from untrusted sources and passes them to the dependency installer.
In Splunk SOAR versions below 8.8.0, an authenticated user that holds a role with the System Settings edit permission could execute arbitrary code on the host that runs Splunk SOAR. The vulnerability is possible because the Representational
CVE-2026-131248 | In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission and restricted tenant access could modify settings for a tenant outside the role scope through the Representational State Transfer (REST) API. With this access, the user could expose confidential tenant environment values, alter tenant settings and automation behavior, or take the tenant out of operation. The vulnerability is possible because the Tenant RES
In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission and restricted tenant access could modify settings for a tenant outside the role scope through the Representational State Transfer (REST)
CVE-2026-131245 | In Splunk SOAR versions below 8.8.0, a user with edit permission for the container label of a pending external prompt could obtain the external prompt link through the Representational State Transfer (REST) API and use the link to view and resolve the associated approval. The vulnerability is possible because the approval detail REST API includes the external prompt link in responses outside the assigned approval scope. For more information see REST Approval
In Splunk SOAR versions below 8.8.0, a user with edit permission for the container label of a pending external prompt could obtain the external prompt link through the Representational State Transfer (REST) API and use the link to view and
CVE-2026-131285 | In Splunk SOAR versions below 8.8.0, an authenticated user who can edit and run playbooks could cause automation batches for other events to stop running. The vulnerability occurs because Splunk SOAR does not bind playbook API requests to the server-provided execution context.
In Splunk SOAR versions below 8.8.0, an authenticated user who can edit and run playbooks could cause automation batches for other events to stop running. The vulnerability occurs because Splunk SOAR does not bind playbook API requests to t
CVE-2026-131280 | In Splunk SOAR versions below 8.8.0, an authenticated user whose role grants system_settings:view but not assets:view could access asset and application inventory, tenant identifiers, connector run messages, and stored configuration snapshots through the ingestion status Representational State Transfer (REST) API. The vulnerability is possible because the ingestion status REST API checks the system_settings:view permission but does not enforce assets:view or
In Splunk SOAR versions below 8.8.0, an authenticated user whose role grants system_settings:view but not assets:view could access asset and application inventory, tenant identifiers, connector run messages, and stored configuration snapsho
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-131296 | In Splunk SOAR versions below 8.8.0, a user with permission to author and run playbooks could add messages to a different playbook run log and cause that run to fail, including runs outside the labels that the user could access. The vulnerability is possible because Splunk SOAR does not verify that playbook API requests use the trusted runtime context for the current playbook run.
In Splunk SOAR versions below 8.8.0, a user with permission to author and run playbooks could add messages to a different playbook run log and cause that run to fail, including runs outside the labels that the user could access. The vulnera
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-131288 | In Splunk SOAR versions below 8.8.0, a user with access to the configured load balancer account could replace a load balancer helper that Splunk SOAR later runs with root privileges during cluster lifecycle operations. If a Splunk SOAR administrator performs a cluster lifecycle operation, Splunk SOAR could execute arbitrary code with root privileges on the load balancer. The vulnerability is possible because Splunk SOAR does not verify the integrity or owner
In Splunk SOAR versions below 8.8.0, a user with access to the configured load balancer account could replace a load balancer helper that Splunk SOAR later runs with root privileges during cluster lifecycle operations. If a Splunk SOAR admi
CVE-2026-131278 | In Splunk SOAR versions below 8.8.0, a user with local access to the affected host could obtain a live Splunk SOAR session token or decrypted asset configuration when another user starts an App Editor debug action. The vulnerability is possible because App Editor debug actions expose sensitive runtime information to other local users on the affected host.
In Splunk SOAR versions below 8.8.0, a user with local access to the affected host could obtain a live Splunk SOAR session token or decrypted asset configuration when another user starts an App Editor debug action. The vulnerability is poss
CVE-2026-131298 | In Splunk SOAR versions below 8.8.0, an authenticated user with edit permission on a workbook could configure a service-level agreement at only the workbook phase or task level. Splunk SOAR then flags the task as overdue immediately and does not display the configured deadline in the work queue. The incorrect deadline status could obscure genuine deadline breaches. The vulnerability is possible because Splunk SOAR treats an absent phase-level or task-level s
In Splunk SOAR versions below 8.8.0, an authenticated user with edit permission on a workbook could configure a service-level agreement at only the workbook phase or task level. Splunk SOAR then flags the task as overdue immediately and doe
CVE-2026-131290 | In Splunk SOAR versions below 8.8.0, an authenticated user with permission to edit and run playbooks could view child playbook status and loop-state metadata for playbook runs outside the authorized scope for that user. The vulnerability is possible because the playbook status API does not bind the requested run to the current execution context before it returns metadata.
In Splunk SOAR versions below 8.8.0, an authenticated user with permission to edit and run playbooks could view child playbook status and loop-state metadata for playbook runs outside the authorized scope for that user. The vulnerability is
CVE-2026-131283 | In Splunk SOAR versions below 8.8.0, an authenticated user with playbook edit permission could cause later playbook conversions to include spurious branch conditions. This can prevent downstream blocks from running in affected converted playbooks. The vulnerability is possible because the playbook converter retains branch conditions from previous conversions.
In Splunk SOAR versions below 8.8.0, an authenticated user with playbook edit permission could cause later playbook conversions to include spurious branch conditions. This can prevent downstream blocks from running in affected converted pla
CVE-2026-131281 | In Splunk SOAR versions below 8.8.0, a user with asset edit permission could change the approval requirements and effective automation user for an asset without Splunk SOAR recording field-level audit details for those changes. This could weaken investigation and accountability for changes to security-sensitive asset settings. The vulnerability is possible because Splunk SOAR does not include the asset approval voting fields and effective automation user fie
In Splunk SOAR versions below 8.8.0, a user with asset edit permission could change the approval requirements and effective automation user for an asset without Splunk SOAR recording field-level audit details for those changes. This could w
CVE-2026-131276 | In Splunk SOAR versions below 8.8.0, an authenticated user that holds a role with the System Settings view permission but not the Assets view permission could view asset and tenant metadata in the ingestion history view. The ingestion history view does not restrict summary results to assets and tenants that the user can view.
In Splunk SOAR versions below 8.8.0, an authenticated user that holds a role with the System Settings view permission but not the Assets view permission could view asset and tenant metadata in the ingestion history view. The ingestion histo
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-131265 | In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings view permission but not the Assets view permission could view asset names, asset identifiers, app names, tenant names, and ingestion schedule settings for polling assets in the ingestion schedule view. The vulnerability is possible because the ingestion schedule view does not verify the Assets view permission before it returns data derived from assets.
In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings view permission but not the Assets view permission could view asset names, asset identifiers, app names, tenant names, and ingestion schedule settings fo
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
CVE-2026-131240 | In Splunk SOAR versions below 8.8.0, an authenticated user could cause Splunk SOAR to store excessive data in the Ingestion Status history through the Representational State Transfer (REST) API. When another user with permission to view system settings retrieves the Ingestion Status history, Splunk SOAR could use additional resources and return a larger response, which could degrade the availability of administrative monitoring. The vulnerability is possible
In Splunk SOAR versions below 8.8.0, an authenticated user could cause Splunk SOAR to store excessive data in the Ingestion Status history through the Representational State Transfer (REST) API. When another user with permission to view sys
Prioritizing CVE-2026-91510 in an Oracle Patch Cycle
Prioritizing CVE-2026-91510 in an Oracle Patch Cycle A patch cycle rarely has enough maintenance capacity for every finding at once. CVE-2026-91510 is still a strong candidate for early action because Oracle rates it 10.0, the attack path i
IT Security News Hourly Summary 2026-11-22 19h : 8 posts
8 posts published in the last hour 17:32Bell Canada Confirms Cyberattack Involving Theft of Enterprise Customer Data 17:31VirusTotal’s New Ransomware Detection Catches Malware Missed by All 75 Antivirus Engines 17:31Linux KVM Flaw CVE-2026-
IT Security News Roundup: 2026-11-22 Afternoon – VMware vCenter zero-day, PHP patches and Cleverbridge card theft
IT Security News: Afternoon roundup, 2026-11-22 Summary The 12:00–18:00 CET window was dominated by breaches and exposed data, with a critical zero-day in VMware vCenter standing out as the most serious technical threat. Several stories sho
CVE-2026-126977 | Philips Hue Bridge HomeKit Pair-Setup default password
A vulnerability marked as critical has been reported in Philips Hue Bridge. This affects an unknown part of the component HomeKit Pair-Setup. This manipulation causes use of default password. The identification of this vulnerability is CVE-
CVE-2026-126976 | llama.cpp GGUF File Parser integer overflow
A vulnerability identified as critical has been detected in llama.cpp. Impacted is an unknown function of the component GGUF File Parser. This manipulation causes integer overflow. The identification of this vulnerability is CVE-2026-126976
CVE-2026-126975 | llama.cpp GGUF File Parser heap-based overflow
A vulnerability was found in llama.cpp. It has been classified as critical. This affects an unknown function of the component GGUF File Parser. Performing a manipulation results in heap-based buffer overflow. This vulnerability is cataloged
CVE-2026-126974 | llama.cpp GGUF File Parser integer overflow
A vulnerability was found in llama.cpp. It has been declared as critical. This impacts an unknown function of the component GGUF File Parser. Executing a manipulation can lead to integer overflow. This vulnerability is registered as CVE-202
CVE-2026-126973 | KDE Gwenview PNG File Parser integer overflow
A vulnerability labeled as critical has been found in KDE Gwenview. The affected element is an unknown function of the component PNG File Parser. Such manipulation leads to integer overflow. This vulnerability is referenced as CVE-2026-1269
CVE-2026-126969 | SmarterTools SmarterMail entropy
A vulnerability marked as problematic has been reported in SmarterTools SmarterMail. Affected by this vulnerability is an unknown functionality. This manipulation causes insufficient entropy. This vulnerability is handled as CVE-2026-126969
CVE-2026-126968 | SmarterTools SmarterMail authorization
A vulnerability, which was classified as problematic, has been found in SmarterTools SmarterMail. This issue affects some unknown processing. The manipulation leads to missing authorization. This vulnerability is referenced as CVE-2026-1269
CVE-2026-126967 | SmarterTools SmarterMail path traversal
A vulnerability described as critical has been identified in SmarterTools SmarterMail. Affected by this issue is some unknown functionality. Such manipulation leads to path traversal. This vulnerability is uniquely identified as CVE-2026-12
CVE-2026-126966 | SmarterTools SmarterMail missing authentication
A vulnerability was found in SmarterTools SmarterMail and classified as critical. The impacted element is an unknown function. Such manipulation leads to missing authentication. This vulnerability is listed as CVE-2026-126966. The attack ma
CVE-2026-126965 | ATEN eco DC sql injection
A vulnerability, which was classified as critical, was found in ATEN eco DC. Impacted is an unknown function. The manipulation results in sql injection. This vulnerability is identified as CVE-2026-126965. The attack can be executed remotel
CVE-2026-126964 | ATEN eco DC fwDeletes.json path traversal
A vulnerability has been found in ATEN eco DC and classified as critical. The affected element is an unknown function of the file fwDeletes.json. This manipulation causes path traversal. This vulnerability is tracked as CVE-2026-126964. The
CVE-2026-126963 | Hinemos certificate validation
A vulnerability classified as problematic was found in Hinemos. This vulnerability affects unknown code. Executing a manipulation can lead to improper certificate validation. The identification of this vulnerability is CVE-2026-126963. The
CVE-2026-126962 | open62541 Subscription use after free
A vulnerability classified as critical has been found in open62541. This affects an unknown part of the component Subscription. Performing a manipulation results in use after free. This vulnerability was named CVE-2026-126962. The attack ma
Designing Network and Access Controls Around Splunk Cluster APIs
Designing Network and Access Controls Around Splunk Cluster APIs CVE-2026-76536 shows that authentication defects and network exposure must be assessed together. An affected standalone Splunk Enterprise instance with clustering disabled and