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 15 Nov, 12:25 UTC from NVD, CISA KEV and FIRST EPSSMarkdownRSSJSON Feed

323Critical, last 7 days2,257High, last 7 days35Added to CISA KEV, 30 days1,781Exploited 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-123039

    Check Point Multiple Products Incorrect Permission Assignment for Critical Resource Vulnerability

    High7.8Exploited, CISA due date 2026-11-16EPSS 2.2%, higher than 83% of scored CVEs

    checkpoint Quantum Security Gateway and 1 moreCVSS 3.1 · 7.8CWE-732, CWE-862

  2. CVE-2026-114713

    UnrealIRCd Improper Neutralization of Delimiters Vulnerability

    High8.6Exploited, CISA due date 2026-11-16EPSS 0.51%, higher than 44% of scored CVEs

    UnrealIRCdCVSS 3.1 · 8.6CWE-140

  3. CVE-2026-124194

    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 CVEs

    Microsoft Office and 6 moreCVSS 3.1 · 6.5CWE-356

  4. CVE-2026-125350

    Google Chromium Use-After-Free Vulnerability

    High8.8Exploited, CISA due date 2026-11-24EPSS 0.96%, higher than 62% of scored CVEs

    Google Chromium and 1 moreCVSS 3.1 · 8.8CWE-416

  5. 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 11%, higher than 96% of scored CVEs

    Barracuda Email Security Gateway (ESG) and 5 moreCVSS 4.0 · 9.3CWE-288

Every exploited CVE

Trends

The last 30 days, by severity.

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

CriticalHighMediumLowNot scored17 Oct 2026 to 15 Nov 2026
Show the numbers
DayCriticalHighMediumLowNot scored
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 202635158142290
5 Nov 202655213149360
6 Nov 202641148202476
7 Nov 2026541652321013
8 Nov 202623128143260
9 Nov 202632164231421
10 Nov 202611712216236192
11 Nov 2026512852374447
12 Nov 202628172129236
13 Nov 202667327337529
14 Nov 202671312626
15 Nov 2026485412

Exploit likelihood (EPSS), last 30 days

  1. Under 1%6252
  2. 1% to 10%225
  3. 10% to 50%4
  4. 50% or more3
  5. Not scored yet75

Most affected vendors, last 30 days

  1. Microsoft1095
  2. IBM343
  3. Google249
  4. Apache Software Foundation199
  5. openemr140
  6. Red Hat124
  7. FFmpeg121
  8. Adobe112
  9. Mozilla108
  10. Fortinet98

Matching CVEs

2,313 CVEs match these filters, page 92 of 93.

  1. CVE-2026-123576

    hickory-dns allocation without limits

    High8.7EPSS 0.41%, higher than 36% of scored CVEs

    hickory-dnsCVSS 4.0 · 8.7CWE-770

    Hickory DNS 0.24.0 through 0.26.1 contains a memory exhaustion vulnerability that allows remote attackers to consume server resources by sending incomplete DNS-over-QUIC request bodies. Attackers can open many connections and send only large length prefixes, causing…

  2. CVE-2026-123575

    hickory-dns allocation without limits

    High8.7EPSS 0.41%, higher than 36% of scored CVEs

    hickory-dnsCVSS 4.0 · 8.7CWE-770

    Hickory DNS before 0.26.2 contains a resource exhaustion vulnerability in its DNS-over-HTTPS HTTP/2 server that lacks sufficient timeouts or limits for incomplete request bodies. Remote attackers can open DoH connections, send incomplete request bodies, and hold connections…

  3. CVE-2026-123574

    hickory-dns improper input validation

    High8.7EPSS 0.34%, higher than 28% of scored CVEs

    hickory-dnsCVSS 4.0 · 8.7CWE-20

    The zone file parser in the hickory-proto crate of Hickory DNS 0.24.0 before 0.26.2 panics when a single token in a zone file is 4096 bytes or longer. Attackers who can supply untrusted zone files to an application using the parser can trigger the panic to cause a denial of…

  4. CVE-2026-123573

    hickory-dns improper input validation

    High8.7EPSS 0.34%, higher than 28% of scored CVEs

    hickory-dnsCVSS 4.0 · 8.7CWE-20

    hickory-dns from 0.20.1 before 0.26.2 contains a denial of service vulnerability in the hickory-proto SVCB and HTTPS record presentation format parser. Attackers can supply untrusted zone files where only a single or double quote replaces a service parameter value, triggering a…

  5. CVE-2026-123572

    hickory-dns vulnerability

    High8.7EPSS 0.34%, higher than 28% of scored CVEs

    hickory-dnsCVSS 4.0 · 8.7CWE-1286

    Hickory-dns from 0.20.1 before 0.26.2 contains a denial of service vulnerability in the hickory-proto SVCB and HTTPS record presentation format parser, which panics on malformed alpn values. Attackers can supply untrusted zone files with unbalanced quotes, consecutive commas,…

  6. CVE-2026-123571

    hickory-dns integer underflow

    High8.7EPSS 0.41%, higher than 36% of scored CVEs

    hickory-dnsCVSS 4.0 · 8.7CWE-191

    Hickory DNS from 0.26.0 before 0.26.2 contains an integer underflow vulnerability in TSIG RDATA decoding that allows remote attackers to trigger a panic via malformed records. Attackers can send a crafted TSIG record in DNS wire format to cause unchecked subtraction underflow,…

  7. CVE-2026-123570

    hickory-dns uncontrolled resource consumption

    High8.7EPSS 0.41%, higher than 36% of scored CVEs

    hickory-dnsCVSS 4.0 · 8.7CWE-400

    The DNS wire-format message parser in hickory-proto (Hickory DNS) 0.18 before 0.26.2 preallocates record vectors sized by the untrusted ANCOUNT, NSCOUNT, and ARCOUNT header fields before reading record data. Remote attackers can send a UDP datagram, or a spoofed response to a…

  8. CVE-2026-123569

    sveltejs devalue allocation without limits

    High8.7EPSS 0.34%, higher than 28% of scored CVEs

    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…

  9. CVE-2026-123566

    sveltejs devalue uncontrolled resource consumption

    High8.7EPSS 0.34%, higher than 28% of scored CVEs

    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…

  10. CVE-2026-123565

    sveltejs devalue uncontrolled resource consumption

    High8.7EPSS 0.34%, higher than 28% of scored CVEs

    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…

  11. CVE-2026-123564

    sveltejs devalue allocation without limits

    High8.7EPSS 0.34%, higher than 28% of scored CVEs

    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…

  12. CVE-2026-123563

    sveltejs devalue excessive memory allocation

    High8.7EPSS 0.38%, higher than 32% of scored CVEs

    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…

  13. CVE-2026-123562

    sveltejs devalue uncaught exception

    High8.7EPSS 0.34%, higher than 28% of scored CVEs

    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…

  14. CVE-2026-123560

    ZcashFoundation zebra incomplete cleanup

    High8.7EPSS 0.34%, higher than 28% of scored CVEs

    ZcashFoundation zebraCVSS 4.0 · 8.7CWE-459

    Zebra before 7.0.0 contains an incomplete cleanup vulnerability that allows unauthenticated peers to stall initial sync by serving a forged checkpoint block body. Attackers can supply a body with forged authorizing data near the final checkpoint, leaving rejected hashes in the…

  15. CVE-2026-123559

    ZcashFoundation zebra inefficient algorithmic complexity

    High8.7EPSS 0.34%, higher than 28% of scored CVEs

    ZcashFoundation zebraCVSS 4.0 · 8.7CWE-407

    Zebra before 7.0.0 contains an inefficient algorithmic complexity vulnerability that allows unauthenticated peers to exhaust verification threads by submitting transactions with many transparent inputs. Attackers can relay invalid transactions with tens of thousands of inputs,…

  16. CVE-2026-123558

    ZcashFoundation zebra vulnerability

    High8.7EPSS 0.34%, higher than 28% of scored CVEs

    ZcashFoundation zebraCVSS 4.0 · 8.7CWE-460

    Zebra zebrad before 7.0.0 contains a denial of service vulnerability that allows a malicious peer to stall checkpoint sync by cancelling the verifier rewind after a failed commit. Attackers can serve a forged block with altered authorizing data plus a restart-triggering block,…

  17. CVE-2026-123557

    ZcashFoundation zebra reachable assertion

    High8.2EPSS 0.31%, higher than 24% of scored CVEs

    ZcashFoundation zebraCVSS 4.0 · 8.2CWE-617

    ZcashFoundation Zebra zebrad before 7.0.0 contains a reachable assertion race condition that allows unauthenticated remote peers to abort the node by triggering disconnection during a blocked outbound send. Malicious peers can return empty FindBlocks or FindHeaders replies and…

  18. CVE-2026-123555

    ZcashFoundation zebra improper exception handling

    High8.7EPSS 0.43%, higher than 38% of scored CVEs

    ZcashFoundation zebraCVSS 4.0 · 8.7CWE-755

    Zebra from 2.3.0 before 7.0.0 contains a denial of service vulnerability that allows unauthenticated peers to evade misbehavior scoring by sending transactions or blocks with invalid transparent scripts. Attackers can flood mempool with script-failing transactions or serve…

  19. CVE-2026-123554

    ZcashFoundation zebra inefficient algorithmic complexity

    High8.7EPSS 0.43%, higher than 38% of scored CVEs

    ZcashFoundation zebraCVSS 4.0 · 8.7CWE-407

    Zebra zebrad 6.4.0 before 7.0.0 performs quadratic work in the mempool coinbase-maturity check because Transaction::coinbase_spend_restriction() rebuilds the transaction's output list once per spent outpoint. Any connected peer can repeatedly send unsigned transactions with…

  20. CVE-2026-123545

    OpenIdentityPlatform OpenAM cross-site request forgery

    High7.1EPSS 0.12%, higher than 2% of scored CVEs

    OpenIdentityPlatform OpenAMCVSS 4.0 · 7.1CWE-352

    OpenAM from 14.5.1 before 16.1.4 contains a cross-site request forgery vulnerability in the OAuth 2.0 device authorization flow that allows attackers to approve device codes when consent is skipped for implied-consent clients. Attackers can start a device authorization and lure…

  21. CVE-2026-123543

    OpenIdentityPlatform OpenAM allocation without limits

    High8.7EPSS 0.39%, higher than 34% of scored CVEs

    OpenIdentityPlatform OpenAMCVSS 4.0 · 8.7CWE-770

    OpenAM before 16.1.4 contains a denial of service vulnerability that allows unauthenticated attackers to exhaust server resources by sending serialized Java data without size or structure limits. Attackers can send small crafted requests to remote SDK endpoints, classic login…

  22. CVE-2026-123542

    OpenIdentityPlatform OpenAM vulnerability

    High7.6EPSS 0.25%, higher than 17% of scored CVEs

    OpenIdentityPlatform OpenAMCVSS 4.0 · 7.6CWE-358

    OpenAM before 16.1.4 fails to enforce PKCE in the OAuth 2.0 device authorization flow, never validating the code verifier when device codes are exchanged for tokens. Attackers who obtain an approved device code from client logs or shared device storage can redeem it for access…

  23. CVE-2026-123538

    OpenIdentityPlatform OpenAM improper signature verification

    High7.5EPSS 0.13%, higher than 3% of scored CVEs

    OpenIdentityPlatform OpenAMCVSS 4.0 · 7.5CWE-347

    OpenAM before 16.1.4 does not verify that a signed SAML 1.x assertion or response was signed by the partner named as its issuer, accepting a signature from any certificate in OpenAM's keystore. An attacker holding such a private key, such as a trusted SAML 1.x partner, can…

  24. CVE-2026-123534

    tornadoweb tornado path traversal

    High8.3EPSS 0.34%, higher than 28% of scored CVEs

    tornadoweb tornadoCVSS 4.0 · 8.3CWE-22

    Tornado before 6.6 contains a path traversal vulnerability in RequestHandler.static_url() and get_version() that allows attackers to hash files outside static_path using ../ sequences. Attackers controlling input passed to static_url() can obtain SHA-512 hashes of readable…

  25. CVE-2026-123532

    GitoxideLabs gitoxide link following

    High7.1EPSS 0.58%, higher than 48% of scored CVEs

    GitoxideLabs gitoxideCVSS 4.0 · 7.1CWE-59

    gix-fs in gitoxide before 0.24.1 contains a credential disclosure vulnerability that allows remote attackers to capture NTLM credentials by supplying UNC symlink targets in a crafted repository. When a victim checks out the repository on Windows with symlinks enabled,…

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.