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 11 Nov, 04:49 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 not scored yet

    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 not scored yet

    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 1.6%, higher than 76% of scored CVEs

    Barracuda Email Security Gateway (ESG)CVSS 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 1.1%, higher than 65% of scored CVEs

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

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

Every exploited CVE

Trends

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

CriticalHighMediumLowNot scored13 Oct 2026 to 11 Nov 2026
Show the numbers
DayCriticalHighMediumLowNot scored
13 Oct 202612000
14 Oct 202622000
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 202635158138321
5 Nov 202655213148361
6 Nov 202640146205476
7 Nov 2026571612321113
8 Nov 202623128143260
9 Nov 2026221492184239
10 Nov 2026103115158743233
11 Nov 20262111510

Exploit likelihood (EPSS), last 30 days

  1. Under 1%713
  2. 1% to 10%25
  3. 10% to 50%2
  4. 50% or more7
  5. Not scored yet3944

Matching CVEs

331 CVEs match these filters, page 8 of 14.

  1. CVE-2026-17327

    IBM API Connect server-side request forgery

    High8.5EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 8.5CWE-918

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to server-side request forgery.

  2. CVE-2026-17326

    IBM API Connect improper authentication

    High8.1EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 8.1CWE-287

    IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to bypass security restrictions due to improper authentication.

  3. CVE-2026-17325

    IBM API Connect server-side request forgery

    High8.5EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 8.5CWE-918

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to improper validation of user-supplied URLs.

  4. CVE-2026-17324

    IBM API Connect missing authentication

    High8.3EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 8.3CWE-306

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to access sensitive configuration data and perform unauthorized actions due to missing authentication for a critical function.

  5. CVE-2026-17323

    IBM API Connect XML external entity

    High8.2EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 8.2CWE-611

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information due to XML external entity (XXE) injection.

  6. CVE-2026-17322

    IBM API Connect sensitive data in logs

    High7.1EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 7.1CWE-532

    IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a local attacker to obtain sensitive credentials and compromise accounts due to insertion of sensitive information into log files.

  7. CVE-2026-17321

    IBM API Connect insecure direct object reference

    High8.1EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 8.1CWE-639

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to delete or overwrite arbitrary control-plane assets due to an insecure direct object reference.

  8. CVE-2026-17320

    IBM API Connect insecure direct object reference

    High7.7EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 7.7CWE-639

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to an insecure direct object reference.

  9. CVE-2026-17319

    IBM API Connect missing authorization

    High7.1EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 7.1CWE-862

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to modify tool configuration and cause a denial of service due to improper authorization. Information supplied by the client is relied on when deciding what a user is allowed to do, which…

  10. CVE-2026-17318

    IBM API Connect insecure direct object reference

    High7.7EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 7.7CWE-639

    IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to improper authorization.

  11. CVE-2026-17317

    IBM API Connect server-side request forgery

    Medium6.4EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 6.4CWE-918

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to access internal resources and cause a denial of service due to server-side request forgery.

  12. CVE-2026-17316

    IBM API Connect server-side request forgery

    High7.2EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 7.2CWE-918

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to perform server-side request forgery due to improper validation of user-supplied input.

  13. CVE-2026-17315

    IBM API Connect server-side request forgery

    Medium5.8EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 5.8CWE-918

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information due to improper validation of user-supplied URLs.

  14. CVE-2026-17314

    IBM API Connect server-side request forgery

    Medium5.0EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 5.0CWE-918

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to server-side request forgery.

  15. CVE-2026-17313

    IBM API Connect authentication bypass by alternate path

    Critical9.8EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 9.8CWE-288

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information and take control of gateway configuration due to authentication bypass via an alternate path.

  16. CVE-2026-17312

    IBM API Connect cross-site request forgery

    Medium5.4EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 5.4CWE-352

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to force a user to authenticate into an attacker-controlled account due to cross-site request forgery. The sign-in flow does not sufficiently verify that a login response belongs to the user's own request,…

  17. CVE-2026-17311

    IBM API Connect insecure direct object reference

    High7.1EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 7.1CWE-639

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to modify application API subscriptions due to broken object-level authorization.

  18. CVE-2026-17310

    IBM API Connect hard-coded cryptographic key

    Medium6.5EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 6.5CWE-321

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information due to the use of a hard-coded cryptographic key.

  19. CVE-2026-17309

    IBM API Connect improper certificate validation

    High8.0EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 8.0CWE-295

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information and tamper with configuration due to improper certificate validation.

  20. CVE-2026-17308

    IBM API Connect improper certificate validation

    Medium6.8EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 6.8CWE-295

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive credentials and manipulate tool responses due to improper certificate validation.

  21. CVE-2026-17307

    IBM API Connect insecure direct object reference

    Medium6.5EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 6.5CWE-639

    IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to broken object-level authorization.

  22. CVE-2026-17306

    IBM API Connect server-side request forgery

    High8.6EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 8.6CWE-918

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information from internal network resources due to server-side request forgery.

  23. CVE-2026-17305

    IBM API Connect server-side request forgery

    Medium5.5EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 5.5CWE-918

    IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to server-side request forgery.

  24. CVE-2026-17304

    IBM API Connect server-side request forgery

    Medium6.5EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 6.5CWE-918

    IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to improper input validation. Locations supplied when service definitions are imported are not sufficiently validated, which could allow the server to…

  25. CVE-2026-17303

    IBM API Connect server-side request forgery

    Medium6.4EPSS not scored yet

    IBM API ConnectCVSS 3.1 · 6.4CWE-918

    IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to access internal network resources due to improper validation of a user-supplied URL. The address is not sufficiently restricted, which could allow the server…

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.