🔴 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: 400 Criticals, davon 2 KEV, Ø CVSS 9,5 Ø CVSS je Monat 10.870 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.83795,8 %+1.738
415.370 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 soar · Sort: ADMIN” ✕
17 vulnerabilities
J/↓ Next K/↑ Previous Enter/O Open dossier C Copy CVE V Grid ↔ List / Search G Top Esc Reset focus/filter
6.5 MEDIUM
EPSS 0.3%
CVE-2026-131285 🌐 Network (remote) 🔑 Limited user rights required

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

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

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

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

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

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

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

🛡️ 29 🔬 23
5.4 MEDIUM
EPSS 0.3%
CVE-2026-131275 🌐 Network (remote) 🔑 Limited user rights required

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

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

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

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

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

🛡️ 29 🔬 23
4.3 MEDIUM
EPSS 0.2%
CVE-2026-131298 🌐 Network (remote) 🔑 Limited user rights required

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

🛡️ 25 🔬 23
17 von ~17 Einträgen geladen End of results — 17 entries loaded. Tip: relax filters to page deeper.