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 18 Nov, 01: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-115731

    Perforce Puppet Enterprise Deserialization of Untrusted Data Vulnerability

    Critical9.4Exploited, CISA due date 2026-12-01EPSS not scored yet

    Perforce Puppet Enterprise and 2 moreCVSS 4.0 · 9.4CWE-94, CWE-502

  2. CVE-2026-123039

    Check Point Multiple Products Incorrect Permission Assignment for Critical Resource Vulnerability

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

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

  3. CVE-2026-114713

    UnrealIRCd Improper Neutralization of Delimiters Vulnerability

    High7.7Exploited, CISA due date 2026-11-16EPSS 0.47%, higher than 41% of scored CVEs

    UnrealIRCdCVSS 3.1 · 7.7CWE-140

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

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

Every exploited CVE

Trends

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

CriticalHighMediumLowNot scored20 Oct 2026 to 18 Nov 2026
Show the numbers
DayCriticalHighMediumLowNot scored
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 202610100
4 Nov 202635160140290
5 Nov 202655213149360
6 Nov 202641149203474
7 Nov 2026551622351012
8 Nov 202623128143260
9 Nov 202632164231421
10 Nov 20261391259649616
11 Nov 202656311250470
12 Nov 202630174131230
13 Nov 202668335337520
14 Nov 202614202190
15 Nov 202610474690
16 Nov 2026161061921823
17 Nov 2026101430481100116
18 Nov 20262231512

Exploit likelihood (EPSS), last 30 days

  1. Under 1%6864
  2. 1% to 10%236
  3. 10% to 50%4
  4. 50% or more3
  5. Not scored yet1158

Matching CVEs

6 CVEs match these filters.

  1. CVE-2026-71304

    pi-hole FTL insufficient session expiration

    High8.8EPSS not scored yet

    pi-hole FTLCVSS 3.1 · 8.8CWE-613

    Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. From 6.0 until 6.7, check_client_auth() in src/api/auth.c detects that a matching session identifier has passed valid_until but still assigns user_id before the expired state can be…

  2. CVE-2026-65966

    pi-hole FTL HTTP response splitting

    Low3.5EPSS not scored yet

    pi-hole FTLCVSS 3.1 · 3.5CWE-113

    Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. From 6.0 until 6.7, validation in src/api/list.c permits spaces for GRAVITY_GROUPS and consequently skips carriage-return and line-feed validation for group names submitted through…

  3. CVE-2026-65964

    pi-hole FTL code injection

    Medium6.6EPSS not scored yet

    pi-hole FTLCVSS 3.1 · 6.6CWE-94, CWE-117

    Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. Prior to 6.7, log_http_access in src/webserver/webserver.c writes attacker-controlled User-Agent content to the access log without output neutralization when debug.api is enabled. If…

  4. CVE-2026-65963

    pi-hole FTL improper input validation

    High7.2EPSS not scored yet

    pi-hole FTLCVSS 3.1 · 7.2CWE-15, CWE-20

    Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. From 6.6.2 until 6.7, PATCH /api/config accepts unfiltered CivetWeb lua_* options through webserver.advancedOpts, while POST /api/teleporter writes attacker-controlled content from a…

  5. CVE-2025-62165

    pi-hole FTL allocation without limits

    Critical9.2EPSS not scored yet

    pi-hole FTLCVSS 4.0 · 9.2CWE-770

    Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. From 6.0 until 6.7, CivetWeb permits unauthenticated clients to flood the WebUI login page and API invalid paths without connection or request-rate limits. Repeated requests can…

  6. CVE-2020-8816

    Pi-Hole AdminLTE Remote Code Execution Vulnerability

    High7.2Exploited, CISA due date 2022-06-10EPSS 78%, higher than 100% of scored CVEs

    Pi-hole AdminLTE and 1 moreCVSS 3.1 · 7.2CWE-78

    Pi-hole Web v4.3.2 (aka AdminLTE) allows Remote Code Execution by privileged dashboard users via a crafted DHCP static lease.

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.