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 15 Nov, 05:24 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-123039

    Check Point Multiple Products Incorrect Permission Assignment for Critical Resource Vulnerability

    High7.8Exploited, CISA due date 2026-11-16EPSS 1.3%, higher than 70% 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.30%, higher than 23% 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

6,539 CVEs published, 517 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 202623530

Exploit likelihood (EPSS), last 30 days

  1. Under 1%5901
  2. 1% to 10%217
  3. 10% to 50%4
  4. 50% or more3
  5. Not scored yet414

Matching CVEs

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

  1. CVE-2026-59611

    Google Android improper input validation

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

    Google AndroidCVSS 3.1 · 7.5CWE-20

    In multiple locations, there is a possible way to trigger a temporary denial of service via an integer overflow trap due to improper input validation. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for…

  2. CVE-2026-59609

    Google Android use after free

    High8.4EPSS 0.14%, higher than 4% of scored CVEs

    Google AndroidCVSS 3.1 · 8.4CWE-416

    In fence_manager_extract_iif of fence_manager.c, there is a possible way to corrupt kernel memory via fence identifier reuse due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed…

  3. CVE-2026-59608

    Google Android memory buffer error

    High7.8EPSS 0.10%, higher than 1% of scored CVEs

    Google AndroidCVSS 3.1 · 7.8CWE-119

    In tone_mapping_info 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.

  4. CVE-2026-59607

    Google Android protection mechanism failure

    High7.8EPSS 0.16%, higher than 5% of scored CVEs

    Google AndroidCVSS 3.1 · 7.8CWE-693

    In TzPipelineInputExtractor of TzPipelineInputExtractor.cpp, there is a possible Logic check bypass 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.

  5. CVE-2026-59603

    Google Android use after free

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

    Google AndroidCVSS 3.1 · 7.5CWE-416

    In RespondReceivedMessage of MtsMessageController.cpp, there is a possible way to trigger a double free and process abort during message retry handling due to a use after free. This could lead to remote denial of service with no additional execution privileges needed. User…

  6. CVE-2026-59598

    Google Android use after free

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

    Google AndroidCVSS 3.1 · 7.8CWE-416

    In platform_rio_ncp_wdt_handler of edgetpu_rio.c, there is a possible Use After Free due to a use after free. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

  7. CVE-2026-59597

    Google Android protection mechanism failure

    High8.4EPSS 0.15%, higher than 4% of scored CVEs

    Google AndroidCVSS 3.1 · 8.4CWE-693

    In bindDataService of DataServiceManager.java, there is a possible way to retain privileged tunnel management permissions across configuration updates due to a logic error. This could lead to local escalation of privilege with no additional execution privileges needed. User…

  8. CVE-2026-59596

    Google Android vulnerability

    High8.4EPSS 0.10%, higher than 1% of scored CVEs

    Google AndroidCVSS 3.1 · 8.4CWE-453

    In multiple functions of mpu.c, there is a possible way to execute code from non-secure memory in the security coprocessor due to an insecure default value. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not…

  9. CVE-2026-59595

    Google Android uncontrolled resource consumption

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

    Google AndroidCVSS 3.1 · 7.5CWE-400

    In DecodeHeaderComponent of SipStack.cpp, there is a possible way to trigger stack exhaustion via unbounded mutual recursion due to a resource exhaustion. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed…

  10. CVE-2026-59594

    Google Android heap-based buffer overflow

    High7.8EPSS 0.10%, higher than 1% of scored CVEs

    Google AndroidCVSS 3.1 · 7.8CWE-122

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

  11. CVE-2026-59593

    Google Android heap-based buffer overflow

    High7.8EPSS 0.10%, higher than 1% of scored CVEs

    Google AndroidCVSS 3.1 · 7.8CWE-122

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

  12. CVE-2026-59589

    Google Android memory buffer error

    High7.8EPSS 0.10%, higher than 1% of scored CVEs

    Google AndroidCVSS 3.1 · 7.8CWE-119

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

  13. CVE-2026-59587

    Google Android memory buffer error

    High8.4EPSS 0.10%, higher than 1% of scored CVEs

    Google AndroidCVSS 3.1 · 8.4CWE-119

    In stpropnci_prop_st_build_set_custom_polling_cmd of stpropnci_prop_st.cc, there is a possible way to trigger an out of bounds write into global memory due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges…

  14. CVE-2026-59585

    Google Android null pointer dereference

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

    Google AndroidCVSS 3.1 · 7.5CWE-476

    In SetDisplayName of RegInfoContact.cpp, there is a possible denial of service due to a missing null check. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

  15. 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…

  16. CVE-2026-59578

    Google Android memory buffer error

    High7.8EPSS 0.10%, higher than 1% 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.

  17. CVE-2026-59573

    Google Android memory buffer error

    High7.8EPSS 0.08%, higher than 0% 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.

  18. 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…

  19. CVE-2026-58804

    Google Android memory buffer error

    High8.4EPSS 0.08%, higher than 0% 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.…

  20. CVE-2026-58798

    Google Android out-of-bounds write

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

    Google AndroidCVSS 3.1 · 8.8CWE-119, CWE-787

    In multiple functions of cn_Tai.cpp, there is a possible way to trigger an out of bounds write due to memory corruption. This could lead to remote (proximal/adjacent) code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

  21. CVE-2026-58796

    Google Android memory buffer error

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

    Google AndroidCVSS 3.1 · 8.4CWE-119

    In multiple functions of AndroidManifest.xml, there is a possible way to trigger unauthorized firmware updates via exported broadcast receivers due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed.…

  22. CVE-2026-58791

    Google Android memory buffer error

    High7.8EPSS 0.08%, higher than 0% 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.

  23. CVE-2026-58790

    Google Android memory buffer error

    High7.8EPSS 0.08%, higher than 0% 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.

  24. 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…

  25. CVE-2026-58788

    Google Android memory buffer error

    High8.4EPSS 0.08%, higher than 0% 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…

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.