🔴 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 Dec 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 Oct 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 22.11.2026 · Δ vs. 14.11.
📈 EPSS-Riser (7 Tage · Top 8)
Microsoft EPSS 81,9 % ↑ +78,8 % CVE-2026-50522 CVSS 9,8
Microsoft · CVE-2026-50522 | Deserialization of untru…
CVE-2026-50522 | Deserialization of untrusted data in Microsoft Office SharePoint allows an unauthorized attacker to execute code over a ne…
EPSS: 3,0 % → 81,9 % (+78,8 %) ⚠️ KEV 🧪 PoC
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
SolarWinds EPSS 87,3 % ↑ +39,3 % CVE-2026-28318 CVSS 7,5
SolarWinds · CVE-2026-28318 | SolarWinds Serv-U is sus…
CVE-2026-28318 | SolarWinds Serv-U is susceptible to specially crafted POST requests that crash the Serv-U service without authentication u…
EPSS: 48,0 % → 87,3 % (+39,3 %) ⚠️ 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
Plex EPSS 19,8 % ↑ +18,0 % CVE-2026-96656 CVSS 8,6
Plex · CVE-2026-96656 | Plex Media Server before…
CVE-2026-96656 | Plex Media Server before 1.43.3.10861 allows an admin user to write arbitrary files that may be executed on load. The pref…
EPSS: 1,8 % → 19,8 % (+18,0 %) ⚠️ 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
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
🛡️ Ethical Use: All CVE and PoC intelligence is intended exclusively for defensive security, patch verification, and authorized testing (Responsible Disclosure). Ethical & Disclosure Charter · Terms § 6a (v2026.11)
Ökosystem & Hersteller Bedrohungs-Matrix:
⚙️ Advanced Researcher Filters (Lifecycle, Scores, EPSS, Exploit, Sort, Dynamics, Source, CWE) 1 aktiv
Reset “🟡 Medium · Product: splunk enterprise · Sort: ADMIN” ✕
35 vulnerabilities
J/↓ Next K/↑ Previous Enter/O Open dossier C Copy CVE V Grid ↔ List / Search G Top Esc Reset focus/filter
5.9 MEDIUM
EPSS 0.3%
CVE-2026-131195 🌐 Network (remote) 🔓 No authentication required

CVE-2026-131195 | In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could send repeated HTTP PubSub channel subscription requests that cause a Denial of Service (DoS) by permanently increasing memory usage until Splunk Enterprise exhausts available memory. The vulnerability affects instances that turn on the [pubsubsvr-http] stanza in server.conf because the HTTP PubSub broker does not release memory associated with a channel af

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could send repeated HTTP PubSub channel subscription requests that cause a Denial of Service (DoS) by permanently increasing memory usage until

🛡️ 36 🔬 33
5.3 MEDIUM
EPSS 0.2%
CVE-2026-131189 🌐 Network (remote) 🔓 No authentication required

CVE-2026-131189 | In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could inject arbitrary fields into Splunk Enterprise audit records via the Representational State Transfer (REST) API. Successful exploitation could allow the unauthenticated user to forge audit evidence, compromising the integrity of audit reviews and security detections that rely on legacy audit-field parsing. The vulnerability exists because Splunk Enterprise

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could inject arbitrary fields into Splunk Enterprise audit records via the Representational State Transfer (REST) API. Successful exploitation

🛡️ 34 🔬 33
6.5 MEDIUM
EPSS 0.3%
CVE-2026-131222 🌐 Network (remote) 🔐 Admin-Rechte nötig

CVE-2026-131222 | In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the edit_modinput_identity_manager capability could use Asset and Identity Management to modify protected saved searches and role capabilities. With this access, the user could obtain full administrator access to the Splunk platform. The vulnerability is possible because Asset and Identity Management does not validate the app namespace before sending a Representational State Tr

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the edit_modinput_identity_manager capability could use Asset and Identity Management to modify protected saved searches and role capabilities. With this acce

🛡️ 33 🔬 23
6.5 MEDIUM
EPSS 0.3%
CVE-2026-131185 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131185 | In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who does not hold the "admin" or "power" Splunk roles could use the apps backup and restore Representational State Transfer (REST) API to prevent subsequent apps backup or restore operations until Splunk Enterprise restarts. This could result in a Denial of Service (DoS). The vulnerability is possible because the apps backup and restore REST API handlers do not correctly enforce

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who does not hold the "admin" or "power" Splunk roles could use the apps backup and restore Representational State Transfer (REST) API to prevent subsequent app

🛡️ 33 🔬 23
6.5 MEDIUM
EPSS 0.2%
CVE-2026-76539 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-76539 | 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 use the search jobs Representational State Transfer (REST) API to access indexed events that the srchFilter setting for the role should hide. The same user could also run internal Search Processing Language (SPL) commands and bypass SPL safeguards for risky commands within indexes that the role can search. The vulnerabili

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 use the search jobs Representational State Transfer (REST) API to access indexed events that the src

🛡️ 33 🔬 23
5.9 MEDIUM
EPSS 0.2%
CVE-2026-131223 🌐 Network (remote) 🔓 No authentication required

CVE-2026-131223 | In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user could trick an authenticated user into opening a link that the unauthenticated user creates. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the authenticated user. The commands could access data and perform actions available to that user. The vulnerability is possible because the Lookup Editor does not

In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user could trick an authenticated user into opening a link that the unauthenticated user creates. Splunk Enterprise Security could then run attacker-controlled Search Pr

🛡️ 31 🔬 21
5.9 MEDIUM
EPSS 0.2%
CVE-2026-131208 🌐 Network (remote) 🔓 No authentication required

CVE-2026-131208 | In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user could create and deliver a crafted Investigation Workbench link to an authenticated Splunk Enterprise Security user. If the authenticated user opens the link, Investigation Workbench could run arbitrary Search Processing Language (SPL) commands using the permissions of the authenticated user. With this access, the unauthenticated user could expose or modify data available to the auth

In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user could create and deliver a crafted Investigation Workbench link to an authenticated Splunk Enterprise Security user. If the authenticated user opens the link, Inves

🛡️ 31 🔬 21
5.9 MEDIUM
EPSS 0.2%
CVE-2026-131201 🌐 Network (remote) 🔓 No authentication required

CVE-2026-131201 | In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user with network-path interception capability could cause attacker-controlled JavaScript to run in the browser of a security analyst who previews a Portable Document Format (PDF) attachment in Mission Control. The JavaScript could expose data and perform actions available to the security analyst. The vulnerability is possible because Mission Control loads the PDF rendering worker from an

In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user with network-path interception capability could cause attacker-controlled JavaScript to run in the browser of a security analyst who previews a Portable Document Fo

🛡️ 31 🔬 21
5.4 MEDIUM
EPSS 0.2%
CVE-2026-131207 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131207 | In Splunk Enterprise Security versions below 8.7.0, an authenticated user who does not hold the edit_correlationsearches capability could set Status to Testing for a versioned detection or clear that setting. This could affect the integrity and availability of detection testing. The vulnerability is possible because the Test Mode Representational State Transfer (REST) API does not require the edit_correlationsearches capability before it creates or deletes s

In Splunk Enterprise Security versions below 8.7.0, an authenticated user who does not hold the edit_correlationsearches capability could set Status to Testing for a versioned detection or clear that setting. This could affect the integrity

🛡️ 29 🔬 23
5.5 MEDIUM
EPSS 0.3%
CVE-2026-131206 🌐 Network (remote) 🔐 Admin-Rechte nötig

CVE-2026-131206 | In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the edit_modinput_data_migrator capability could cause the data migration input to run arbitrary Search Processing Language (SPL) commands with elevated permissions. With this access, the user could read data outside the assigned role scope and write data to indexes and lookup tables. The vulnerability is possible because the data migration input does not restrict configured se

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the edit_modinput_data_migrator capability could cause the data migration input to run arbitrary Search Processing Language (SPL) commands with elevated permi

🛡️ 29 🔬 23
5.0 MEDIUM
EPSS 0.2%
CVE-2026-131230 🌐 Network (remote) 🔓 No authentication required

CVE-2026-131230 | In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user could trick a user that holds a role with the ueba_can_view_ui capability into opening a link that the unauthenticated user creates for the User and Entity Behavior Analytics (UEBA) Overview dashboard. When the user opens the link, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who opens the link. T

In Splunk Enterprise Security versions below 8.7.0, an unauthenticated user could trick a user that holds a role with the ueba_can_view_ui capability into opening a link that the unauthenticated user creates for the User and Entity Behavior

🛡️ 28 🔬 21
6.7 MEDIUM
EPSS 0.2%
CVE-2026-131213 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131213 | In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_analyst" Splunk Enterprise Security role could store attacker-controlled data in finding exclusion rule metadata. Another authenticated user could later open the Finding Exclusion Rules page. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who opened the page. The first user could access data

In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_analyst" Splunk Enterprise Security role could store attacker-controlled data in finding exclusion rule metadata. Another authenticated user could later open the

🛡️ 28 🔬 11
6.4 MEDIUM
EPSS 0.1%
CVE-2026-131238 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131238 | In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled certificate values. If another user who can access the Secure Sockets Layer Search dashboard 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

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled certificate values. If another user who can access the Secure Sockets Layer Search dashboard select

🛡️ 27 🔬 11
6.4 MEDIUM
EPSS 0.2%
CVE-2026-131232 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131232 | 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 vulnerability scan data. If another user who can access the Vulnerability Scan Details dashboard selects an affected value, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the value. The user who stores the values

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 vulnerability scan data. If another user who can access the Vulnerability Scan Details da

🛡️ 27 🔬 11
6.3 MEDIUM
EPSS 0.2%
CVE-2026-131227 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131227 | 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 Network Resolution data. If another user who can access the Domain Name System Search dashboard 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

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 Network Resolution data. If another user who can access the Domain Name System Search das

🛡️ 27 🔬 11
6.4 MEDIUM
EPSS 0.2%
CVE-2026-131226 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131226 | 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 Intrusion Detection data. If another user who can access the Intrusion Search dashboard 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 ac

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 Intrusion Detection data. If another user who can access the Intrusion Search dashboard s

🛡️ 27 🔬 11
6.4 MEDIUM
EPSS 0.3%
CVE-2026-131197 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131197 | In Splunk Enterprise versions below 10.4.5, 10.2.9, and 10.0.12, a low-privileged user who holds the "power" Splunk role could overwrite shared application dashboard views with arbitrary Search Processing Language (SPL) commands. When another authenticated user opens an affected dashboard in Splunk Web, Splunk Enterprise executes the injected SPL using the viewing user's permissions, potentially allowing the low-privileged user to access or modify data avail

In Splunk Enterprise versions below 10.4.5, 10.2.9, and 10.0.12, a low-privileged user who holds the "power" Splunk role could overwrite shared application dashboard views with arbitrary Search Processing Language (SPL) commands. When anoth

🛡️ 27 🔬 11
6.3 MEDIUM
EPSS 0.2%
CVE-2026-131180 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131180 | 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 create and share a dashboard that contains attacker-controlled Search Processing Language (SPL). The SPL could run using the permissions of the user who opens the dashboard. With this access, the user who created the dashboard could expose stored credentials and write data to an index. The vulnerability is possible because Splunk Enterprise

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 create and share a dashboard that contains attacker-controlled Search Processing Language (SPL). The SPL could run using

🛡️ 27 🔬 11
5.9 MEDIUM
EPSS 0.2%
CVE-2026-131220 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131220 | In Splunk Enterprise Security versions below 8.7.0, a user who can influence event values that populate an affected data model based on the Common Information Model could cause attacker-controlled values to appear in an affected Dashboard Studio view. Another authenticated user could later click a corresponding row in that view. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of th

In Splunk Enterprise Security versions below 8.7.0, a user who can influence event values that populate an affected data model based on the Common Information Model could cause attacker-controlled values to appear in an affected Dashboard S

🛡️ 26 🔬 11
4.7 MEDIUM
EPSS 0.2%
CVE-2026-76534 🌐 Network (remote) 🔐 Admin-Rechte nötig

CVE-2026-76534 | In Splunk Enterprise for Windows versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user that holds a role with the edit_user capability could create multiple user accounts that share the same user directory. This could expose user-specific configuration between those accounts, let one account modify configuration used by another account, or disrupt features that depend on separate user directories. The vulnerability is caused by improper validation of use

In Splunk Enterprise for Windows versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a user that holds a role with the edit_user capability could create multiple user accounts that share the same user directory. This could expose user-speci

🛡️ 26 🔬 23
5.7 MEDIUM
EPSS 0.2%
CVE-2026-131216 🌐 Network (remote) 🔐 Admin-Rechte nötig

CVE-2026-131216 | In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the manage_all_investigations capability could store attacker-controlled script content in a legacy investigation workbench panel title. Another authenticated user could later open a legacy investigation workbench that renders the panel. The script could then run in the browser of the user who opened the workbench and expose data or actions available through Splunk Web to the u

In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the manage_all_investigations capability could store attacker-controlled script content in a legacy investigation workbench panel title. Another authenticated

🛡️ 25 🔬 11
4.3 MEDIUM
EPSS 0.2%
CVE-2026-131187 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131187 | In Splunk Enterprise versions below 10.6.1, 10.4.5, and 10.2.9, a low-privileged user who does not hold the "admin" or "power" Splunk roles could access file path and metadata listings from search head knowledge bundles via the Representational State Transfer (REST) API. This unauthorized access could expose sensitive metadata, including Splunk platform usernames, private knowledge-object configuration file names, installed application directories, and the f

In Splunk Enterprise versions below 10.6.1, 10.4.5, and 10.2.9, a low-privileged user who does not hold the "admin" or "power" Splunk roles could access file path and metadata listings from search head knowledge bundles via the Representati

🛡️ 25 🔬 23
5.4 MEDIUM
EPSS 0.2%
CVE-2026-131237 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131237 | 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 data used by the Weak Encrypted Communication report. If another user who can access the report selects an affected drilldown, Splunk Enterprise Security could run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selects the drilldown. The user who stores the

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 data used by the Weak Encrypted Communication report. If another user who can access the

🛡️ 24 🔬 11
5.4 MEDIUM
EPSS 0.2%
CVE-2026-131233 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131233 | 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 endpoint summary data. If another user who can access the Time Center dashboard 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 sen

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 endpoint summary data. If another user who can access the Time Center dashboard selects a

🛡️ 24 🔬 11
5.4 MEDIUM
EPSS 0.2%
CVE-2026-131231 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131231 | 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 managed-lookup audit data. If another user who can access the Managed Lookups Audit dashboard 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 t

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 managed-lookup audit data. If another user who can access the Managed Lookups Audit dashb

🛡️ 24 🔬 11
5.4 MEDIUM
EPSS 0.2%
CVE-2026-131228 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131228 | In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_user" Splunk Enterprise Security role could run a search that causes attacker-controlled Search Processing Language (SPL) text to appear in the Search Audit dashboard. If another user who can access the dashboard selects the affected search, Splunk Enterprise Security could run attacker-controlled SPL commands using the permissions of the user who selects the search. The user who r

In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_user" Splunk Enterprise Security role could run a search that causes attacker-controlled Search Processing Language (SPL) text to appear in the Search Audit dashb

🛡️ 24 🔬 11
5.4 MEDIUM
EPSS 0.2%
CVE-2026-131225 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131225 | 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 the Malware data model. Another authenticated user with access to the Malware Search dashboard could later select a table row containing those values. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selected the row.

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 the Malware data model. Another authenticated user with access to the Malware Search dash

🛡️ 24 🔬 11
5.4 MEDIUM
EPSS 0.2%
CVE-2026-131205 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131205 | In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_user" Splunk Enterprise Security role could store attacker-controlled asset data in an asset source lookup. A user that holds a role with the mc_assets_read capability could later open the Asset Center dashboard and select that value in the Asset Information table. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the perm

In Splunk Enterprise Security versions below 8.7.0, a user who holds the "ess_user" Splunk Enterprise Security role could store attacker-controlled asset data in an asset source lookup. A user that holds a role with the mc_assets_read capab

🛡️ 24 🔬 11
5.4 MEDIUM
EPSS 0.2%
CVE-2026-131183 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131183 | In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a low-privileged user who holds the "power" Splunk role could inject arbitrary Search Processing Language (SPL) commands into a Classic Dashboard search. When another user opens the affected dashboard in Splunk Web, those injected commands execute with the viewing user's permissions, potentially allowing the low-privileged user to access stored credentials and write data to indexes. The

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a low-privileged user who holds the "power" Splunk role could inject arbitrary Search Processing Language (SPL) commands into a Classic Dashboard search. When another

🛡️ 24 🔬 11
4.8 MEDIUM
EPSS 0.2%
CVE-2026-131235 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131235 | 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 data used by the Credit Card Data Found dashboard. If another user who can access the dashboard 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

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 data used by the Credit Card Data Found dashboard. If another user who can access the das

🛡️ 22 🔬 11
4.8 MEDIUM
EPSS 0.2%
CVE-2026-76541 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-76541 | In Splunk Enterprise versions below 10.6.0, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could store attacker-controlled Search Processing Language (SPL) in a shared data model calculation. When a user who can run a search against the shared data model runs one, the injected SPL can run using the permissions of the user who ran the search. This could expose sensitive credentials to the user who created the shared data model. T

In Splunk Enterprise versions below 10.6.0, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the "power" Splunk role could store attacker-controlled Search Processing Language (SPL) in a shared data model calculation. When a user who c

🛡️ 22 🔬 11
4.6 MEDIUM
EPSS 0.2%
CVE-2026-131221 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131221 | 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 intrusion detection data. Another user who holds the "pci_user" role could later select the corresponding row in the Intrusion Detection and Prevention System Alert Activity Details panel. The report could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user

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 intrusion detection data. Another user who holds the "pci_user" role could later select t

🛡️ 21 🔬 11
4.6 MEDIUM
EPSS 0.2%
CVE-2026-131217 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131217 | 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 data that populates the System Misconfigurations report. Another user with access to the report could later select a related row. The System Misconfigurations report could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who selected the row. The commands

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 data that populates the System Misconfigurations report. Another user with access to the

🛡️ 21 🔬 11
4.6 MEDIUM
EPSS 0.2%
CVE-2026-131212 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131212 | 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 data that populates the Malware Activity report. Another user with access to the report could later click a related row. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who clicked the row. The commands could access data

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 data that populates the Malware Activity report. Another user with access to the report c

🛡️ 21 🔬 11
4.6 MEDIUM
EPSS 0.2%
CVE-2026-131194 🌐 Network (remote) 🔑 Limited user rights required

CVE-2026-131194 | In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a low-privileged user who holds the "power" Splunk role could inject malicious content into a Splunk Web view. When another authenticated user opens the affected view in Splunk Web, the injected content executes unauthorized JavaScript code within the viewing user's browser session. The vulnerability is possible because Splunk Web does not properly validate content in a view definition

In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a low-privileged user who holds the "power" Splunk role could inject malicious content into a Splunk Web view. When another authenticated user opens the affected view

🛡️ 21 🔬 11
35 von ~35 Einträgen geladen End of results — 35 entries loaded. Tip: relax filters to page deeper.