Skip to main content

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, 05:11 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.

  1. 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

  2. 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

  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 8.9%, higher than 95% of scored CVEs

    Barracuda Email Security Gateway (ESG) and 5 moreCVSS 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 6.2%, higher than 94% of scored CVEs

    Barracuda Email Security Gateway (ESG) and 9 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.64%, higher than 51% of scored CVEs

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

Every exploited CVE

Trends

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

CriticalHighMediumLowNot scored15 Oct 2026 to 13 Nov 2026
Show the numbers
DayCriticalHighMediumLowNot scored
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 202635158142290
5 Nov 202655213149360
6 Nov 202640148203476
7 Nov 2026541642321113
8 Nov 202623128143260
9 Nov 202631165231421
10 Nov 2026106118959645178
11 Nov 2026512842374448
12 Nov 202628172129236
13 Nov 202691021174

Exploit likelihood (EPSS), last 30 days

  1. Under 1%5232
  2. 1% to 10%188
  3. 10% to 50%2
  4. 50% or more4
  5. Not scored yet309

Matching CVEs

2,260 CVEs match these filters, page 24 of 91.

  1. CVE-2026-59582

    Google Android integer overflow

    High7.5EPSS 0.39%, higher than 34% of scored CVEs

    Google AndroidCVSS 3.1 · 7.5CWE-190

    In StartTimer of UcePublishManager.cpp, there is a possible way to trigger a process abort during timer calculation due to an integer overflow. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for…

  2. CVE-2026-59578

    Google Android memory buffer error

    High7.8EPSS 0.14%, higher than 3% of scored CVEs

    Google AndroidCVSS 3.1 · 7.8CWE-119

    In s_check_valid_tile_param_custom_tile of av1_encoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

  3. CVE-2026-59573

    Google Android memory buffer error

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

    Google AndroidCVSS 3.1 · 7.8CWE-119

    In max_num_ref_frames of avc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

  4. CVE-2026-58807

    Google Android uncontrolled resource consumption

    High7.5EPSS 0.36%, higher than 30% of scored CVEs

    Google AndroidCVSS 3.1 · 7.5CWE-400

    In Retry_MtsMessageInPending of MtsMessageController.cpp, there is a possible way to trigger memory exhaustion via leaked message objects due to a logic error. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not…

  5. CVE-2026-58804

    Google Android memory buffer error

    High8.4EPSS 0.12%, higher than 2% of scored CVEs

    Google AndroidCVSS 3.1 · 8.4CWE-119

    In ExecuteGraphCommand of multiple files, there is a possible way to trigger an out of bounds write via an oversized scratch memory declaration due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed.…

  6. CVE-2026-58791

    Google Android memory buffer error

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

    Google AndroidCVSS 3.1 · 7.8CWE-119

    In pic_timing of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

  7. CVE-2026-58790

    Google Android memory buffer error

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

    Google AndroidCVSS 3.1 · 7.8CWE-119

    In CMD_ENC_SET_PARAM of encoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

  8. CVE-2026-58789

    Google Android out-of-bounds write

    High7.5EPSS 0.39%, higher than 34% of scored CVEs

    Google AndroidCVSS 3.1 · 7.5CWE-787

    In s_gen_tile_param of multiple files, there is a possible way to trigger an out of bounds write in tile parameter arrays due to an incorrect bounds check. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed…

  9. CVE-2026-58788

    Google Android memory buffer error

    High8.4EPSS 0.12%, higher than 2% of scored CVEs

    Google AndroidCVSS 3.1 · 8.4CWE-119

    In stpropnci_process_std of stpropnci_std.cc, there is a possible way to trigger an out of bounds write into global state due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not…

  10. CVE-2026-58786

    Google Android memory buffer error

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

    Google AndroidCVSS 3.1 · 7.8CWE-119

    In cnm_memset of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

  11. CVE-2026-58757

    Google Android memory buffer error

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

    Google AndroidCVSS 3.1 · 7.8CWE-119

    In mfc_alloc_enc_roi_buffer of mfc_buf.c, there is a possible out-of-bounds write due to a heap buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  12. CVE-2026-58697

    Google Android memory buffer error

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

    Google AndroidCVSS 3.1 · 7.8CWE-119

    In codec3p_secure of codec3p_secure, there is a possible Heap Buffer Overflow due to a missing bounds check. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

  13. CVE-2026-58690

    Google Android integer overflow

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

    Google AndroidCVSS 3.1 · 7.8CWE-190

    In multiple functions of bitmap_image_buffer.h, there is a possible way to trigger an out of bounds write on the trusted execution environment heap due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User…

  14. CVE-2026-57037

    Google Android improper privilege management

    High8.4EPSS 0.12%, higher than 2% of scored CVEs

    Google AndroidCVSS 3.1 · 8.4CWE-269

    In getChppAppState of chpp_init.cc, there is a possible way to trigger an out of bounds read and corrupt task control structures due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction…

  15. CVE-2026-56980

    Google Android integer overflow

    High8.4EPSS 0.12%, higher than 2% of scored CVEs

    Google AndroidCVSS 3.1 · 8.4CWE-190

    In createDataFlowAsync of data_flow_manager.cc, there is a possible way to trigger an out of bounds write in shared memory due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed…

  16. CVE-2026-56966

    Google Android vulnerability

    High8.4EPSS 0.13%, higher than 2% of scored CVEs

    Google AndroidCVSS 3.1 · 8.4

    In CommitToBuffer of hal_override_options.bundle.cc, there is a possible way to retain stale direct memory access mappings to secure memory due to a confused deputy. This could lead to local escalation of privilege with System execution privileges needed. User interaction is…

  17. CVE-2026-56951

    Google Android protection mechanism failure

    High8.4EPSS 0.13%, higher than 2% of scored CVEs

    Google AndroidCVSS 3.1 · 8.4CWE-693

    In on_vkUpdateDescriptorSetWithTemplateSized2GOOGLE of vk_decoder_global_state.cpp, there is a possible way to leak host code pointers to a guest virtual machine due to a logic error. This could lead to local escalation of privilege with no additional execution privileges…

  18. CVE-2026-56933

    Google Android memory buffer error

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

    Google AndroidCVSS 3.1 · 7.8CWE-119

    In RecordApTx of efw_ap_transport.c, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

  19. CVE-2026-56930

    Google Android unintended proxy

    High8.4EPSS 0.12%, higher than 2% of scored CVEs

    Google AndroidCVSS 3.1 · 8.4CWE-441

    In smmu_find_ste of smmu.c, there is a possible way to retain stale translation lookaside buffer entries across stream identifiers due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not…

  20. CVE-2026-56910

    Google Android memory buffer error

    High8.4EPSS 0.12%, higher than 2% of scored CVEs

    Google AndroidCVSS 3.1 · 8.4CWE-119

    In multiple locations, there is a possible way to trigger an out of bounds read and write in shared memory 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…

  21. CVE-2026-55344

    Google Android memory buffer error

    High7.8EPSS 0.13%, higher than 2% of scored CVEs

    Google AndroidCVSS 3.1 · 7.8CWE-119

    In TzSharedMemory of TzSharedMemory.c, there is a possible Heap buffer overflow due to a logic error in the code. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

  22. CVE-2026-55321

    Google Android memory buffer error

    High7.8EPSS 0.13%, higher than 2% of scored CVEs

    Google AndroidCVSS 3.1 · 7.8CWE-119

    In parse_prime256v1 of keymint_asn1.c, there is a possible Heap Buffer Overflow due to a logic error in the code. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

  23. CVE-2026-55312

    Google Android memory buffer error

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

    Google AndroidCVSS 3.1 · 7.8CWE-119

    In insert_node of remap.c, there is a possible way to trigger an out of bounds write in the address remapping table due to a non-heap buffer overflow. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for…

  24. CVE-2026-50077

    BlackBerry Ltd QNX Hypervisor out-of-bounds write

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

    BlackBerry Ltd QNX Hypervisor and 1 moreCVSS 3.1 · 7.7CWE-787

    Invalid Memory Access via the MSI-X table in QVM could allow an attacker in the guest to execute arbitrary code in the QVM to cause memory corruption, information disclosure or a crash of the QVM.

  25. CVE-2026-26248

    Fortinet FortiSandbox cross-site scripting

    High8.8EPSS 0.55%, higher than 47% of scored CVEs

    Fortinet FortiSandbox and 2 moreCVSS 3.1 · 8.8CWE-79

    A improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Fortinet FortiSandbox 5.0.0 through 5.0.5, FortiSandbox 4.4.0 through 4.4.8, FortiSandbox 4.2 all versions, FortiSandbox Cloud 5.0.4 through 5.0.5, FortiSandbox PaaS 5.0.4…

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.