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 13 Nov, 03:10 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 1.6%, higher than 76% of scored CVEsMicrosoft Office and 6 moreCVSS 3.1 · 6.5CWE-356
Google Chromium Use-After-Free Vulnerability
High8.8Exploited, CISA due date 2026-11-24EPSS 0.96%, higher than 62% of scored CVEsGoogle 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 8.9%, higher than 95% of scored CVEsBarracuda Email Security Gateway (ESG) and 5 moreCVSS 4.0 · 9.3CWE-288
Barracuda Networks Multiple Products OS Command Injection Vulnerability
High8.6Exploited, CISA due date 2026-11-13EPSS 6.2%, higher than 94% of scored CVEsBarracuda Email Security Gateway (ESG) and 9 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.64%, higher than 51% of scored CVEsOpenwave Messaging Limited Webtop Media Transcoder and 2 moreCVSS 3.1 · 4.3CWE-669
Trends
The last 30 days, by severity.
5,723 CVEs published, 436 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 |
|---|---|---|---|---|---|
| 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 | 142 | 29 | 0 |
| 5 Nov 2026 | 55 | 213 | 149 | 36 | 0 |
| 6 Nov 2026 | 40 | 148 | 203 | 47 | 6 |
| 7 Nov 2026 | 54 | 164 | 232 | 11 | 13 |
| 8 Nov 2026 | 23 | 128 | 143 | 26 | 0 |
| 9 Nov 2026 | 31 | 165 | 231 | 42 | 1 |
| 10 Nov 2026 | 106 | 1189 | 596 | 45 | 178 |
| 11 Nov 2026 | 51 | 284 | 237 | 44 | 48 |
| 12 Nov 2026 | 28 | 172 | 129 | 23 | 6 |
| 13 Nov 2026 | 7 | 4 | 20 | 16 | 2 |
Exploit likelihood (EPSS), last 30 days
- Under 1%5232
- 1% to 10%188
- 10% to 50%2
- 50% or more4
- Not scored yet297
Most affected vendors, last 30 days
Most common weaknesses, last 30 days
- Cross-site scripting (CWE-79)427
- Heap-based buffer overflow (CWE-122)357
- Use after free (CWE-416)327
- Missing authorization (CWE-862)314
- Insecure direct object reference (CWE-639)202
- Out-of-bounds read (CWE-125)192
- Incorrect authorization (CWE-863)172
- Server-side request forgery (CWE-918)169
- Out-of-bounds write (CWE-787)159
- Path traversal (CWE-22)158
Matching CVEs
2,254 CVEs match these filters, page 8 of 91.
libilbm heap-based buffer overflow
High7.8EPSS 0.17%, higher than 6% of scored CVEslibilbmCVSS 3.0 · 7.8CWE-122
libilbm ILBM File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of libilbm. User interaction is required to exploit this vulnerability in that the target…
Google Chrome use after free
High8.8EPSS 0.25%, higher than 17% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-416
Use after free in Accessibility in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome use after free
High8.8EPSS 0.25%, higher than 17% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-416
Use after free in BrowserTag in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome use after free
High8.8EPSS 0.25%, higher than 17% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-416
Use after free in Layout in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome memory buffer error
High8.8EPSS 0.27%, higher than 19% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-119
Memory corruption in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome integer overflow
High8.8EPSS 0.25%, higher than 17% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-190
Integer overflow in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome use of uninitialized variable
High7.5EPSS 0.28%, higher than 20% of scored CVEsGoogle ChromeCVSS 3.1 · 7.5CWE-457
Use of uninitialized variable in Skia in Google Chrome on on Android prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome use after free
High8.8EPSS 0.28%, higher than 21% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-416
Use after free in Accessibility in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Critical)
Google Chrome type confusion
High8.8EPSS 0.31%, higher than 24% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-843
Type confusion in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome type confusion
High8.8EPSS 0.28%, higher than 20% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-843
Type confusion in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome incomplete cleanup
High8.8EPSS 0.28%, higher than 20% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-459
Incomplete cleanup in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome use after free
High7.5EPSS 0.27%, higher than 19% of scored CVEsGoogle ChromeCVSS 3.1 · 7.5CWE-416
Use after free in Compositing in Google Chrome prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome unchecked unusual condition
High8.1EPSS 0.22%, higher than 12% of scored CVEsGoogle ChromeCVSS 3.1 · 8.1CWE-754
Improper state validation in ANGLE in Google Chrome on on Windows prior to 157.0.8103.78 allowed a remote attacker to bypass web origin policy via a crafted HTML page. (Chromium security severity: High)
Google Chrome incorrectly resolved name
High7.5EPSS 0.28%, higher than 20% of scored CVEsGoogle ChromeCVSS 3.1 · 7.5CWE-706
Incorrect reference resolution in Browser in Google Chrome on on Mac prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome use after free
High8.8EPSS 0.25%, higher than 17% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-416
Use after free in PDF in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome use after free
High8.8EPSS 0.27%, higher than 20% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-416
Use after free in CSS in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome use after free
High8.8EPSS 0.25%, higher than 17% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-416
Use after free in Elements in Google Chrome prior to 157.0.8103.78 allowed a remote attacker leveraging social engineering to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome type confusion
High8.8EPSS 0.30%, higher than 23% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-843
Type confusion in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome missing authorization
High8.1EPSS 0.24%, higher than 15% of scored CVEsGoogle ChromeCVSS 3.1 · 8.1CWE-862
Missing authorization in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to bypass web origin policy via a crafted HTML page. (Chromium security severity: High)
Google Chrome use after free
High8.8EPSS 0.29%, higher than 22% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-416
Use after free in CSS in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Critical)
Google Chrome out-of-bounds write
High8.8EPSS 0.25%, higher than 17% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-787
Out of bounds write in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome use after free
High8.8EPSS 0.27%, higher than 20% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-416
Use after free in MediaStream in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome out-of-bounds read
High8.8EPSS 0.25%, higher than 17% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-125
Out of bounds read in Media in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome vulnerability
High8.8EPSS 0.27%, higher than 20% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-193
Off-by-one error in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Google Chrome heap-based buffer overflow
High8.8EPSS 0.29%, higher than 22% of scored CVEsGoogle ChromeCVSS 3.1 · 8.8CWE-122
Buffer overflow in Turbolev in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
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.