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 20 Nov, 01:49 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.
Apache Axis Unsafe Reflection Vulnerability
Critical9.8Exploited, CISA due date 2026-11-21EPSS 1.1%, higher than 67% of scored CVEsApache Axis and 1 moreCVSS 3.1 · 9.8CWE-470
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 CVEsVanderbilt University Research Electronic Data Capture (REDCap) and 2 moreCVSS 3.1 · 9.8CWE-73, CWE-94
BerriAI LiteLLM Unprotected Alternate Channel Vulnerability
High8.8Exploited, CISA due date 2026-12-02EPSS 17%, higher than 97% of scored CVEsBerriAI LiteLLM and 8 moreCVSS 3.1 · 8.8CWE-420, CWE-94
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 CVEsSynology DiskStation Manager (DSM) and 3 moreCVSS 3.1 · 9.8CWE-116
Perforce Puppet Enterprise Deserialization of Untrusted Data Vulnerability
Critical9.4Exploited, CISA due date 2026-12-01EPSS 0.69%, higher than 54% of scored CVEsPerforce Puppet Enterprise and 2 moreCVSS 4.0 · 9.4CWE-94, CWE-502
Trends
The last 30 days, by severity.
10,012 CVEs published, 860 of them critical. Many arrive without a score yet: NVD and the reporting organisations add CVSS over the following days.
Show the numbers
| Day | Critical | High | Medium | Low | Not scored |
|---|---|---|---|---|---|
| 22 Oct 2026 | 2 | 0 | 0 | 0 | 0 |
| 23 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 24 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 25 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 26 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 27 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 28 Oct 2026 | 0 | 1 | 0 | 0 | 0 |
| 29 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 30 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 31 Oct 2026 | 0 | 1 | 0 | 0 | 0 |
| 1 Nov 2026 | 0 | 0 | 0 | 0 | 0 |
| 2 Nov 2026 | 1 | 1 | 0 | 0 | 0 |
| 3 Nov 2026 | 1 | 0 | 1 | 0 | 0 |
| 4 Nov 2026 | 35 | 160 | 140 | 29 | 0 |
| 5 Nov 2026 | 55 | 213 | 149 | 36 | 0 |
| 6 Nov 2026 | 41 | 149 | 203 | 47 | 4 |
| 7 Nov 2026 | 55 | 159 | 238 | 10 | 12 |
| 8 Nov 2026 | 23 | 128 | 143 | 26 | 0 |
| 9 Nov 2026 | 33 | 164 | 230 | 42 | 1 |
| 10 Nov 2026 | 139 | 1260 | 648 | 61 | 6 |
| 11 Nov 2026 | 56 | 311 | 250 | 47 | 0 |
| 12 Nov 2026 | 30 | 174 | 131 | 23 | 0 |
| 13 Nov 2026 | 68 | 335 | 337 | 52 | 0 |
| 14 Nov 2026 | 14 | 20 | 21 | 9 | 0 |
| 15 Nov 2026 | 10 | 47 | 46 | 9 | 0 |
| 16 Nov 2026 | 19 | 115 | 192 | 18 | 11 |
| 17 Nov 2026 | 109 | 466 | 542 | 111 | 0 |
| 18 Nov 2026 | 112 | 304 | 253 | 34 | 11 |
| 19 Nov 2026 | 56 | 270 | 423 | 53 | 259 |
| 20 Nov 2026 | 1 | 0 | 6 | 2 | 8 |
Exploit likelihood (EPSS), last 30 days
- Under 1%8076
- 1% to 10%252
- 10% to 50%5
- 50% or more1
- Not scored yet1678
Most affected vendors, last 30 days
- Microsoft1104
- Oracle Corporation578
- Google452
- IBM364
- JetBrains320
- Linux298
- Apache Software Foundation231
- Red Hat146
- Splunk146
- openemr140
Most common weaknesses, last 30 days
- Cross-site scripting (CWE-79)841
- Missing authorization (CWE-862)613
- Use after free (CWE-416)431
- Heap-based buffer overflow (CWE-122)400
- Incorrect authorization (CWE-863)370
- Insecure direct object reference (CWE-639)348
- Path traversal (CWE-22)301
- Improper access control (CWE-284)293
- Information exposure (CWE-200)282
- Out-of-bounds read (CWE-125)269
Matching CVEs
1,557 CVEs match these filters, page 2 of 63.
Splunk AI Assistant insecure direct object reference
High8.1EPSS not scored yetSplunk AI AssistantCVSS 3.1 · 8.1CWE-639
In Splunk AI Assistant versions below 2.0.0 a user who does not hold the "admin" or "power" Splunk roles could access data associated with another tenant and cause actions to be attributed to that tenant through the Representational State Transfer (REST) API. The vulnerability…
Splunk AI Assistant missing authorization
High7.1EPSS not scored yetSplunk AI AssistantCVSS 3.1 · 7.1CWE-862
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…
Splunk App for Stream XML external entity
High7.5EPSS not scored yetSplunk App for StreamCVSS 3.1 · 7.5CWE-611
In Splunk App for Stream versions below 8.1.7, an unauthenticated user who can reach the Splunk App for Stream Representational State Transfer (REST) API on the management port (8089) could upload an Extensible Markup Language (XML) vocabulary file, which lets the vocabulary…
Splunk SOAR insecure direct object reference
High8.1EPSS not scored yetSplunk SOARCVSS 3.1 · 8.1CWE-639
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…
Splunk SOAR untrusted input in a security decision
High8.8EPSS not scored yetSplunk SOARCVSS 3.1 · 8.8CWE-807
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…
Splunk SOAR insecure direct object reference
High8.3EPSS not scored yetSplunk 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…
Splunk SOAR improper privilege management
High7.3EPSS not scored yetSplunk 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…
Splunk SOAR insecure direct object reference
High7.1EPSS not scored yetSplunk 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…
Splunk SOAR sensitive data in logs
High8.1EPSS not scored yetSplunk 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…
Splunk SOAR vulnerability
High7.3EPSS not scored yetSplunk 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…
Splunk SOAR path traversal
High7.2EPSS not scored yetSplunk 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…
Splunk SOAR incorrect authorization
High8.8EPSS not scored yetSplunk 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…
Splunk SOAR path traversal
High8.8EPSS not scored yetSplunk 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…
Splunk SOAR uncontrolled search path
High8.8EPSS not scored yetSplunk 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…
Splunk SOAR uncontrolled search path
High7.2EPSS not scored yetSplunk 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…
Splunk SOAR sensitive data in a response
High7.7EPSS not scored yetSplunk 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…
Splunk SOAR argument injection
High8.8EPSS not scored yetSplunk 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…
Splunk SOAR insecure direct object reference
High7.1EPSS not scored yetSplunk 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…
Splunk SOAR inclusion of untrusted functionality
High8.8EPSS not scored yetSplunk 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…
Splunk SOAR cross-site scripting
High8.7EPSS not scored yetSplunk 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…
Splunk SOAR cross-site scripting
High8.7EPSS not scored yetSplunk 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…
Splunk SOAR inclusion of untrusted functionality
High7.2EPSS not scored yetSplunk 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…
Splunk SOAR incorrectly resolved name
High7.5EPSS not scored yetSplunk 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…
Splunk SOAR missing authorization
High8.8EPSS not scored yetSplunk 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…
Splunk SOAR incorrect authorization
High7.2EPSS not scored yetSplunk 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…
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.