Export limit exceeded: 428552 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 428552 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (428552 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-132133 | 2026-11-19 | 4.8 Medium | ||
| @fastify/middie is the middleware engine that adds Express and Connect style middleware support to Fastify. In versions up to and including 9.3.6, middie builds the match regular expression for each path-scoped middleware from its mount path without collapsing duplicate slashes, even when the application enables the ignoreDuplicateSlashes router option. Under that option Fastify's router collapses duplicate slashes in both the registered route and the request path, so a mount path containing a doubled slash is served by the router at its single-slash form while the middleware's compiled match still requires the doubled slash and never matches. A path-scoped middleware such as authentication, authorization, or rate limiting is therefore skipped while the router dispatches the request to the protected handler, without any authentication required. Applications are affected when they enable ignoreDuplicateSlashes and a middleware mount path reaches middie with a duplicate slash, most commonly when a plugin prefix that ends with a slash is joined to a mount path that starts with one. The issue is fixed in @fastify/middie 9.3.7, and users should upgrade to 9.3.7 or later. As a workaround, enforce authorization in a Fastify hook such as preHandler that runs after routing, and avoid mount paths and plugin prefixes that introduce duplicate slashes. | ||||
| CVE-2026-125060 | 2026-11-19 | 8.2 High | ||
| The checkout of JTL-Shop stores the delivery address ID submitted by the customer in the session and adopts it into the order without verifying that the address belongs to the ordering customer. A remote attacker with access to the checkout, including a guest, can thereby attach the delivery address of another customer to their own order. Name and address of the other customer, and depending on the shop configuration further contact data, then appear in the order confirmation and customer account. As the IDs are sequential, addresses can be enumerated. Goods may also be shipped to the wrong address. | ||||
| CVE-2026-133057 | 2026-11-19 | 3.7 Low | ||
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 the TFS helper server was exposed on all network interfaces | ||||
| CVE-2026-133056 | 2026-11-19 | 3.5 Low | ||
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in implicit agent requirements was possible | ||||
| CVE-2026-133055 | 2026-11-19 | 3.5 Low | ||
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS on the Failure Conditions page was possible | ||||
| CVE-2026-133054 | 2026-11-19 | 6.8 Medium | ||
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Create Project dialog was possible | ||||
| CVE-2026-133053 | 2026-11-19 | 5.3 Medium | ||
| In JetBrains TeamCity before 2026.2.1 arbitrary file read was possible via symlinks in Mercurial subrepositories | ||||
| CVE-2026-133052 | 2026-11-19 | 6.8 Medium | ||
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 a DOM-based XSS in the plugin installation dialog was possible | ||||
| CVE-2026-133051 | 2026-11-19 | 6.8 Medium | ||
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the JaCoCo coverage settings was possible | ||||
| CVE-2026-133050 | 2026-11-19 | 6.8 Medium | ||
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored and reflected XSS in Space project connection dialogs was possible | ||||
| CVE-2026-133049 | 2026-11-19 | 6.8 Medium | ||
| In JetBrains TeamCity before 2026.2.1 stored XSS in the Pull Requests health report for VCS roots was possible | ||||
| CVE-2026-133048 | 2026-11-19 | 5.4 Medium | ||
| In JetBrains TeamCity before 2026.2.1 improper authorization allowed using AWS connections of other projects in cloud profiles | ||||
| CVE-2026-133047 | 2026-11-19 | 6.8 Medium | ||
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS on the thread dump page was possible | ||||
| CVE-2026-133046 | 2026-11-19 | 6.8 Medium | ||
| In JetBrains TeamCity before 2026.2.1 stored XSS in recipe export errors was possible | ||||
| CVE-2026-133045 | 2026-11-19 | 6.8 Medium | ||
| In JetBrains TeamCity before 2026.2.1 stored XSS in VMware vSphere cloud profile settings was possible | ||||
| CVE-2026-133043 | 2026-11-19 | 6.5 Medium | ||
| In JetBrains TeamCity before 2026.2.1 missing authorization allowed reading VCS file contents and patches of other projects | ||||
| CVE-2026-133042 | 2026-11-19 | 6.8 Medium | ||
| In JetBrains TeamCity before 2026.2.1 stored XSS in the Amazon EC2 cloud profile editor was possible | ||||
| CVE-2026-133041 | 2026-11-19 | 6.8 Medium | ||
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Commit Status Publisher settings was possible | ||||
| CVE-2026-133039 | 2026-11-19 | 6.8 Medium | ||
| In JetBrains TeamCity before 2026.2.1 stored XSS in the Pull Requests health report for Space connections was possible | ||||
| CVE-2026-133038 | 2026-11-19 | 6.8 Medium | ||
| In JetBrains TeamCity before 2026.2.1 stored XSS in the Maven Build Info project header was possible | ||||