Skip to main content

Free tool · No sign-in

CVE radar: the latest vulnerabilities, explained.

Every new CVE from NVD, with whether it is exploited in the wild (CISA KEV), how likely it is to be (FIRST EPSS), and what it means for your architecture in plain language.

Updated 19 Nov, 20:47 UTC from NVD, CISA KEV and FIRST EPSSMarkdownRSSJSON Feed

Patch first

Exploited in the wild, newest first.

CISA adds a CVE to its Known Exploited Vulnerabilities catalog when attackers are using it. Patch these first, then CVEs with a high EPSS score, then the most severe, starting with anything reachable from the internet.

  1. CVE-2026-90436

    Apache Axis Unsafe Reflection Vulnerability

    Critical9.8Exploited, CISA due date 2026-11-21EPSS 1.1%, higher than 67% of scored CVEs

    Apache Axis and 1 moreCVSS 3.1 · 9.8CWE-470

  2. CVE-2026-90817

    Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability

    Critical9.8Exploited, CISA due date 2026-11-21EPSS 3.7%, higher than 90% of scored CVEs

    Vanderbilt University Research Electronic Data Capture (REDCap) and 2 moreCVSS 3.1 · 9.8CWE-73, CWE-94

  3. CVE-2026-40217

    BerriAI LiteLLM Unprotected Alternate Channel Vulnerability

    High8.8Exploited, CISA due date 2026-12-02EPSS 17%, higher than 97% of scored CVEs

    BerriAI LiteLLM and 8 moreCVSS 3.1 · 8.8CWE-420, CWE-94

  4. CVE-2024-10441

    Synology DiskStation Manager (DSM) Improper Encoding or Escaping of Output Vulnerability

    Critical9.8Exploited, CISA due date 2026-11-21EPSS 1.3%, higher than 70% of scored CVEs

    Synology DiskStation Manager (DSM) and 3 moreCVSS 3.1 · 9.8CWE-116

  5. CVE-2026-115731

    Perforce Puppet Enterprise Deserialization of Untrusted Data Vulnerability

    Critical9.4Exploited, CISA due date 2026-12-01EPSS 0.69%, higher than 54% of scored CVEs

    Perforce Puppet Enterprise and 2 moreCVSS 4.0 · 9.4CWE-94, CWE-502

Every exploited CVE

Trends

9,929 CVEs published, 850 of them critical. Many arrive without a score yet: NVD and the reporting organisations add CVSS over the following days.

CriticalHighMediumLowNot scored21 Oct 2026 to 19 Nov 2026
Show the numbers
DayCriticalHighMediumLowNot scored
21 Oct 202620000
22 Oct 202620000
23 Oct 202600000
24 Oct 202600000
25 Oct 202600000
26 Oct 202600000
27 Oct 202600000
28 Oct 202601000
29 Oct 202600000
30 Oct 202600000
31 Oct 202601000
1 Nov 202600000
2 Nov 202611000
3 Nov 202610100
4 Nov 202635160140290
5 Nov 202655213149360
6 Nov 202641149203474
7 Nov 2026551592381012
8 Nov 202623128143260
9 Nov 202633164230421
10 Nov 20261391260648616
11 Nov 202656311250470
12 Nov 202630174131230
13 Nov 202668335337520
14 Nov 202614202190
15 Nov 202610474690
16 Nov 2026191151921811
17 Nov 20261094665421110
18 Nov 20261072982533422
19 Nov 20265025039451248

Exploit likelihood (EPSS), last 30 days

  1. Under 1%8076
  2. 1% to 10%252
  3. 10% to 50%5
  4. 50% or more3
  5. Not scored yet1593

Matching CVEs

147 CVEs match these filters, page 2 of 6.

  1. CVE-2026-131294

    Splunk SOAR insecure direct object reference

    Medium6.5EPSS not scored yet

    Splunk SOARCVSS 3.1 · 6.5CWE-639

    In Splunk SOAR versions below 8.8.0, an authenticated user who can edit and run playbooks on a container label could associate a custom-function callback with another playbook run. The callback could modify the state of a container outside the authorized scope for that user.…

  2. CVE-2026-131293

    Splunk SOAR insecure direct object reference

    High8.3EPSS not scored yet

    Splunk SOARCVSS 3.1 · 8.3CWE-639

    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…

  3. CVE-2026-131292

    Splunk SOAR insecure direct object reference

    Medium6.5EPSS not scored yet

    Splunk SOARCVSS 3.1 · 6.5CWE-639

    In Splunk SOAR versions below 8.8.0, a user who can edit and run a playbook on a permitted label could cause Splunk SOAR to return custom-function status and callback state from another playbook run. The issue results from insufficient binding between a custom-function-status…

  4. CVE-2026-131291

    Splunk SOAR insecure direct object reference

    Medium6.5EPSS not scored yet

    Splunk SOARCVSS 3.1 · 6.5CWE-639

    In Splunk SOAR versions below 8.8.0, a Splunk SOAR user who can edit and run playbooks for a permitted container label could associate action and callback state with a running playbook outside that container label. This could affect playbook automation for containers that the…

  5. CVE-2026-131290

    Splunk SOAR insecure direct object reference

    Medium4.3EPSS not scored yet

    Splunk SOARCVSS 3.1 · 4.3CWE-639

    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…

  6. CVE-2026-131289

    Splunk SOAR insufficient verification of data authenticity

    Low3.1EPSS not scored yet

    Splunk SOARCVSS 3.1 · 3.1CWE-345

    In Splunk SOAR versions below 8.8.0, a user who holds a role that can edit and run playbooks in Splunk SOAR could cause Splunk SOAR to run non-read-only actions from a Safe Mode playbook, resulting in unauthorized state changes. The vulnerability is possible because Splunk SOAR…

  7. CVE-2026-131288

    Splunk SOAR improper privilege management

    High7.3EPSS not scored yet

    Splunk SOARCVSS 3.1 · 7.3CWE-269

    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…

  8. CVE-2026-131287

    Splunk SOAR incorrect authorization

    Critical9.6EPSS not scored yet

    Splunk SOARCVSS 3.1 · 9.6CWE-863

    In Splunk SOAR versions below 8.8.0, a user that holds a role with the Playbooks view, edit, execute, and delete permissions could cause existing cross-repository playbook references to run attacker-controlled playbook code. The vulnerability is possible because Splunk SOAR can…

  9. CVE-2026-131286

    Splunk SOAR insecure direct object reference

    High7.1EPSS not scored yet

    Splunk SOARCVSS 3.1 · 7.1CWE-639

    In Splunk SOAR versions below 8.8.0, an authenticated user with permission to author and run playbooks could view action data outside the authorized scope for that user and change the status and message of another playbook run. The vulnerability is possible because the playbook…

  10. CVE-2026-131285

    Splunk SOAR insecure direct object reference

    Medium6.5EPSS not scored yet

    Splunk SOARCVSS 3.1 · 6.5CWE-639

    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.

  11. CVE-2026-131284

    Splunk SOAR mass assignment

    Medium4.3EPSS not scored yet

    Splunk SOARCVSS 3.1 · 4.3CWE-915

    In Splunk SOAR versions below 8.8.0, an authenticated user with permission to view and edit containers could import a container archive that makes artifacts appear to be part of a case or have notes when no corresponding case associations or notes exist. This could cause…

  12. CVE-2026-131283

    Splunk SOAR vulnerability

    Medium4.3EPSS not scored yet

    Splunk SOARCVSS 3.1 · 4.3CWE-665

    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…

  13. CVE-2026-131282

    Splunk SOAR sensitive data in logs

    High8.1EPSS not scored yet

    Splunk SOARCVSS 3.1 · 8.1CWE-532

    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…

  14. CVE-2026-131281

    Splunk SOAR vulnerability

    Medium4.3EPSS not scored yet

    Splunk SOARCVSS 3.1 · 4.3CWE-778

    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…

  15. CVE-2026-131280

    Splunk SOAR missing authorization

    Medium6.5EPSS not scored yet

    Splunk SOARCVSS 3.1 · 6.5CWE-862

    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…

  16. CVE-2026-131279

    Splunk SOAR vulnerability

    Medium4.3EPSS not scored yet

    Splunk SOARCVSS 3.1 · 4.3CWE-697

    In Splunk SOAR versions below 8.8.0, an authenticated user with permission to edit artifacts could cause indicator correlation data to retain stale field associations, which can produce incorrect correlation results and event counts. The vulnerability is possible because Splunk…

  17. CVE-2026-131278

    Splunk SOAR vulnerability

    High7.3EPSS not scored yet

    Splunk SOARCVSS 3.1 · 7.3CWE-214

    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…

  18. CVE-2026-131277

    Splunk SOAR path traversal

    Medium6.3EPSS not scored yet

    Splunk SOARCVSS 3.1 · 6.3CWE-22

    In Splunk SOAR versions below 8.8.0, a user that holds a role with permission to edit playbooks and repositories could store a modified utility block in a playbook. If a user that holds a role with permission to edit playbook code later opens and saves the playbook in the…

  19. CVE-2026-131276

    Splunk SOAR incorrect authorization

    Medium4.3EPSS not scored yet

    Splunk SOARCVSS 3.1 · 4.3CWE-863

    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…

  20. CVE-2026-131275

    Splunk SOAR mass assignment

    Medium5.4EPSS not scored yet

    Splunk SOARCVSS 3.1 · 5.4CWE-915

    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…

  21. CVE-2026-131274

    Splunk SOAR vulnerability

    Low2.7EPSS not scored yet

    Splunk SOARCVSS 3.1 · 2.7CWE-778

    In Splunk SOAR versions below 8.8.0, a user with the system_settings permission could change event custom field definitions without the changes appearing in the audit trail, reducing forensic visibility and change accountability. The issue occurs because Splunk SOAR does not…

  22. CVE-2026-131273

    Splunk SOAR incorrect authorization

    Medium4.3EPSS not scored yet

    Splunk SOARCVSS 3.1 · 4.3CWE-863

    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…

  23. CVE-2026-131272

    Splunk SOAR path traversal

    High7.2EPSS not scored yet

    Splunk SOARCVSS 3.1 · 7.2CWE-22

    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…

  24. CVE-2026-131271

    Splunk SOAR incorrect authorization

    High8.8EPSS not scored yet

    Splunk SOARCVSS 3.1 · 8.8CWE-863

    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…

  25. CVE-2026-131270

    Splunk SOAR path traversal

    High8.8EPSS not scored yet

    Splunk SOARCVSS 3.1 · 8.8CWE-22

    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…

Reading the radar

CVSS, KEV and EPSS, briefly.

What is a CVE?

A CVE is a public identifier for one vulnerability in one product, such as CVE-2026-59310. The CVE program assigns it; NVD, run by the US National Institute of Standards and Technology, adds scores, weakness classes and affected product lists.

What does the CVSS score tell me?

CVSS rates how severe a vulnerability is on its own, from 0 to 10, and its vector says how it is reached: over the network or locally, with or without an account, with or without someone clicking. It says nothing about whether anyone is exploiting it. The radar shows the newest CVSS version scored and names it, because version 4.0 and 3.1 scores differ.

What is CISA KEV?

The Known Exploited Vulnerabilities catalog is CISA's list of CVEs with reliable evidence of exploitation in the wild. US federal agencies must fix each one by its due date, and it is the strongest signal of what to patch first.

What is EPSS?

FIRST's Exploit Prediction Scoring System estimates the probability that a CVE will see exploitation activity in the next 30 days, recomputed daily. Most CVEs score well under 1%, so the radar also shows the percentile: how a CVE ranks against every scored CVE.

How should I prioritise?

Patch what CISA lists as exploited first. Then CVEs with a high EPSS score, then the most severe by CVSS. Within each group, start with whatever is reachable from the internet without an account.

Where do the explanations come from?

Veriom writes them from fixed templates over each record: the weakness class says what went wrong and where in an architecture it lives, the CVSS vector says how it is reached and what it affects, and KEV, EPSS and CISA's assessment say whether it is exploited. Nobody reviews each CVE by hand, so read the description and the references before acting.

How fresh is the data?

New and changed CVEs arrive from NVD every hour, the KEV catalog every six hours and EPSS scores once a day. Each page shows when the data was last updated.

Know where a vulnerable component would sit in your systems.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

14-day free trial

Understand how your systems connect.

See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published. The radar covers CVEs published since 4 Nov 2026, plus every CVE in the KEV catalog.