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 11 Nov, 15:27 UTC from NVD, CISA KEV and FIRST EPSSMarkdownRSSJSON Feed

339Critical, last 7 days2,110High, last 7 days40Added to CISA KEV, 30 days1,779Exploited 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-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

The last 30 days, by severity.

4,959 CVEs published, 363 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 2026103115159043230
11 Nov 202619801501632

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 yet4212

Most affected vendors, last 30 days

  1. Microsoft1096
  2. IBM322
  3. Apache Software Foundation187
  4. Google168
  5. FFmpeg121
  6. Adobe112
  7. Mozilla108
  8. Red Hat90
  9. JetBrains89
  10. openemr60

Matching CVEs

2,186 CVEs match these filters, page 81 of 88.

  1. CVE-2026-68985

    Samsung Semiconductor Exynos 1280 out-of-bounds write

    High7.5EPSS 0.14%, higher than 3% of scored CVEs

    Samsung Semiconductor Exynos 1280 and 2 moreCVSS 3.1 · 7.5CWE-787

    In the Samsung Exynos NPU driver, improper validation of user input in the ioctl handler can lead to an out-of-bounds write, which causes a denial of service.

  2. CVE-2026-68984

    Samsung Semiconductor Exynos 2100 integer overflow

    High8.1EPSS 0.14%, higher than 3% of scored CVEs

    Samsung Semiconductor Exynos 2100 and 9 moreCVSS 3.1 · 8.1CWE-190

    In the Samsung Exynos NPU kernel driver, an integer overflow allows an unprivileged application to trigger memory corruption.

  3. CVE-2026-48179

    Samsung Semiconductor Exynos 1080 vulnerability

    High7.5EPSS 0.14%, higher than 3% of scored CVEs

    Samsung Semiconductor Exynos 1080 and 4 moreCVSS 3.1 · 7.5CWE-1286

    In the Exynos modem's IMS stack, improper handling of SDP payload leads to a Denial of Service

  4. CVE-2026-48178

    Samsung Semiconductor Exynos 2200 vulnerability

    High8.8EPSS 0.11%, higher than 1% of scored CVEs

    Samsung Semiconductor Exynos 2200 and 3 moreCVSS 3.1 · 8.8CWE-413

    Out of bound access in PPC due to race condition in global variable access

  5. CVE-2026-48176

    Samsung Semiconductor Exynos 1080 unchecked quantity

    High7.5EPSS 0.14%, higher than 3% of scored CVEs

    Samsung Semiconductor Exynos 1080 and 4 moreCVSS 3.1 · 7.5CWE-1284

    A memory corruption vulnerability caused by improper validation of messages

  6. CVE-2026-35494

    Samsung Semiconductor Exynos 1280 out-of-bounds write

    High7.5EPSS 0.14%, higher than 3% of scored CVEs

    Samsung Semiconductor Exynos 1280 and 8 moreCVSS 3.1 · 7.5CWE-787

    In the baseband, memory corruption during NAS packet processing can cause a denial of service.

  7. CVE-2026-33969

    Samsung Semiconductor Exynos 850 infinite loop

    High7.5EPSS 0.18%, higher than 7% of scored CVEs

    Samsung Semiconductor Exynos 850 and 9 moreCVSS 3.1 · 7.5CWE-835

    In the NAS Authentication Request message decoding procedure, a missing lower bound check causes an infinite loop, leading to Denial of Service.

  8. CVE-2026-33958

    Samsung Semiconductor Exynos 1080 vulnerability

    High7.5EPSS 0.15%, higher than 4% of scored CVEs

    Samsung Semiconductor Exynos 1080 and 9 moreCVSS 3.1 · 7.5CWE-1286

    Processing a malformed RRC Reconfiguration message leads to an out-of-bounds (OOB) access, resulting in a denial-of-service (DoS) condition.

  9. CVE-2026-122323

    kyverno decompression bomb

    High8.7EPSS 0.34%, higher than 27% of scored CVEs

    kyvernoCVSS 4.0 · 8.7CWE-409

    Kyverno from 1.11.0 before 1.19.2 contains an unbounded decompression vulnerability in FetchSignatureBlob that allows attackers to exhaust memory by supplying highly compressed notary signature layers. Attackers who control registry referrers or signatures can publish small…

  10. CVE-2026-122322

    kyverno decompression bomb

    High8.7EPSS 0.40%, higher than 34% of scored CVEs

    kyvernoCVSS 4.0 · 8.7CWE-409

    Kyverno from 1.11.0 before 1.19.2 contains an unbounded decompression vulnerability in extractStatement that allows remote attackers to exhaust memory by supplying highly compressed attestation layers. Attackers controlling registry referrer artifacts can push gzip predicate…

  11. CVE-2026-122321

    kyverno time-of-check to time-of-use race

    High8.5EPSS 0.23%, higher than 14% of scored CVEs

    kyvernoCVSS 4.0 · 8.5CWE-367

    Kyverno 1.18.0 before 1.19.2 contains a signature verification bypass in verifyImages because cached verification results are keyed by the image reference string (such as a tag) rather than bound to the verified digest, so cache hits skip signature and attestation checks. An…

  12. CVE-2026-122320

    kyverno missing authorization

    High8.3EPSS 0.21%, higher than 12% of scored CVEs

    kyvernoCVSS 4.0 · 8.3CWE-862

    Kyverno before 1.19.2 contains a missing authorization vulnerability that allows namespaced Policy authors to read resources in other namespaces by templating generate.clone or cloneList namespace values. Attackers can annotate a triggering ConfigMap so the…

  13. CVE-2026-122319

    kyverno vulnerability

    High8.7EPSS 0.28%, higher than 20% of scored CVEs

    kyvernoCVSS 4.0 · 8.7CWE-704

    Kyverno before 1.19.2 contains a denial-of-service vulnerability in the In and NotIn operators that allows attackers to crash the policy engine via an unchecked type assertion. Attackers can submit resources whose JMESPath-evaluated values yield arrays of integers, booleans, or…

  14. CVE-2026-122318

    kyverno improper certificate validation

    High7.2EPSS 0.18%, higher than 7% of scored CVEs

    kyvernoCVSS 4.0 · 7.2CWE-295

    Kyverno before 1.19.2 contains an authentication bypass in matchCertificateData that skips verifyImages subject and subjectRegExp checks when the signing certificate has no Subject Alternative Name. Attackers holding a leaf certificate from a configured private trust root can…

  15. CVE-2026-122316

    kyverno missing authorization

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

    kyvernoCVSS 4.0 · 8.4CWE-862

    Kyverno from 1.17.0 before 1.19.2 contains a missing authorization vulnerability in the mutate-existing background processor that allows namespaced tenants to modify resources outside their namespace. Attackers can create a NamespacedMutatingPolicy targeting Namespace objects…

  16. CVE-2026-122315

    kyverno uncaught exception

    High8.7EPSS 0.40%, higher than 35% of scored CVEs

    kyvernoCVSS 4.0 · 8.7CWE-248

    Kyverno before 1.19.2 contains an unchecked type assertion in buildStatementMap that allows unauthenticated attackers to crash the policy engine via crafted attestation statements. Attackers can push an OCI referrer manifest with a non-string type field to bypass image…

  17. CVE-2026-122314

    kyverno uncaught exception

    High8.7EPSS 0.30%, higher than 23% of scored CVEs

    kyvernoCVSS 4.0 · 8.7CWE-248

    Kyverno before 1.19.2 contains an unchecked type assertion in its variable-substitution engine that allows users who can submit resources to crash the policy engine. Attackers can submit resources with non-string fields referenced by {{- variable }} shallow substitution in…

  18. CVE-2026-122312

    kyverno improper privilege management

    High8.3EPSS 0.31%, higher than 24% of scored CVEs

    kyvernoCVSS 4.0 · 8.3CWE-269

    Kyverno from 1.19.1 before 1.19.2 contains a namespace isolation bypass in APICall Fetch() in pkg/engine/apicall/apiCall.go because path.Clean treats '?' as a path character, letting the namespace regex match segments inside the query string. Users who can create namespaced…

  19. CVE-2026-122309

    kyverno uncontrolled resource consumption

    High8.2EPSS 0.20%, higher than 10% of scored CVEs

    kyvernoCVSS 4.0 · 8.2CWE-400

    Kyverno before 1.19.2 contains a denial of service vulnerability that allows namespace-scoped policy authors to exhaust CPU and memory by submitting CEL expressions evaluated without runtime cost limits. Attackers can create a NamespacedValidatingPolicy or…

  20. CVE-2026-122308

    kyverno insecure direct object reference

    High8.4EPSS 0.23%, higher than 14% of scored CVEs

    kyvernoCVSS 4.0 · 8.4CWE-639

    Kyverno before 1.19.2 contains an authorization bypass vulnerability in the Generation Handler that allows users with create/update permissions to trigger synchronized generate policies by spoofing internal generate.kyverno.io labels. Attackers can label a ConfigMap as…

  21. CVE-2026-122307

    kyverno incorrect authorization

    High8.3EPSS 0.24%, higher than 16% of scored CVEs

    kyvernoCVSS 4.0 · 8.3CWE-863

    Kyverno before 1.19.2 contains a policy bypass vulnerability in the admissionpolicygenerator controller, which folds PolicyExceptions into generated ValidatingAdmissionPolicies while ignoring the --enablePolicyException, --exceptionNamespace, and policy kind gates. Users with…

  22. CVE-2026-122306

    kyverno inefficient algorithmic complexity

    High8.3EPSS 0.30%, higher than 23% of scored CVEs

    kyvernoCVSS 4.0 · 8.3CWE-407

    Kyverno before 1.19.2 contains a denial of service vulnerability that allows namespaced policy authors to exhaust admission controller CPU by submitting pathological wildcard patterns. Attackers can create a Policy with crafted match and exclude names evaluated by…

  23. CVE-2026-122305

    kyverno infinite loop

    High8.3EPSS 0.30%, higher than 23% of scored CVEs

    kyvernoCVSS 4.0 · 8.3CWE-835

    Kyverno before 1.19.2 contains a denial of service vulnerability in substituteVariablesIfAny that allows low-privileged users to hang the admission webhook via self-referential variable templates. Attackers can create resources whose annotations re-introduce the embedded policy…

  24. CVE-2025-66368

    Samsung Semiconductor Exynos 1080 unchecked unusual condition

    High7.5EPSS 0.15%, higher than 4% of scored CVEs

    Samsung Semiconductor Exynos 1080 and 2 moreCVSS 3.1 · 7.5CWE-754

    Incorrect handling of SDP payload leads to a Denial of Service

  25. CVE-2025-66367

    Samsung Semiconductor Exynos 850 out-of-bounds read

    High7.5EPSS 0.15%, higher than 4% of scored CVEs

    Samsung Semiconductor Exynos 850 and 9 moreCVSS 3.1 · 7.5CWE-125

    Improper handling of NAS DLTransport messages may lead to a baseband crash.

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.