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 11 Nov, 04: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.
Microsoft Office Outlook Missing User Interaction for Potentially Unsafe Action Vulnerability
Medium6.5Exploited, CISA due date 2026-11-24EPSS not scored yetMicrosoft Office and 6 moreCVSS 3.1 · 6.5CWE-356
Google Chromium Use-After-Free Vulnerability
High8.8Exploited, CISA due date 2026-11-24EPSS not scored yetGoogle Chromium and 1 moreCVSS 3.1 · 8.8CWE-416
Barracuda Networks Email Security Gateway (ESG) Authentication Bypass Using an Alternate Path or Channel Vulnerability
Critical9.3Exploited, CISA due date 2026-11-13EPSS 1.6%, higher than 76% of scored CVEsBarracuda Email Security Gateway (ESG)CVSS 4.0 · 9.3CWE-288
Barracuda Networks Multiple Products OS Command Injection Vulnerability
High8.6Exploited, CISA due date 2026-11-13EPSS 1.1%, higher than 65% of scored CVEsBarracuda Email Security Gateway (ESG) and 5 moreCVSS 4.0 · 8.6CWE-78
Openwave Messaging Limited Webtop Media Transcoder Incorrect Resource Transfer Between Spheres Vulnerability
Medium4.3Exploited, CISA due date 2026-11-24EPSS 0.27%, higher than 20% of scored CVEsOpenwave Messaging Limited Webtop Media Transcoder and 2 moreCVSS 3.1 · 4.3CWE-669
Trends
The last 30 days, by severity.
4,691 CVEs published, 346 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 |
|---|---|---|---|---|---|
| 13 Oct 2026 | 1 | 2 | 0 | 0 | 0 |
| 14 Oct 2026 | 2 | 2 | 0 | 0 | 0 |
| 15 Oct 2026 | 1 | 2 | 0 | 0 | 0 |
| 16 Oct 2026 | 0 | 0 | 1 | 0 | 0 |
| 17 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 18 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 19 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 20 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 21 Oct 2026 | 2 | 0 | 0 | 0 | 0 |
| 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 | 0 | 0 | 1 | 0 | 0 |
| 4 Nov 2026 | 35 | 158 | 138 | 32 | 1 |
| 5 Nov 2026 | 55 | 213 | 148 | 36 | 1 |
| 6 Nov 2026 | 40 | 146 | 205 | 47 | 6 |
| 7 Nov 2026 | 57 | 161 | 232 | 11 | 13 |
| 8 Nov 2026 | 23 | 128 | 143 | 26 | 0 |
| 9 Nov 2026 | 22 | 149 | 218 | 42 | 39 |
| 10 Nov 2026 | 103 | 1151 | 587 | 43 | 233 |
| 11 Nov 2026 | 2 | 11 | 15 | 1 | 0 |
Exploit likelihood (EPSS), last 30 days
- Under 1%713
- 1% to 10%25
- 10% to 50%2
- 50% or more7
- Not scored yet3944
Most affected vendors, last 30 days
Most common weaknesses, last 30 days
- Heap-based buffer overflow (CWE-122)343
- Cross-site scripting (CWE-79)329
- Use after free (CWE-416)276
- Missing authorization (CWE-862)230
- Out-of-bounds read (CWE-125)172
- Insecure direct object reference (CWE-639)164
- Server-side request forgery (CWE-918)147
- Path traversal (CWE-22)128
- Out-of-bounds write (CWE-787)127
- Incorrect authorization (CWE-863)127
Matching CVEs
266 CVEs match these filters, page 10 of 11.
Google Chromium V8 Memory Corruption Vulnerability
High8.8Exploited, CISA due date 2021-11-17EPSS 39%, higher than 99% of scored CVEsGoogle Chromium V8 and 3 moreCVSS 3.1 · 8.8CWE-755
Inappropriate implementation in V8 in Google Chrome prior to 95.0.4638.69 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Google Chromium Intents Improper Input Validation Vulnerability
Medium6.1Exploited, CISA due date 2021-11-17EPSS 4.9%, higher than 92% of scored CVEsGoogle Chromium Intents and 4 moreCVSS 3.1 · 6.1CWE-601, CWE-20
Insufficient validation of untrusted input in Intents in Google Chrome on Android prior to 95.0.4638.69 allowed a remote attacker to arbitrarily browser to a malicious URL via a crafted HTML page.
Google Chromium Information Disclosure Vulnerability
Medium6.5Exploited, CISA due date 2021-11-17EPSS 20%, higher than 97% of scored CVEsGoogle Chromium and 3 moreCVSS 3.1 · 6.5CWE-862
Inappropriate implementation in Memory in Google Chrome prior to 94.0.4606.71 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page.
Google Chromium V8 Use-After-Free Vulnerability
High8.8Exploited, CISA due date 2021-11-17EPSS 35%, higher than 98% of scored CVEsGoogle Chromium V8 and 3 moreCVSS 3.1 · 8.8CWE-416
Use after free in V8 in Google Chrome prior to 94.0.4606.71 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Google Chromium Portals Use-After-Free Vulnerability
Critical9.6Exploited, CISA due date 2021-11-17EPSS 12%, higher than 96% of scored CVEsGoogle Chromium Portals and 3 moreCVSS 3.1 · 9.6CWE-416
Use after free in Portals in Google Chrome prior to 94.0.4606.61 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.
Google Chromium Indexed DB API Use-After-Free Vulnerability
Critical9.6Exploited, CISA due date 2021-11-17EPSS 33%, higher than 98% of scored CVEsGoogle Chromium Indexed DB API and 2 moreCVSS 3.1 · 9.6CWE-416
Use after free in Indexed DB API in Google Chrome prior to 93.0.4577.82 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.
Google Chromium V8 Out-of-Bounds Write Vulnerability
High8.8Exploited, CISA due date 2021-11-17EPSS 63%, higher than 99% of scored CVEsGoogle Chromium V8 and 2 moreCVSS 3.1 · 8.8CWE-787
Out of bounds write in V8 in Google Chrome prior to 93.0.4577.82 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Google Chromium V8 Type Confusion Vulnerability
High8.8Exploited, CISA due date 2021-11-17EPSS 9.0%, higher than 95% of scored CVEsGoogle Chromium V8 and 1 moreCVSS 3.1 · 8.8CWE-843
Type Confusion in V8 in Google Chrome prior to 91.0.4472.164 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Google Chromium WebGL Use-After-Free Vulnerability
High8.8Exploited, CISA due date 2021-11-17EPSS 7.4%, higher than 94% of scored CVEsGoogle Chromium WebGL and 2 moreCVSS 3.1 · 8.8CWE-416
Use after free in WebGL in Google Chrome prior to 91.0.4472.114 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Google Chromium V8 Type Confusion Vulnerability
High8.8Exploited, CISA due date 2021-11-17EPSS 65%, higher than 99% of scored CVEsGoogle Chromium V8 and 2 moreCVSS 3.1 · 8.8CWE-843
Type confusion in V8 in Google Chrome prior to 91.0.4472.101 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Google Chromium PopupBlocker Security Bypass Vulnerability
Medium6.5Exploited, CISA due date 2022-07-18EPSS 17%, higher than 97% of scored CVEsGoogle Chromium PopupBlocker and 2 moreCVSS 3.1 · 6.5CWE-863
Insufficient policy enforcement in PopupBlocker in Google Chrome prior to 91.0.4472.77 allowed a remote attacker to bypass navigation restrictions via a crafted iframe.
Google Chromium V8 Type Confusion Vulnerability
High8.8Exploited, CISA due date 2021-11-17EPSS 84%, higher than 100% of scored CVEsGoogle Chromium V8 and 3 moreCVSS 3.1 · 8.8CWE-843
Type confusion in V8 in Google Chrome prior to 90.0.4430.85 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page.
Google Chromium V8 Improper Input Validation Vulnerability
High8.8Exploited, CISA due date 2021-11-17EPSS 70%, higher than 99% of scored CVEsGoogle Chromium V8 and 2 moreCVSS 3.1 · 8.8CWE-787
Insufficient validation of untrusted input in V8 in Google Chrome prior to 89.0.4389.128 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Google Chromium Blink Use-After-Free Vulnerability
High8.8Exploited, CISA due date 2021-11-17EPSS 9.3%, higher than 95% of scored CVEsGoogle Chromium Blink and 2 moreCVSS 3.1 · 8.8CWE-416
Use after free in Blink in Google Chrome prior to 89.0.4389.128 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Google Chromium Blink Use-After-Free Vulnerability
High8.8Exploited, CISA due date 2021-11-17EPSS 10.0%, higher than 96% of scored CVEsGoogle Chromium Blink and 3 moreCVSS 3.1 · 8.8CWE-416
Use after free in Blink in Google Chrome prior to 89.0.4389.90 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Google Chromium Race Condition Vulnerability
High8.8Exploited, CISA due date 2021-11-17EPSS 24%, higher than 98% of scored CVEsGoogle Chromium and 3 moreCVSS 3.1 · 8.8CWE-362
Data race in audio in Google Chrome prior to 89.0.4389.72 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Google Chromium V8 Heap Buffer Overflow Vulnerability
High8.8Exploited, CISA due date 2021-11-17EPSS 20%, higher than 97% of scored CVEsGoogle Chromium V8 and 3 moreCVSS 3.1 · 8.8CWE-787
Heap buffer overflow in V8 in Google Chrome prior to 88.0.4324.150 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Google Chrome Media Use-After-Free Vulnerability
High8.8Exploited, CISA due date 2022-07-10EPSS 11%, higher than 96% of scored CVEsGoogle Chrome Media and 1 moreCVSS 3.1 · 8.8CWE-416
Use after free in Media in Google Chrome prior to 81.0.4044.92 allowed a remote attacker to execute arbitrary code via a crafted HTML page.
Google Chrome Use-After-Free Vulnerability
Critical9.6Exploited, CISA due date 2022-05-03EPSS 2.7%, higher than 86% of scored CVEsGoogle ChromeCVSS 3.1 · 9.6CWE-416
Use after free in site isolation in Google Chrome prior to 86.0.4240.198 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.
Google Chromium V8 Incorrect Implementation Vulnerabililty
High8.8Exploited, CISA due date 2022-05-03EPSS 2.8%, higher than 86% of scored CVEsGoogle Chromium V8 and 1 moreCVSS 3.1 · 8.8CWE-787
Inappropriate implementation in V8 in Google Chrome prior to 86.0.4240.198 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Google Chrome for Android UI Heap Buffer Overflow Vulnerability
Critical9.6Exploited, CISA due date 2022-05-03EPSS 6.4%, higher than 94% of scored CVEsGoogle Chrome for Android UI and 2 moreCVSS 3.1 · 9.6CWE-787, CWE-122
Heap buffer overflow in UI in Google Chrome on Android prior to 86.0.4240.185 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.
Google Chromium V8 Type Confusion Vulnerability
High8.8Exploited, CISA due date 2022-05-03EPSS 48%, higher than 99% of scored CVEsGoogle Chromium V8 and 8 moreCVSS 3.1 · 8.8CWE-787, CWE-843
Inappropriate implementation in V8 in Google Chrome prior to 86.0.4240.183 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Google Chrome FreeType Heap Buffer Overflow Vulnerability
Critical9.6Exploited, CISA due date 2021-11-17EPSS 64%, higher than 99% of scored CVEsGoogle Chrome FreeType and 6 moreCVSS 3.1 · 9.6CWE-787, CWE-120
Heap buffer overflow in Freetype in Google Chrome prior to 86.0.4240.111 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Mediatek Multiple Chipsets Insufficient Input Validation Vulnerability
High7.8Exploited, CISA due date 2022-05-03EPSS 1.4%, higher than 72% of scored CVEsAndroid and 9 moreCVSS 3.1 · 7.8CWE-787
In the ioctl handlers of the Mediatek Command Queue driver, there is a possible out of bounds write due to insufficient input sanitization and missing SELinux restrictions. This could lead to local escalation of privilege with no additional execution privileges needed. User…
Android Kernel Out-of-Bounds Write Vulnerability
High7.8Exploited, CISA due date 2022-05-03EPSS 3.2%, higher than 88% of scored CVEsAndroid Kernel and 2 moreCVSS 3.1 · 7.8CWE-20
In binder_transaction of binder.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product:…
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.
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.