Skip to main content
veriom
Menu

Explore Veriom products, resources, and account pages.

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, 02:49 UTC from NVD, CISA KEV and FIRST EPSSMarkdownRSSJSON Feed

334Critical, last 7 days2,104High, last 7 days40Added to CISA KEV, 30 days1,779Exploited CVEs tracked

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

    Microsoft Office Outlook Missing User Interaction for Potentially Unsafe Action Vulnerability

    Medium6.5Exploited, CISA due date 2026-11-24EPSS not scored yet

    Microsoft Office and 6 moreCVSS 3.1 · 6.5CWE-356

  2. CVE-2026-125350

    Google Chromium Use-After-Free Vulnerability

    High8.8Exploited, CISA due date 2026-11-24EPSS not scored yet

    Google Chromium and 1 moreCVSS 3.1 · 8.8CWE-416

  3. CVE-2026-116606

    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 CVEs

    Barracuda Email Security Gateway (ESG)CVSS 4.0 · 9.3CWE-288

  4. CVE-2026-111560

    Barracuda Networks Multiple Products OS Command Injection Vulnerability

    High8.6Exploited, CISA due date 2026-11-13EPSS 1.1%, higher than 65% of scored CVEs

    Barracuda Email Security Gateway (ESG) and 5 moreCVSS 4.0 · 8.6CWE-78

  5. CVE-2026-111793

    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 CVEs

    Openwave Messaging Limited Webtop Media Transcoder and 2 moreCVSS 3.1 · 4.3CWE-669

Every exploited CVE

Trends

The last 30 days, by severity.

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

CriticalHighMediumLowNot scored13 Oct 2026 to 11 Nov 2026
Show the numbers
DayCriticalHighMediumLowNot scored
13 Oct 202612000
14 Oct 202622000
15 Oct 202612000
16 Oct 202600100
17 Oct 202600000
18 Oct 202600000
19 Oct 202600000
20 Oct 202600000
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 202600100
4 Nov 202635158138321
5 Nov 202655213148361
6 Nov 202640146205476
7 Nov 2026571612321113
8 Nov 202623128143260
9 Nov 2026221492184239
10 Nov 2026103115158743233
11 Nov 202624610

Exploit likelihood (EPSS), last 30 days

  1. Under 1%713
  2. 1% to 10%25
  3. 10% to 50%2
  4. 50% or more7
  5. Not scored yet3928

Most affected vendors, last 30 days

  1. Microsoft1096
  2. IBM322
  3. Google168
  4. Apache Software Foundation157
  5. FFmpeg121
  6. Adobe112
  7. Mozilla108
  8. JetBrains89
  9. Red Hat77
  10. openemr60

Matching CVEs

9 CVEs match these filters.

  1. CVE-2026-123569

    sveltejs devalue allocation without limits

    High8.7EPSS not scored yet

    sveltejs devalueCVSS 4.0 · 8.7CWE-770

    The devalue package for npm before 5.6.3 can consume excessive CPU and memory when serializing sparse arrays with uneval or stringify. An attacker who manages to get a sparse array created on the server, which mainstream wire formats do not allow, and serialized there can cause…

  2. CVE-2026-123568

    sveltejs devalue prototype pollution

    Low2.1EPSS not scored yet

    sveltejs devalueCVSS 4.0 · 2.1CWE-1321

    Sveltejs devalue before 5.6.3 contains a prototype pollution vulnerability that allows attackers to alter object prototypes by supplying untrusted data to uneval. When the generated code is later evaluated, it creates objects with polluted prototypes, producing output data…

  3. CVE-2026-123567

    sveltejs devalue prototype pollution

    Medium6.3EPSS not scored yet

    sveltejs devalueCVSS 4.0 · 6.3CWE-1321

    Sveltejs devalue before 5.6.4 contains a prototype injection vulnerability that allows attackers to inject __proto__ own properties into objects returned by devalue.parse and devalue.unflatten. Attackers can supply crafted serialized input that, when downstream code merges…

  4. CVE-2026-123566

    sveltejs devalue uncontrolled resource consumption

    High8.7EPSS not scored yet

    sveltejs devalueCVSS 4.0 · 8.7CWE-400

    Sveltejs devalue before 5.9.3 contains a denial of service vulnerability that allows attackers to cause CPU amplification by supplying sparse arrays to uneval. Attackers who influence sparse values passed to uneval can force synchronous work proportional to the declared array…

  5. CVE-2026-123565

    sveltejs devalue uncontrolled resource consumption

    High8.7EPSS not scored yet

    sveltejs devalueCVSS 4.0 · 8.7CWE-400

    Sveltejs devalue before 5.9.3 contains a resource exhaustion vulnerability where repeated primitive strings cause quadratic expansion in the uneval function. Attackers can supply a small crafted payload that is parsed and then passed to uneval, producing a very large serialized…

  6. CVE-2026-123564

    sveltejs devalue allocation without limits

    High8.7EPSS not scored yet

    sveltejs devalueCVSS 4.0 · 8.7CWE-770

    Sveltejs devalue from 1.0.0 before 5.9.3 contains a memory exhaustion flaw in uneval, whose generated code for sparse arrays allocates memory proportional to the array's declared length when evaluated. Attackers who can influence a very large sparse array serialized by an…

  7. CVE-2026-123563

    sveltejs devalue excessive memory allocation

    High8.7EPSS not scored yet

    sveltejs devalueCVSS 4.0 · 8.7CWE-789

    Devalue before 5.9.3 contains a validation bypass vulnerability that allows custom ArrayBuffer revivers to skip typed-array allocation checks in the parse function. Attackers can supply very small crafted input processed by a malformed ArrayBuffer reviver to allocate massive…

  8. CVE-2026-123562

    sveltejs devalue uncaught exception

    High8.7EPSS not scored yet

    sveltejs devalueCVSS 4.0 · 8.7CWE-248

    devalue (sveltejs/devalue) 5.8.0 before 5.9.3 contains an unhandled promise rejection in stringifyAsync: when serializing multiple promises, a later promise rejecting before an earlier one settles leaves an internal rejection unhandled, even if the caller catches the returned…

  9. CVE-2026-123561

    sveltejs devalue prototype pollution

    Medium6.3EPSS not scored yet

    sveltejs devalueCVSS 4.0 · 6.3CWE-1321

    devalue before 5.9.3 allows malformed null-prototype object keys to bypass parse's __proto__ rejection through property-key coercion, an incomplete fix for GHSA-mwv9-gp5h-frr4. Attackers can supply crafted payloads that yield objects with a __proto__ own property, which alone…

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.

See how Veriom maps an architectureTake the interactive tour

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.