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 3 of 6.

  1. CVE-2026-131269

    Splunk SOAR uncontrolled search path

    High8.8EPSS not scored yet

    Splunk SOARCVSS 3.1 · 8.8CWE-427

    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…

  2. CVE-2026-131268

    Splunk SOAR uncontrolled search path

    High7.2EPSS not scored yet

    Splunk SOARCVSS 3.1 · 7.2CWE-427

    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…

  3. CVE-2026-131267

    Splunk SOAR insufficiently protected credentials

    Medium6.3EPSS not scored yet

    Splunk SOARCVSS 3.1 · 6.3CWE-522

    In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings view and edit permissions could test a Lightweight Directory Access Protocol authentication provider and cause Splunk SOAR to send a stored directory service account bind password to a host…

  4. CVE-2026-131266

    Splunk SOAR sensitive data in a response

    High7.7EPSS not scored yet

    Splunk SOARCVSS 3.1 · 7.7CWE-201

    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…

  5. CVE-2026-131265

    Splunk SOAR incorrect authorization

    Medium4.3EPSS not scored yet

    Splunk SOARCVSS 3.1 · 4.3CWE-863

    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…

  6. CVE-2026-131264

    Splunk SOAR insufficiently protected credentials

    Medium6.3EPSS not scored yet

    Splunk SOARCVSS 3.1 · 6.3CWE-522

    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 the stored root credential for an external credential store to a host that the user controls. Depending on the configuration, the exposed…

  7. CVE-2026-131263

    Splunk SOAR argument injection

    High8.8EPSS not scored yet

    Splunk SOARCVSS 3.1 · 8.8CWE-88

    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…

  8. CVE-2026-131262

    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 who can view and edit containers in at least one container label could create artifacts with parent relationships to containers and artifacts outside those labels. This could expose fields from restricted artifacts and…

  9. CVE-2026-131261

    Splunk SOAR inclusion of untrusted functionality

    High8.8EPSS not scored yet

    Splunk SOARCVSS 3.1 · 8.8CWE-829

    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…

  10. CVE-2026-131260

    Splunk SOAR cross-site scripting

    High8.7EPSS not scored yet

    Splunk SOARCVSS 3.1 · 8.7CWE-79

    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…

  11. CVE-2026-131259

    Splunk SOAR missing authorization

    Medium5.4EPSS not scored yet

    Splunk SOARCVSS 3.1 · 5.4CWE-862

    In Splunk SOAR versions below 8.8.0, a user with permission to create and view containers for a label could use the Representational State Transfer (REST) API to create a container that references a workbook phase in a case the user cannot view, disclosing the phase name and…

  12. CVE-2026-131258

    Splunk SOAR cross-site scripting

    High8.7EPSS not scored yet

    Splunk SOARCVSS 3.1 · 8.7CWE-79

    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…

  13. CVE-2026-131257

    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 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…

  14. CVE-2026-131256

    Splunk SOAR inclusion of untrusted functionality

    High7.2EPSS not scored yet

    Splunk SOARCVSS 3.1 · 7.2CWE-829

    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…

  15. CVE-2026-131255

    Splunk SOAR incorrectly resolved name

    High7.5EPSS not scored yet

    Splunk SOARCVSS 3.1 · 7.5CWE-706

    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…

  16. CVE-2026-131254

    Splunk SOAR insecure direct object reference

    Medium5.4EPSS not scored yet

    Splunk SOARCVSS 3.1 · 5.4CWE-639

    In Splunk SOAR versions below 8.8.0, a user with permission to create containers on one label could use the Representational State Transfer (REST) API to create a container with a parent relationship to a container that the user cannot access. This could let the user alter…

  17. CVE-2026-131253

    Splunk SOAR code injection

    Critical9.9EPSS not scored yet

    Splunk SOARCVSS 3.1 · 9.9CWE-94

    In Splunk SOAR versions below 8.8.0, an authenticated user that holds a role with the Apps edit, Containers edit, and Playbooks execute permissions could use the App Wizard to execute arbitrary code as the user account that runs Splunk SOAR. This could compromise the…

  18. CVE-2026-131252

    Splunk SOAR missing authorization

    High8.8EPSS not scored yet

    Splunk SOARCVSS 3.1 · 8.8CWE-862

    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…

  19. CVE-2026-131251

    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, 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…

  20. CVE-2026-131250

    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 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…

  21. CVE-2026-131249

    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 view, edit, and run playbooks and access to at least one container label could retrieve a callback handle from a playbook run outside the container-label scope granted to that account. The…

  22. CVE-2026-131248

    Splunk SOAR incorrect authorization

    High7.2EPSS not scored yet

    Splunk SOARCVSS 3.1 · 7.2CWE-863

    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…

  23. CVE-2026-131247

    Splunk SOAR missing authorization

    Medium4.3EPSS not scored yet

    Splunk SOARCVSS 3.1 · 4.3CWE-862

    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…

  24. CVE-2026-131246

    Splunk SOAR information exposure

    High8.8EPSS not scored yet

    Splunk SOARCVSS 3.1 · 8.8CWE-200

    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…

  25. CVE-2026-131245

    Splunk SOAR information exposure

    High7.1EPSS not scored yet

    Splunk SOARCVSS 3.1 · 7.1CWE-200

    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…

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.