🔴 Live Security Advisory & EPSS Exploit Radar

Zero-Day & Vulnerability Intelligence Hub

Echtzeit-Tracking mit EPSS Exploit-Wahrscheinlichkeiten, Angriffsvektor-Decodern und KI-Patch-Anleitungen.

421k+ 🇪🇺 EUVD-Datenbank
0 🔴 Critical im Radar
0 ⚠️ CISA KEV
0 🔓 Aktiv ausgenutzt
0 🧪 PoC verfügbar
📊 Historien-Charts — Criticals-Trend · Vendors · EPSS-Verteilung
🔴 Criticals pro Monat (12 M) 2025-12: 426 Criticals, davon 9 KEV, Ø CVSS 9,6 Dez 25 2026-01: 433 Criticals, davon 10 KEV, Ø CVSS 9,6 2026-02: 419 Criticals, davon 4 KEV, Ø CVSS 9,5 Feb 26 2026-03: 652 Criticals, davon 6 KEV, Ø CVSS 9,5 2026-04: 578 Criticals, davon 5 KEV, Ø CVSS 9,5 Apr 26 2026-05: 683 Criticals, davon 13 KEV, Ø CVSS 9,5 2026-06: 944 Criticals, davon 14 KEV, Ø CVSS 9,6 Jun 26 2026-07: 1329 Criticals, davon 13 KEV, Ø CVSS 9,6 2026-08: 1830 Criticals, davon 11 KEV, Ø CVSS 9,5 Aug 26 2026-09: 1551 Criticals, davon 17 KEV, Ø CVSS 9,5 2026-10: 1625 Criticals, davon 12 KEV, Ø CVSS 9,5 Okt 26 2026-11: 402 Criticals, davon 2 KEV, Ø CVSS 9,5 Ø CVSS je Monat 10.872 Criticals · ▮ KEV-Anteil · ┄ Ø CVSS 9,5
🏢 Top-Vendor-Veröffentlichungen (6 M) Adobe Apache Software Foundation Apple Google IBM Linux Microsoft Oracle Corporation
● Adobe ● Apache Software Foundation ● Apple ● Google ● IBM ● Linux ● Microsoft ● Oracle Corporation
📈 EPSS-Verteilung (Messungen)
TierCVEsAnteilΔ 7 T
≥90 %7950,2 %+8
≥50 %3.5610,9 %+3
≥10 %13.1773,2 %+12
<10 %397.84495,8 %+1.738
415.377 CVEs mit EPSS-Score (FIRST.org) · Stand 23.11.2026 · Δ vs. 14.11.
📈 EPSS-Riser (7 Tage · Top 8)
WSO2 EPSS 78,8 % ↑ +56,5 % CVE-2026-5430 CVSS 10,0
WSO2 · CVE-2026-5430 | The JWT authentication me…
CVE-2026-5430 | The JWT authentication mechanism accepts tokens signed with algorithms other than those explicitly configured or supported.…
EPSS: 22,4 % → 78,8 % (+56,5 %) ⚠️ KEV 🧪 PoC
Mirasvit EPSS 82,3 % ↑ +56,2 % CVE-2026-45247 CVSS 9,3
Mirasvit · CVE-2026-45247 | Mirasvit Full Page Cache…
CVE-2026-45247 | Mirasvit Full Page Cache Warmer for Magento 2 before version 1.11.12 contains a PHP object injection vulnerability that al…
EPSS: 26,2 % → 82,3 % (+56,2 %) ⚠️ KEV 🧪 PoC
Adobe EPSS 81,6 % ↑ +34,2 % CVE-2026-48356 CVSS 9,3
Adobe · CVE-2026-48356 | Adobe Commerce is affect…
CVE-2026-48356 | Adobe Commerce is affected by an Unrestricted Upload of File with Dangerous Type vulnerability that could result in arbitr…
EPSS: 47,5 % → 81,6 % (+34,2 %) ⚠️ KEV 🧪 PoC
kestra-io EPSS 20,4 % ↑ +18,3 % CVE-2026-49869 CVSS 10,0
kestra-io · CVE-2026-49869 | Kestra is an open-source…
CVE-2026-49869 | Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, AuthenticationFilter in Kestra …
EPSS: 2,1 % → 20,4 % (+18,3 %) ⚠️ KEV 🧪 PoC
Google EPSS 99,9 % ↑ +17,3 % CVE-2026-111497 CVSS 9,2
Google · CVE-2026-111497 | A buffer overflow vulne…
CVE-2026-111497 | A buffer overflow vulnerability in the Brotli decoder (c/dec/decode.c) in Google Brotli versions 1.0.3 through 1.2.0 on a…
EPSS: 82,6 % → 99,9 % (+17,3 %) ⚠️ KEV 🧪 PoC
berriai EPSS 78,0 % ↑ +9,1 % CVE-2026-40217 CVSS 8,8
berriai · CVE-2026-40217 | LiteLLM through 2026-04-…
CVE-2026-40217 | LiteLLM through 2026-04-08 allows remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/tes…
EPSS: 68,9 % → 78,0 % (+9,1 %) 🧪 PoC
RARLAB EPSS 98,8 % ↑ +8,3 % CVE-2025-6218 CVSS 7,8
RARLAB · CVE-2025-6218 | RARLAB WinRAR Directory T…
CVE-2025-6218 | RARLAB WinRAR Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execut…
EPSS: 90,5 % → 98,8 % (+8,3 %) ⚠️ KEV 🧪 PoC
dgtlmoon EPSS 93,0 % ↑ +7,8 % CVE-2024-32651 CVSS 10,0
dgtlmoon · CVE-2024-32651 | changedetection.io is an…
CVE-2024-32651 | changedetection.io is an open source web page change detection, website watcher, restock monitor and notification service.…
EPSS: 85,3 % → 93,0 % (+7,8 %) 🧪 PoC
Frühindikator · FIRST.org
Datenquellen & Methodik: Primärquelle ist die EUVD der ENISA (laufender Datenbank-Sync, alle 15 Minuten), abgeglichen mit dem CISA-KEV-Katalog und der NVD — Detail-Dossiers reichern fehlende Felder live per NVD an — mit Fallback auf CIRCL vulnerability-lookup (EU/Non-Profit, aggregiert CVE-, GitHub- und OSV-Advisories). Der CISA-KEV-Katalog (Known Exploited Vulnerabilities, ~1.700 aktiv ausgenutzte Schwachstellen) wird bei jedem Sync vollständig neu geladen und kreuzreferenziert — filterbar über die KEV-Pille. CVSS 3.1 wird nach Ampel-Logik aus Verteidigersicht dekodiert; EPSS bezeichnet die 30-Tage-Exploit-Wahrscheinlichkeit (FIRST.org).
🇪🇺 ENISA EUVD 🇺🇸 NVD ⚠️ CISA KEV ⚡ EPSS
🛡️ Ethische Nutzung: Alle CVE- und PoC-Daten dienen ausschließlich der defensiven Absicherung, Patch-Verifikation und autorisierten Sicherheitsprüfungen (Responsible Disclosure). Ethik- & Disclosure-Richtlinie · AGB § 6a (v2026.11)
Ökosystem & Hersteller Bedrohungs-Matrix:
⚙️ Erweiterte Forscher-Filter (Lifecycle, Scores, EPSS, Exploit, Sortierung, Dynamik, Quelle, CWE)
46 Treffer (46 von 46 Treffern)
Ansicht „🟠 High (7.0+) · 🏢 splunk“ zurücksetzen ✕
46 Schwachstellen
J/↓ Nächste K/↑ Vorherige Enter/O Dossier öffnen C CVE kopieren V Kacheln ↔ Liste / Suche G Nach oben Esc Fokus/Filter löschen
7.1 HIGH
EPSS 0.2%
CVE-2026-131303 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-131303 | In Splunk AI Assistant versions below 2.0.0, a user who does not hold the "admin" or "power" Splunk roles could obtain limited information about indexes and data sources outside their authorized scope through the assistant. The vulnerability is possible because Splunk AI Assistant does not fully apply authorization controls to all information that it retrieves.

In Splunk AI Assistant versions below 2.0.0, a user who does not hold the "admin" or "power" Splunk roles could obtain limited information about indexes and data sources outside their authorized scope through the assistant. The vulnerabilit

🛡️ 35 🔬 26
8.1 HIGH
EPSS 0.3%
CVE-2026-131297 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

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

🛡️ 43 🔬 36
8.8 HIGH
EPSS 0.5%
CVE-2026-131295 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

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

🛡️ 41 🔬 26
8.3 HIGH
EPSS 0.3%
CVE-2026-131293 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

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

🛡️ 39 🔬 26
7.3 HIGH
EPSS 0.1%
CVE-2026-131288 💻 Lokal 🔑 Geringe Nutzerrechte nötig

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

🛡️ 26 🔬 6
8.1 HIGH
EPSS 0.3%
CVE-2026-131282 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

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

🛡️ 38 🔬 26
7.3 HIGH
EPSS 0.2%
CVE-2026-131278 💻 Lokal 🔑 Geringe Nutzerrechte nötig

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

🛡️ 26 🔬 6
7.2 HIGH
EPSS 0.6%
CVE-2026-131272 🌐 Netzwerk (Remote) 🔐 Admin-Rechte nötig

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

🛡️ 35 🔬 26
8.8 HIGH
EPSS 0.2%
CVE-2026-131271 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

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

🛡️ 41 🔬 26
8.8 HIGH
EPSS 0.4%
CVE-2026-131270 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

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

🛡️ 41 🔬 26
8.8 HIGH
EPSS 0.5%
CVE-2026-131269 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

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

🛡️ 41 🔬 26
7.2 HIGH
EPSS 0.5%
CVE-2026-131268 🌐 Netzwerk (Remote) 🔐 Admin-Rechte nötig

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

🛡️ 35 🔬 26
7.7 HIGH
EPSS 0.2%
CVE-2026-131266 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

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

🛡️ 37 🔬 26
8.8 HIGH
EPSS 0.5%
CVE-2026-131263 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

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

🛡️ 41 🔬 26
8.8 HIGH
EPSS 0.5%
CVE-2026-131261 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

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

🛡️ 41 🔬 26
8.7 HIGH
EPSS 0.2%
CVE-2026-131260 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

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

🛡️ 35 🔬 14
8.7 HIGH
EPSS 0.2%
CVE-2026-131258 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

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

🛡️ 35 🔬 14
7.2 HIGH
EPSS 0.5%
CVE-2026-131256 🌐 Netzwerk (Remote) 🔐 Admin-Rechte nötig

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

🛡️ 35 🔬 26
7.5 HIGH
EPSS 0.3%
CVE-2026-131255 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

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

🛡️ 36 🔬 24
8.8 HIGH
EPSS 0.3%
CVE-2026-131252 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

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

🛡️ 41 🔬 26
7.2 HIGH
EPSS 0.4%
CVE-2026-131248 🌐 Netzwerk (Remote) 🔐 Admin-Rechte nötig

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)

🛡️ 35 🔬 26
8.8 HIGH
EPSS 0.4%
CVE-2026-131246 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

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

🛡️ 41 🔬 26
7.1 HIGH
EPSS 0.2%
CVE-2026-131245 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

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

🛡️ 35 🔬 26
7.6 HIGH
EPSS 0.3%
CVE-2026-131243 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

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

🛡️ 37 🔬 26
7.3 HIGH
EPSS 0.3%
CVE-2026-131239 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-131239 | In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in Updates data. If another user who can access the System Update Status report selects an affected row, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the row. The user who stores the values could then access sensit

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in Updates data. If another user who can access the System Update Status report selects an a

🛡️ 31 🔬 14
8.8 HIGH
EPSS 0.3%
CVE-2026-131236 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-131236 | In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user who can influence indexed event data could store attacker-controlled values in event fields. If another authenticated user who reviews the event selects the View Adaptive Response Invocations or View Adaptive Response Results workflow action from Event Actions, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of

In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user who can influence indexed event data could store attacker-controlled values in event fields. If another authenticated user who reviews the event selects the View Ad

🛡️ 41 🔬 24
8.3 HIGH
EPSS 0.3%
CVE-2026-131218 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-131218 | In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the mc_investigation_read capability could inject arbitrary Search Processing Language (SPL) into Mission Control dashboard search requests. Mission Control could then run the injected SPL with elevated permissions. With this access, the user could cause Mission Control to read stored credentials and write data to indexes and lookups. The vulnerability is possible because Missi

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the mc_investigation_read capability could inject arbitrary Search Processing Language (SPL) into Mission Control dashboard search requests. Mission Control c

🛡️ 39 🔬 26
8.3 HIGH
EPSS 0.3%
CVE-2026-131215 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-131215 | In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the ueba_finding_exclusion_edit capability could store attacker-controlled values in a User and Entity Behavior Analytics (UEBA) finding exclusion rule. Splunk Enterprise Security could later run attacker-controlled Search Processing Language (SPL) commands from the rule with elevated permissions. With this access, the user could cause Splunk Enterprise Security to read stored

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the ueba_finding_exclusion_edit capability could store attacker-controlled values in a User and Entity Behavior Analytics (UEBA) finding exclusion rule. Splun

🛡️ 39 🔬 26
7.3 HIGH
EPSS 0.3%
CVE-2026-131211 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-131211 | In Splunk App for Payment Card Industry Compliance versions below 8.7.0, a user who holds the "ess_user" Splunk Enterprise Security role could add attacker-controlled values to lookup data used by the Primary Functions report. If another authenticated user later selects the value in the Primary Function Summary panel, the Splunk App for Payment Card Industry Compliance could run attacker-controlled Search Processing Language (SPL) commands using the permissi

In Splunk App for Payment Card Industry Compliance versions below 8.7.0, a user who holds the "ess_user" Splunk Enterprise Security role could add attacker-controlled values to lookup data used by the Primary Functions report. If another au

🛡️ 31 🔬 14
8.1 HIGH
EPSS 0.3%
CVE-2026-131210 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-131210 | In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the ueba_finding_exclusion_edit capability could create a finding exclusion rule that references an attacker-controlled lookup definition if the role also grants write access to globally shared lookup definitions, as the "ess_analyst" Splunk Enterprise Security role does. The User and Entity Behavior Analytics (UEBA) Content App could later include the lookup name in a search a

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the ueba_finding_exclusion_edit capability could create a finding exclusion rule that references an attacker-controlled lookup definition if the role also gra

🛡️ 38 🔬 26
8.3 HIGH
EPSS 0.5%
CVE-2026-131209 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-131209 | In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the ueba_ers_execution_post capability could cause the User and Entity Behavior Analytics (UEBA) Content App to run arbitrary Search Processing Language (SPL) commands with elevated permissions through an Entity Risk Score calculation. With this access, the user could expose stored credentials and other data outside the permissions assigned to that role. The vulnerability is po

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the ueba_ers_execution_post capability could cause the User and Entity Behavior Analytics (UEBA) Content App to run arbitrary Search Processing Language (SPL)

🛡️ 39 🔬 26
8.3 HIGH
EPSS 0.3%
CVE-2026-131203 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-131203 | In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_analyst" Splunk Enterprise Security role could modify a search macro associated with risk exclusions. Scheduled Risk data model acceleration searches could later run attacker-controlled Search Processing Language (SPL) commands from that macro with elevated permissions. With this access, the user who modified the search macro could expose stored credentials and modify indexes or lo

In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_analyst" Splunk Enterprise Security role could modify a search macro associated with risk exclusions. Scheduled Risk data model acceleration searches could later

🛡️ 39 🔬 26
8.1 HIGH
EPSS 0.3%
CVE-2026-131200 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-131200 | In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_analyst" Splunk Enterprise Security role could create an attacker-controlled saved search. Threat intelligence lookup generation could later run the saved search with elevated permissions, which could let the user who created the saved search run arbitrary Search Processing Language (SPL) commands with those permissions. The vulnerability is possible because Splunk Enterprise Secur

In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_analyst" Splunk Enterprise Security role could create an attacker-controlled saved search. Threat intelligence lookup generation could later run the saved search

🛡️ 38 🔬 26
8.8 HIGH
EPSS 0.4%
CVE-2026-131199 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-131199 | In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the mc_investigation_read capability could cause the Risk Event Timeline Representational State Transfer (REST) API to run arbitrary Search Processing Language (SPL) commands with elevated permissions. With this access, the user could expose stored credentials and modify indexes and lookup data available to those permissions. The vulnerability is possible because the affected R

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the mc_investigation_read capability could cause the Risk Event Timeline Representational State Transfer (REST) API to run arbitrary Search Processing Languag

🛡️ 41 🔬 26
7.1 HIGH
EPSS 0.2%
CVE-2026-131198 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-131198 | In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the mc_view_im_data capability could cause the Mission Control incident mapping Representational State Transfer (REST) API to run arbitrary Search Processing Language (SPL) commands with elevated permissions. With this access, the user could expose all data in Splunk indexes and all stored credentials and modify protected indexes and lookup data. The vulnerability is possible b

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the mc_view_im_data capability could cause the Mission Control incident mapping Representational State Transfer (REST) API to run arbitrary Search Processing

🛡️ 35 🔬 26
7.5 HIGH
EPSS 0.4%
CVE-2026-131192 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-131192 | In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could access live event data from the indexing pipeline through the Representational State Transfer (REST) API on a standalone instance or a search head that is not an indexer cluster member. The vulnerability is possible because Splunk Enterprise accepts an empty shared key during service authentication.

In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could access live event data from the indexing pipeline through the Representational State Transfer (REST) API on a standalone instance

🛡️ 41 🔬 36
7.5 HIGH
EPSS 0.4%
CVE-2026-131190 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-131190 | In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could access RapidDiag process metadata and log file inventory information through the Representational State Transfer (REST) API. The vulnerability is possible because certain RapidDiag REST API endpoints accept a factory-default shared key for node authentication, which lets requests bypass Splunk user authentication. For more information see Using RapidDiag (h

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could access RapidDiag process metadata and log file inventory information through the Representational State Transfer (REST) API. The vulnerab

🛡️ 41 🔬 36
7.1 HIGH
EPSS 0.2%
CVE-2026-131188 🌐 Netzwerk (Remote) 🔓 Keine Authentifizierung nötig

CVE-2026-131188 | In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, an unauthenticated user could craft a malicious link that, if opened by an authenticated user, executes arbitrary Search Processing Language (SPL) searches with the victim's permissions. Successful exploitation could allow the unauthenticated user to access or modify data, alter Splunk platform configurations, and disrupt operations available to the affected user. The vulnerability is

In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, an unauthenticated user could craft a malicious link that, if opened by an authenticated user, executes arbitrary Search Processing Language (SPL) searches with the vi

🛡️ 35 🔬 24
7.6 HIGH
EPSS 0.3%
CVE-2026-131182 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-131182 | In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could store malicious Search Processing Language (SPL) in a shared dashboard. The malicious SPL could run using the permissions of the user who opened the dashboard and could access or modify data available to that user and disrupt Splunk Enterprise availability. The vulnerability is possible because Splunk Enterprise does not preserve quoted sea

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could store malicious Search Processing Language (SPL) in a shared dashboard. The malicious SPL could run using the permission

🛡️ 32 🔬 14
7.6 HIGH
EPSS 0.3%
CVE-2026-131179 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-131179 | In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could add attacker-controlled Search Processing Language (SPL) to a shared dashboard. When another user opens the dashboard in Splunk Web, Splunk Enterprise could run the attacker-controlled SPL using the permissions of that dashboard viewer. The attacker-controlled SPL could expose stored credentials, modify indexed data, and reduce availability

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could add attacker-controlled Search Processing Language (SPL) to a shared dashboard. When another user opens the dashboard in

🛡️ 32 🔬 14
7.6 HIGH
EPSS 0.3%
CVE-2026-131178 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-131178 | In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could craft a shared Classic Dashboard that runs arbitrary Search Processing Language (SPL) commands for another authenticated user. Exploitation requires the dashboard viewer to open the shared dashboard. The injected commands could access data available to the dashboard viewer, modify data available to the dashboard viewer, and partially disrup

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could craft a shared Classic Dashboard that runs arbitrary Search Processing Language (SPL) commands for another authenticated

🛡️ 32 🔬 14
7.1 HIGH
EPSS 0.2%
CVE-2026-131177 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-131177 | In Splunk Enterprise versions below 10.4.4, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could run arbitrary Search Processing Language (SPL) searches with elevated privileges through saved search dispatch and access stored credentials and indexed data or modify lookup data. The vulnerability is possible because Splunk Enterprise does not correctly neutralize caller-supplied saved search dispatch values before it

In Splunk Enterprise versions below 10.4.4, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could run arbitrary Search Processing Language (SPL) searches with elevated privileges through saved searc

🛡️ 35 🔬 26
7.6 HIGH
EPSS 0.3%
CVE-2026-131175 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-131175 | In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user who holds the "power" Splunk role could create and share a metric alert that causes Analytics Workspace to run a malicious Search Processing Language (SPL) when another authenticated user opens a link to the alert. The malicious SPL could expose data, modify data, or disrupt services available in the affected session. The vulnerability is possible because Analytics Workspace doe

In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user who holds the "power" Splunk role could create and share a metric alert that causes Analytics Workspace to run a malicious Search Processing Language (SPL) when

🛡️ 32 🔬 14
8.1 HIGH
EPSS 0.3%
CVE-2026-76544 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-76544 | In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could cause scheduled metric alert searches to run arbitrary Search Processing Language (SPL) commands and access credentials stored in cleartext. This requires at least one non-internal metric index on the instance. The vulnerability is possible because Splunk Enterprise does not fully validate metric alert filter input before

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could cause scheduled metric alert searches to run arbitrary Search Processing Language (SPL) commands and

🛡️ 38 🔬 26
8.8 HIGH
EPSS 0.3%
CVE-2026-76540 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-76540 | In Splunk Enterprise versions below 9.4.17, 10.0.12, 10.2.9, and 10.4.5, a user who does not hold the "admin" or "power" Splunk roles can configure a metric alert through the Representational State Transfer (REST) API that runs a search with elevated privileges. The vulnerability lets the user access or modify data and disrupt the Splunk Enterprise instance. The vulnerability occurs because Splunk Enterprise does not enforce the required role-based authorizat

In Splunk Enterprise versions below 9.4.17, 10.0.12, 10.2.9, and 10.4.5, a user who does not hold the "admin" or "power" Splunk roles can configure a metric alert through the Representational State Transfer (REST) API that runs a search wit

🛡️ 41 🔬 26
8.8 HIGH
EPSS 0.4%
CVE-2026-76538 🌐 Netzwerk (Remote) 🔑 Geringe Nutzerrechte nötig

CVE-2026-76538 | In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could cause Splunk Enterprise to run arbitrary Search Processing Language (SPL) searches with elevated privileges through data model acceleration. The vulnerability is possible because Splunk Enterprise does not correctly neutralize caller-supplied data model acceleration values before it places them into generated summarizatio

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could cause Splunk Enterprise to run arbitrary Search Processing Language (SPL) searches with elevated pri

🛡️ 41 🔬 26
46 von ~46 Einträgen geladen Ende der Trefferliste — 46 Einträge geladen. Tipp: Filter leichtern für tieferes Blättern.