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

12 CVEs match these filters.

  1. CVE-2026-122153

    ICRTouch TouchOffice information exposure

    High7.5EPSS not scored yet

    ICRTouch TouchOfficeCVSS 3.1 · 7.5CWE-200

    The TouchOffice API `clerkList` endpoint appears to return sensitive clerk authentication data, including clerk PINs and iButton serial numbers. If the endpoint is accessible to callers who do not require access to these values, the API exposes reusable authentication material…

  2. CVE-2026-122152

    ICRTouch TouchTakeaway vulnerability

    Not scoredEPSS not scored yet

    ICRTouch TouchTakeawayNot scored yet

    The ICRTouch white-label TouchTakeaway Cordova applications do not implement certificate or public-key pinning for backend HTTPS connections. The applications therefore rely exclusively on the device’s system trust store when validating server certificates. An attacker who can…

  3. CVE-2026-122150

    ICRTouch TouchPoint POS improper authentication

    Critical9.1EPSS not scored yet

    ICRTouch TouchPoint POS and 1 moreCVSS 3.1 · 9.1CWE-287

    The PocketTouch and TouchPoint POS `CHECKPAYMENT` workflow accepts a caller-supplied clerk number without adequately verifying that the requesting client is authorized to act as that clerk. An attacker with access to the POS protocol may be able to specify another employee’s…

  4. CVE-2026-122149

    ICRTouch TouchPoint POS missing authentication

    Critical9.1EPSS not scored yet

    ICRTouch TouchPoint POS and 1 moreCVSS 3.1 · 9.1CWE-306

    The PocketTouch and TouchPoint POS protocol includes a `SAVECONFIG` command that appears capable of overwriting till configuration files remotely. An attacker with network access to the POS socket service may be able to submit a crafted `SAVECONFIG` command and replace or…

  5. CVE-2026-122147

    ICRTouch PocketTouch hard-coded credentials

    Critical9.8EPSS not scored yet

    ICRTouch PocketTouchCVSS 3.1 · 9.8CWE-798

    ICRTouch PocketTouch version 1.700 build 2025.3726 defines hard-coded default values for multiple credential fields, including a socket password and configuration and shutdown passwords. An additional email-related password field is initialized without a value.

  6. CVE-2026-122145

    ICRTouch PocketTouch cleartext transmission

    High7.5EPSS not scored yet

    ICRTouch PocketTouchCVSS 3.1 · 7.5CWE-319

    ICRTouch PocketTouch version 1.700 build 2025.3726 transmits the POS socket password in plaintext XML over an unencrypted TCP connection. The protocol does not provide transport-layer encryption to protect credentials from interception. An attacker able to observe network…

  7. CVE-2026-122143

    ICRTouch Commander exposed dangerous method

    High7.5EPSS not scored yet

    ICRTouch CommanderCVSS 3.1 · 7.5CWE-749

    ICRTouch Commander administrative interface performs security-sensitive operations through HTTP GET requests and includes an API key in the request query string. GET requests are commonly retained in browser history, proxy logs, server logs, analytics systems, referrer headers,…

  8. CVE-2026-122142

    ICRTouch Commander unlimited sign-in attempts

    Critical9.8EPSS not scored yet

    ICRTouch CommanderCVSS 3.1 · 9.8CWE-307

    ICRTouch Commander administrative login interface does not adequately restrict repeated authentication attempts. The interface also returns distinguishable responses for multiple authentication states, including different behavior when a `siteID` value is supplied.

  9. CVE-2026-122141

    ICRTouch TouchTakeaway cross-site request forgery

    High8.1EPSS not scored yet

    ICRTouch TouchTakeaway and 1 moreCVSS 3.1 · 8.1CWE-352

    The wallet top-up functionality in ICRTouch ByTable and TouchTakeaway does not adequately protect state-changing requests against CSRF. An attacker-controlled website can cause an authenticated customer’s browser to submit a wallet top-up request and add an attacker-selected…

  10. CVE-2026-122125

    ICRTouch TouchTakeaway cross-site request forgery

    Medium5.4EPSS not scored yet

    ICRTouch TouchTakeaway and 1 moreCVSS 3.1 · 5.4CWE-352

    ICRTouch ByTable and TouchTakeaway do not consistently implement anti-CSRF protections for state-changing web requests. The affected functionality does not require a per-session CSRF token or otherwise verify that requests originated from an authorized application context. An…

  11. CVE-2026-122122

    ICRTouch TouchTakeaway insecure direct object reference

    Critical9.1EPSS not scored yet

    ICRTouch TouchTakeaway and 1 moreCVSS 3.1 · 9.1CWE-639

    The order-tracking functionality in ICRTouch ByTable and TouchTakeaway does not adequately verify that a requester is authorized to access the specified order. An unauthenticated remote attacker can modify an order identifier to retrieve information associated with other…

  12. CVE-2026-122055

    ICRTouch PocketTouch hard-coded credentials

    Critical9.8EPSS not scored yet

    ICRTouch PocketTouchCVSS 3.1 · 9.8CWE-798

    ICRTouch PocketTouch version 1.700 build 2025.3726 contains a default socket password set to the literal value password. Where the default value remains unchanged and is accepted by a TouchPoint POS terminal, an attacker with network access to the terminal’s socket service may…

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.