Export limit exceeded: 428950 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 428950 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (428950 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-132931 | 1 Jetbrains | 1 Teamcity | 2026-11-19 | 6.1 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the build feature parameters page was possible | ||||
| CVE-2026-132956 | 1 Jetbrains | 1 Teamcity | 2026-11-19 | 5.4 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Build Features page was possible | ||||
| CVE-2026-132972 | 1 Jetbrains | 1 Teamcity | 2026-11-19 | 4.8 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Slack Notifier settings page was possible | ||||
| CVE-2026-133056 | 1 Jetbrains | 1 Teamcity | 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-133077 | 1 Jetbrains | 1 Teamcity | 2026-11-19 | 7.2 High |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 privilege escalation to system administrator was possible via Project Import | ||||
| CVE-2026-133078 | 1 Jetbrains | 1 Teamcity | 2026-11-19 | 7.2 High |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via security context spoofing in the Kotlin DSL sandbox | ||||
| CVE-2026-133091 | 1 Jetbrains | 1 Teamcity | 2026-11-19 | 8 High |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS on the Users page was possible | ||||
| CVE-2026-133093 | 1 Jetbrains | 1 Teamcity | 2026-11-19 | 7.2 High |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 code injection in parent project Kotlin DSL was possible via subproject settings | ||||
| CVE-2026-133099 | 1 Jetbrains | 1 Teamcity | 2026-11-19 | 6.5 Medium |
| In JetBrains TeamCity before 2026.2.2 vCS root passwords could be extracted via the REST API property locator | ||||
| CVE-2026-133100 | 1 Jetbrains | 1 Teamcity | 2026-11-19 | 6.8 Medium |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 command injection in Project Import artifact copy scripts was possible | ||||
| CVE-2026-133101 | 1 Jetbrains | 1 Teamcity | 2026-11-19 | 6.5 Medium |
| In JetBrains TeamCity before 2026.2.2 a CSRF attack was possible on the diagnostic page | ||||
| CVE-2026-133103 | 1 Jetbrains | 1 Teamcity | 2026-11-19 | 6.8 Medium |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS in the enforced settings restriction tooltip was possible | ||||
| CVE-2026-133104 | 1 Jetbrains | 1 Teamcity | 2026-11-19 | 6.4 Medium |
| In JetBrains TeamCity before 2026.2.2 stored XSS in external change viewer links was possible | ||||
| CVE-2026-133106 | 1 Jetbrains | 1 Teamcity | 2026-11-19 | 6.8 Medium |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 stored XSS on the Projects Import page was possible | ||||
| CVE-2026-133107 | 1 Jetbrains | 1 Teamcity | 2026-11-19 | 2.4 Low |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 hTML injection in pipeline notification emails was possible via commit messages | ||||
| CVE-2026-133178 | 1 Flowintel | 1 Flowintel | 2026-11-19 | N/A |
| flowintel allows users with editor-level access to author case and task fields, including aggregated tags. When these records are exported as CSV, the field values are written verbatim into the output file. Because no sanitisation is applied to user-supplied text before CSV serialisation, an attacker can store values that begin with spreadsheet formula triggers (such as =, +, -, @, or their fullwidth Unicode equivalents, or leading control/whitespace characters). When a victim opens the exported CSV in a spreadsheet application (e.g. Microsoft Excel, LibreOffice Calc), the stored text is interpreted and executed as a live formula rather than displayed as literal text. This can lead to unintended data manipulation within the spreadsheet, potential data exfiltration via formula functions, or execution of downstream commands depending on the spreadsheet application and its configuration. The vulnerability requires the victim to actively open the CSV file in a spreadsheet application; the flowintel application itself is not directly compromised. Affected: <4.1.0 | ||||
| CVE-2026-133177 | 1 Misp | 1 Misp | 2026-11-19 | N/A |
| MISP contains an authorization flaw in the sharing group capture logic. When a sharing group is re-captured with a newer modified timestamp and an updated roster, the application unconditionally overwrote the type, nationality, sector, and contacts fields of every organisation listed in the roster, including the host organisation. This behaviour was reachable by any user holding the perm_sync role, and additionally by any external server pulled from or any feed fetched, because those operations execute with the privileges of the site administrator who initiated them. As a result, a low-privileged sync user or a malicious/compromised external feed or pull source could silently corrupt organisation records on the receiving MISP instance without any site-admin or internal-sync authorization. The vulnerability does not disclose data or affect availability; the impact is limited to integrity of organisation metadata (type, nationality, sector, contacts). The fix restricts organisation detail updates to internal sync operations (pulls over links flagged as internal, or senders holding perm_sync_internal) and site administrators; all other sync, pull, and feed operations may only match existing organisations by UUID or create new ones, without modifying their stored details. | ||||
| CVE-2026-133175 | 1 Misp | 1 Misp | 2026-11-19 | N/A |
| MISP contains an authorization bypass in its server-to-server proposal synchronization mechanism. Two related flaws were identified: 1. The events/pushProposals endpoint located the target event by UUID without enforcing any access-control check. A sync user with perm_sync could push shadow-attribute proposals to any event on the local instance, including events with restricted distribution (e.g., distribution level 0, visible only to the owning organisation). The stored proposal also carried the sender-supplied event_uuid and event_org_id rather than the local event's actual identity, corrupting the data model. 2. When accepting an edit proposal (old_id != 0), the code resolved the target live attribute by UUID alone (Attribute.uuid = shadow.uuid) without scoping the lookup to the proposal's own event. A malicious sync user could therefore craft a proposal whose uuid matched an attribute in a different event; upon acceptance, the wrong attribute would be modified or deleted. The same unscoped lookup existed in the ShadowAttribute::acceptProposal path. Preconditions: an authenticated user with sync permission (perm_sync) on a MISP instance that participates in server-to-server synchronisation. The attacker must know or enumerate the UUID of a target event or attribute. Security impact: unauthorised read access to restricted events, unauthorised insertion of proposals onto events the user cannot see, and unauthorised modification or deletion of attributes belonging to other events. This compromises the confidentiality and integrity of threat-intelligence data across organisational boundaries within a MISP deployment. | ||||
| CVE-2026-126086 | 2026-11-19 | N/A | ||
| In Eclipse Dataspace Components (EDC) – Connector (`org.eclipse.edc:decentralized-claims-*`, `org.eclipse.edc:jwt-verifiable-credentials`, `org.eclipse.edc:ldp-verifiable-credentials`) there's a credential verification bypass in Decentralized Claims Protocol (DCP) presentation handling: a participant can present credentials appearing to be issued by any trusted issuer without holding them. | ||||
| CVE-2026-123894 | 2026-11-19 | 6.7 Medium | ||
| VMware Tools for Windows contains a SAML token signature bypass vulnerability. Affected versions: 13.x.x.x (fixed in 13.1.5.0); 12.3.x (fixed in 12.5.5). | ||||