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

323Critical, last 7 days2,255High, 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 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

The last 30 days, by severity.

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

Most affected vendors, last 30 days

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

Matching CVEs

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

  1. CVE-2026-58787

    Google Android heap-based buffer overflow

    High8.8EPSS 0.15%, higher than 5% of scored CVEs

    Google AndroidCVSS 3.1 · 8.8CWE-122

    In chppWifiRangingEventNotification of clients/wifi.c, there is a possible Heap Buffer Overflow due to a logic error in the code. This could lead to remote (proximal/adjacent) escalation of privilege with execution privileges needed. User interaction is for exploitation.

  2. CVE-2026-58786

    Google Android memory buffer error

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

  3. CVE-2026-58757

    Google Android memory buffer error

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

  4. CVE-2026-58740

    Google Android integer overflow

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

    Google AndroidCVSS 3.1 · 7.8CWE-190

    In BitmapImageBuffer of bitmap_image_buffer.h, there is a possible out-of-bounds write due to an integer overflow. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation.

  5. CVE-2026-58697

    Google Android memory buffer error

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

  6. CVE-2026-58690

    Google Android integer overflow

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

  7. CVE-2026-58684

    Google Android protection mechanism failure

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

    Google AndroidCVSS 3.1 · 8.4CWE-693

    In smmu_config_l3tt of smmu.c, there is a possible permission bypass due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  8. CVE-2026-57037

    Google Android improper privilege management

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

  9. CVE-2026-57036

    Google Android protection mechanism failure

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

    Google AndroidCVSS 3.1 · 8.4CWE-693

    In send_vdu_directive of gdmc/gsp/dev/bmsm/plat/lga/vdu.c, there is a possible Logic error 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.

  10. CVE-2026-57009

    Google Android protection mechanism failure

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

    Google AndroidCVSS 3.1 · 8.4CWE-693

    In GC2AvcDec of GC2AvcDec.cpp, there is a possible Logic error 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.

  11. CVE-2026-57005

    Google Android unintended proxy

    High8.8EPSS 0.17%, higher than 6% of scored CVEs

    Google AndroidCVSS 3.1 · 8.8CWE-441

    In EuiccPort.buildUiccAccessRule of EuiccPort.java, there is a possible Confused Deputy due to a confused deputy. This could lead to remote escalation of privilege with execution privileges needed. User interaction is for exploitation.

  12. CVE-2026-57004

    Google Android out-of-bounds write

    High8.4EPSS 0.17%, higher than 6% of scored CVEs

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

    In PresenceDecoderV1::DecodeDataElements of presence_decoder_v1.cc, there is a possible out-of-bounds write due to a missing bounds check. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for…

  13. CVE-2026-56980

    Google Android integer overflow

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

  14. CVE-2026-56969

    Google Android use after free

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

    Google AndroidCVSS 3.1 · 7.8CWE-416

    In edgetpu_group_clear_responses of edgetpu_group.c, there is a possible Use After Free 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.

  15. CVE-2026-56966

    Google Android vulnerability

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

  16. CVE-2026-56951

    Google Android protection mechanism failure

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

  17. CVE-2026-56944

    Google Android use after free

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

    Google AndroidCVSS 3.1 · 7.8CWE-416

    In smmu_detach_dev of private/google-modules/iommu/arm-smmu-v3/drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c, there is a possible Use After Free due to a logic error in the code. This could lead to local escalation of privilege with User execution privileges needed. User…

  18. CVE-2026-56938

    Google Android race condition

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

    Google AndroidCVSS 3.1 · 7.0CWE-362, CWE-416

    In port_shutdown of ipc.c, there is a possible Use After Free due to a race condition. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

  19. CVE-2026-56934

    Google Android protection mechanism failure

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

    Google AndroidCVSS 3.1 · 7.8CWE-693

    In arm_lpae_split_blk_unmap of drivers/iommu/io-pgtable-arm-common.c, there is a possible Logic error due to a logic error in the code. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation.

  20. CVE-2026-56933

    Google Android memory buffer error

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

  21. CVE-2026-56930

    Google Android unintended proxy

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

  22. CVE-2026-56929

    Google Android protection mechanism failure

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

    Google AndroidCVSS 3.1 · 7.8CWE-693

    In TrustyKeyMintManager::VerifyHat of trusty_keymint_manager.cc, there is a possible Security 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.

  23. CVE-2026-56926

    Google Android unintended proxy

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

    Google AndroidCVSS 3.1 · 8.4CWE-441

    In multiple functions of PssSubscriptionManager.java, there is a possible way to spoof subscription switch results and trigger a device reboot due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User…

  24. CVE-2026-56919

    Google Android unintended proxy

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

    Google AndroidCVSS 3.1 · 8.8CWE-441

    In PackageSignatureChecker of SystemUIGoogleModule.java, there is a possible background activity launch due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.

  25. CVE-2026-56916

    Google Android time-of-check to time-of-use race

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

    Google AndroidCVSS 3.1 · 7.8CWE-367

    In _vqueue_get_avail_buf_locked of trusty/kernel/lib/trusty/vqueue.c, there is a possible Double-read / TOCTOU due to a race condition. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

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.