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, 12:25 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.
Check Point Multiple Products Incorrect Permission Assignment for Critical Resource Vulnerability
High7.8Exploited, CISA due date 2026-11-16EPSS 2.2%, higher than 83% of scored CVEscheckpoint Quantum Security Gateway and 1 moreCVSS 3.1 · 7.8CWE-732, CWE-862
UnrealIRCd Improper Neutralization of Delimiters Vulnerability
High8.6Exploited, CISA due date 2026-11-16EPSS 0.51%, higher than 44% of scored CVEsUnrealIRCdCVSS 3.1 · 8.6CWE-140
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 CVEsMicrosoft Office and 6 moreCVSS 3.1 · 6.5CWE-356
Google Chromium Use-After-Free Vulnerability
High8.8Exploited, CISA due date 2026-11-24EPSS 0.96%, higher than 62% of scored CVEsGoogle Chromium and 1 moreCVSS 3.1 · 8.8CWE-416
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 CVEsBarracuda Email Security Gateway (ESG) and 5 moreCVSS 4.0 · 9.3CWE-288
Trends
The last 30 days, by severity.
6,559 CVEs published, 519 of them critical. Many arrive without a score yet: NVD and the reporting organisations add CVSS over the following days.
Show the numbers
| Day | Critical | High | Medium | Low | Not scored |
|---|---|---|---|---|---|
| 17 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 18 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 19 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 20 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 21 Oct 2026 | 2 | 0 | 0 | 0 | 0 |
| 22 Oct 2026 | 2 | 0 | 0 | 0 | 0 |
| 23 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 24 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 25 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 26 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 27 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 28 Oct 2026 | 0 | 1 | 0 | 0 | 0 |
| 29 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 30 Oct 2026 | 0 | 0 | 0 | 0 | 0 |
| 31 Oct 2026 | 0 | 1 | 0 | 0 | 0 |
| 1 Nov 2026 | 0 | 0 | 0 | 0 | 0 |
| 2 Nov 2026 | 1 | 1 | 0 | 0 | 0 |
| 3 Nov 2026 | 0 | 0 | 1 | 0 | 0 |
| 4 Nov 2026 | 35 | 158 | 142 | 29 | 0 |
| 5 Nov 2026 | 55 | 213 | 149 | 36 | 0 |
| 6 Nov 2026 | 41 | 148 | 202 | 47 | 6 |
| 7 Nov 2026 | 54 | 165 | 232 | 10 | 13 |
| 8 Nov 2026 | 23 | 128 | 143 | 26 | 0 |
| 9 Nov 2026 | 32 | 164 | 231 | 42 | 1 |
| 10 Nov 2026 | 117 | 1221 | 623 | 61 | 92 |
| 11 Nov 2026 | 51 | 285 | 237 | 44 | 47 |
| 12 Nov 2026 | 28 | 172 | 129 | 23 | 6 |
| 13 Nov 2026 | 67 | 327 | 337 | 52 | 9 |
| 14 Nov 2026 | 7 | 13 | 12 | 6 | 26 |
| 15 Nov 2026 | 4 | 8 | 5 | 4 | 12 |
Exploit likelihood (EPSS), last 30 days
- Under 1%6252
- 1% to 10%225
- 10% to 50%4
- 50% or more3
- Not scored yet75
Most affected vendors, last 30 days
Most common weaknesses, last 30 days
- Cross-site scripting (CWE-79)529
- Missing authorization (CWE-862)387
- Heap-based buffer overflow (CWE-122)364
- Use after free (CWE-416)342
- Insecure direct object reference (CWE-639)232
- Incorrect authorization (CWE-863)215
- Out-of-bounds read (CWE-125)208
- SQL injection (CWE-89)187
- Path traversal (CWE-22)184
- Out-of-bounds write (CWE-787)183
Matching CVEs
2,313 CVEs match these filters, page 93 of 93.
go-vikunja vikunja uncontrolled resource consumption
High8.7EPSS 0.37%, higher than 31% of scored CVEsgo-vikunja vikunjaCVSS 4.0 · 8.7CWE-400
Vikunja from 1.0.0 before 2.7.1 contains an uncontrolled resource consumption vulnerability that allows authenticated users to bypass service.maxitemsperpage by sending page=0 to /api/v1 list endpoints. Attackers can self-register and repeatedly request page=0 to force…
go-vikunja vikunja insufficient session expiration
High7.6EPSS 0.23%, higher than 14% of scored CVEsgo-vikunja vikunjaCVSS 4.0 · 7.6CWE-613
Vikunja before 2.7.1 contains an insufficient session expiration vulnerability that allows holders of revoked access tokens to keep authenticating because SetupTokenMiddleware skips session and account-status checks. Attackers with a stolen token can, after logout, password…
go-vikunja vikunja allocation without limits
High7.1EPSS 0.31%, higher than 24% of scored CVEsgo-vikunja vikunjaCVSS 4.0 · 7.1CWE-770
Vikunja before 2.7.1 allocates memory without limits in its Trello, Todoist and Microsoft To Do migration importers, which buffer remote attachment downloads and API responses in memory without size caps. Authenticated users can start a migration that references huge…
go-vikunja vikunja allocation without limits
High7.1EPSS 0.31%, higher than 24% of scored CVEsgo-vikunja vikunjaCVSS 4.0 · 7.1CWE-770
Vikunja before 2.7.1 contains an uncontrolled resource consumption vulnerability that allows authenticated users to exhaust server memory by requesting avatars at many distinct sizes. Attackers can upload a noisy avatar and fetch it at each size up to 1024, caching roughly a…
go-vikunja vikunja insecure direct object reference
High7.1EPSS 0.31%, higher than 25% of scored CVEsgo-vikunja vikunjaCVSS 4.0 · 7.1CWE-639
Vikunja before 2.7.1 contains an authorization bypass vulnerability that allows authenticated users to read any task by injecting a crafted task object into a no-op Kanban bucket move. Attackers can set task.id to a victim task and task.project_id to their own project, routing…
go-vikunja vikunja improper privilege management
High7.1EPSS 0.30%, higher than 23% of scored CVEsgo-vikunja vikunjaCVSS 4.0 · 7.1CWE-269
Vikunja from 0.18.0 before 2.7.1 contains a privilege escalation vulnerability that allows team owners to gain admin or ownership of read-only shared projects by deleting accounts. Attackers can create a bot, add it to their team, and delete it through the bots endpoint,…
go-vikunja vikunja allocation without limits
High7.1EPSS 0.31%, higher than 24% of scored CVEsgo-vikunja vikunjaCVSS 4.0 · 7.1CWE-770
Vikunja before 2.7.1 contains a denial of service vulnerability that allows authenticated users to exhaust API process memory by uploading WeKan or vikunja-file imports with no item-count cap. Attackers can submit a ~22 MB WeKan JSON with hundreds of thousands of cards or…
go-vikunja vikunja response discrepancy
High7.1EPSS 0.22%, higher than 13% of scored CVEsgo-vikunja vikunjaCVSS 4.0 · 7.1CWE-204
Vikunja before 2.7.1 contains an information disclosure vulnerability that allows authenticated users to determine whether private teams exist by calling the team member self-removal endpoint. Attackers can send DELETE requests to /teams/{id}/members/{own username} for…
go-vikunja vikunja allocation without limits
High7.1EPSS 0.30%, higher than 23% of scored CVEsgo-vikunja vikunjaCVSS 4.0 · 7.1CWE-770
Vikunja before 2.7.1 contains a resource exhaustion vulnerability in the vikunja-file ZIP importer that allows authenticated users to consume CPU and memory by uploading archives with excessive entries. Attackers can upload export ZIPs containing many empty or non-files/…
go-vikunja vikunja sensitive data in a response
High7.6EPSS 0.25%, higher than 17% of scored CVEsgo-vikunja vikunjaCVSS 4.0 · 7.6CWE-201
Vikunja before 2.7.1 contains a credential exposure vulnerability that allows attackers to steal stored auth tokens by inducing users to switch the frontend API URL. Because checkAndSetApiUrl leaves origin-independent localStorage tokens in place, the bearer token and desktop…
go-vikunja vikunja sensitive data in logs
High8.4EPSS 0.27%, higher than 19% of scored CVEsgo-vikunja vikunjaCVSS 4.0 · 8.4CWE-532
Vikunja before 2.7.1 embeds live password-reset, email-confirmation and account-deletion tokens in the URL query string of emailed links, so the full request URI, including the token, is written to Vikunja's HTTP access log and any reverse-proxy logs when a user clicks the…
go-vikunja vikunja uncontrolled resource consumption
High7.1EPSS 0.31%, higher than 24% of scored CVEsgo-vikunja vikunjaCVSS 4.0 · 7.1CWE-400
Vikunja before 2.7.1 contains an uncontrolled resource consumption vulnerability that allows authenticated users to exhaust server memory through concurrent image decodes in avatar and background uploads. Attackers can send several parallel tiny, highly compressible PNGs…
go-vikunja vikunja cleartext transmission
High7.6EPSS 0.16%, higher than 5% of scored CVEsgo-vikunja vikunjaCVSS 4.0 · 7.6CWE-319
Vikunja veans before 2.7.1 contains a protocol downgrade vulnerability in serverCandidates that allows on-path attackers to force plain HTTP during veans init and login. Attackers can block HTTPS ports so discovery accepts an unverified HTTP response, capturing passwords, TOTP…
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.