Export limit exceeded: 17153 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (17153 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-132985 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 4.9 Medium |
| In JetBrains TeamCity before 2026.2 project administrators could read OAuth connection secrets of ancestor projects | ||||
| CVE-2026-132996 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 2.7 Low |
| In JetBrains TeamCity before 2026.2 mute and unmute operations via XML-RPC could be attributed to other users | ||||
| CVE-2026-133048 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 5.4 Medium |
| In JetBrains TeamCity before 2026.2.1 improper authorization allowed using AWS connections of other projects in cloud profiles | ||||
| CVE-2026-133096 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 7.1 High |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 improper authorization allowed queuing builds with personal changes of other users | ||||
| CVE-2026-61799 | 1 Netty | 1 Netty-incubator-codec-ohttp | 2026-11-21 | 5.3 Medium |
| netty-incubator-codec-ohttp implements Oblivious HTTP (OHTTP) gateway and client functionality using Netty. Prior to 0.0.23.Final, BinaryHttpParser in codec-bhttp/src/main/java/io/netty/incubator/codec/bhttp/BinaryHttpParser.java accumulates attacker-controlled Binary HTTP variable-length integers into the int offset sumBytes. BinaryHttpParser.readRequestHead, BinaryHttpParser.readFieldLine, and BinaryHttpParser.getIndeterminateLength can narrow long lengths into that offset, causing integer wraparound before buffer indices are calculated. A remote peer that supplies a valid large encoded length to BinaryHttpParser or BinaryHttpDecoder can trigger an unchecked bounds exception from a small malformed message, fail or close the channel, and repeatedly cause denial of service. Java and Netty bounds checks prevent memory corruption, and no information disclosure was observed. This issue is fixed in version 0.0.23.Final. | ||||
| CVE-2026-133085 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 7.6 High |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 an XXE was possible in the TFS helper process | ||||
| CVE-2026-133090 | 1 Jetbrains | 1 Teamcity | 2026-11-21 | 7.2 High |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 improper authorization allowed overwriting versioned settings of other projects | ||||
| CVE-2026-133252 | 1 Jetbrains | 1 Datalore | 2026-11-21 | 3.1 Low |
| In JetBrains Datalore before 2026.4.1 open redirect after OpenID login was possible via the origin parameter | ||||
| CVE-2026-14879 | 1 Ibm | 1 Watsonxdata | 2026-11-21 | 6.5 Medium |
| IBM watsonx.data 2.4.0 through 2.4.0 patch 8 does not invalidate session after a logout which could allow an authenticated user to impersonate another user on the system. | ||||
| CVE-2026-59968 | 1 Kovah | 1 Linkace | 2026-11-21 | N/A |
| LinkAce is a self-hosted archive to collect website links. Prior to 2.5.9, the authenticated GET /api/v2/lists/{list}/links endpoint in app/Http/Controllers/API/ListLinksController.php authorizes access only to the parent list and then returns its links without applying visibleForUser(). Because another user's INTERNAL or PUBLIC list may legitimately contain PRIVATE links, a normal authenticated user who may view the list can also receive those private link records, including their URLs, titles, descriptions, icons, and timestamps. Equivalent web, tag, notes, and feed handlers apply the per-link visibility scope, so this API handler is the affected exception. This issue is fixed in version 2.5.9. | ||||
| CVE-2026-133324 | 1 Mitel | 1 Micollab | 2026-11-21 | 5.3 Medium |
| A vulnerability in the Audio, Web, and Video Conferencing (AWV) component of Mitel MiCollab through 10.3 (10.3.0.18) could allow an unauthenticated attacker to conduct an authentication bypass attack due to improper handling of authentication. A successful exploit could allow an attacker to bypass authentication and perform unauthorized actions within the context of the application. This is MTLVULN-1877. | ||||
| CVE-2026-133521 | 2 Barassistant, Karlomikus | 2 Bar Assistant, Bar-assistant | 2026-11-21 | 5.4 Medium |
| Bar Assistant 3.0.0 before 6.11.0 contains an authorization bypass vulnerability in BarController::join that allows authenticated users to join bars without a valid invite code. Attackers can send POST requests to /api/bars/join omitting invite_code, matching invite-disabled bars with NULL codes, to read cocktails, ingredients, members, settings and search tokens. | ||||
| CVE-2026-133662 | 1 Flowintel | 1 Flowintel | 2026-11-21 | N/A |
| flowintel contains multiple authorization bypass vulnerabilities in its Analyzer (MISP Modules) functionality, affecting both the web interface and the REST API. - Saving analyzer results to a case or task accepted caller-supplied case and task identifiers without verifying that the authenticated user is a member of the target case or holds the required restricted-task permissions. An authenticated user could write notes, create tasks, and attach MISP objects or attributes into another organization's case. - Stored analyzer results were retrievable by UUID by any authenticated user. Both the web endpoint and the API endpoint returned the full result payload without checking ownership, exposing another user's analysis output. - The save handler did not validate the structure of the request, did not reject conflicting destination selections, and did not halt processing when a task-note operation failed, allowing partial or unintended writes. Preconditions: the attacker must possess a valid authenticated session (or API token) in flowintel. No administrative role is required. Security impact: unauthorized cross-tenant data disclosure (analyzer results) and unauthorized cross-tenant data modification (notes, tasks, MISP objects/attributes in another organization's case). Affected versions: flowintel prior to 4.1.0. | ||||
| CVE-2026-133844 | 1 Flowintel | 1 Flowintel | 2026-11-21 | N/A |
| FlowIntel, a threat intelligence case management platform, contains an information disclosure vulnerability in its case serialization logic. When a case is rendered via the REST API or browser views, all connector instances associated with that case were included in the response regardless of the requesting user's permissions. This means that any authenticated user with read access to a case could observe connector metadata belonging to other users (personal-scope connectors) or other organizations (org-scope connectors), including connector URLs, descriptions, UUIDs, and potentially embedded API credentials. Preconditions: - An authenticated user account with at least read access to the affected case - The case must have connector instances attached that belong to other users or organizations Impact: - Disclosure of personal connector endpoints and credentials of other users - Disclosure of organization-scoped connector metadata across organizational boundaries - Enumeration of connector infrastructure (URLs, UUIDs, descriptions) not intended for the viewer Affected versions: < 4.1.0 | ||||
| CVE-2026-133561 | 1 Mattermost | 1 Mattermost | 2026-11-21 | 4.3 Medium |
| Mattermost versions 11.2.x <= 11.2.4 fail to validate that the redirect target on the web app landing page that prompts users to open links in the desktop app stays on the Mattermost origin which allows an unauthenticated attacker to redirect a user to an arbitrary external site via a crafted link. Mattermost Advisory ID: MMSA-2026-00893 | ||||
| CVE-2026-133652 | 1 Flowintel | 1 Flowintel | 2026-11-21 | N/A |
| Flowintel , contained a session management vulnerability in its browser authentication mechanism. The session identifier used a bare numeric user ID rather than a credential-bound token, resulting in several related weaknesses: - Remembered logins (remember-me cookies) remained valid after a user changed their password, allowing an attacker holding a previously issued cookie to retain access indefinitely. - Server-side session identifiers were not rotated upon login (local, SSO, or remembered), enabling session fixation. - Self-service email and password changes did not require verification of the current password, permitting an attacker with an active session to modify account credentials without knowledge of the existing password. - Administrator-initiated password resets did not revoke other browser sessions, invalidate remembered logins, or rotate the affected user's API key. An attacker who obtained a valid session or remember-me cookie (e.g., through XSS, network interception, or cookie theft) could maintain unauthorized access even after the legitimate user changed their password. Additionally, an attacker with any valid session could change the account's email address or password without knowing the current credentials, effectively taking over the account. Affected versions: Flowintel prior to 4.1.0. | ||||
| CVE-2026-133659 | 1 Flowintel | 1 Flowintel | 2026-11-21 | N/A |
| Flowintel contains multiple SSO identity and organisation trust boundary violations that collectively allow account takeover, privilege escalation, and unauthorized access to private case data. - Keycloak SSO accepted unverified email claims, and all SSO providers (Keycloak, Entra ID, SimpleSAML) could resolve a claimed email address to an existing account that was created via a different sign-in method, enabling cross-provider account collision and unauthorized access to another user's account and data. - Entra ID role mapping relied on group display names, which tenant members could duplicate by creating a group with the same name as a privileged group (e.g. FlowintelAdmin), resulting in unauthorized role escalation. - SSO provisioning reused organisations whose display names matched user-controlled profile names, granting the new SSO user access to that organisation's private cases without explicit administrator assignment. - Case sharing via the API resolved organisations by name using a first-match query, so ambiguous names could silently resolve to the wrong organisation. Preconditions: an attacker must have a valid SSO identity (Keycloak, Entra ID, or SimpleSAML) or be a member of the relevant Entra tenant. No local administrator access is required. Security impact: unauthorized access to private case data, privilege escalation to Editor or higher roles, and account takeover across authentication providers. Affected versions: Flowintel prior to 4.1.0. | ||||
| CVE-2026-133663 | 1 Flowintel | 1 Flowintel | 2026-11-21 | N/A |
| flowintel contains an Insecure Direct Object Reference (IDOR) vulnerability affecting multiple endpoints that manage child records of cases and tasks. An authenticated user with access to one case or task could read or modify records belonging to other cases by supplying identifiers of those records directly in the request. Affected operations include: - Reading task notes, subtasks, and URL tools by referencing their IDs without verifying they belong to the authorized task - Retrieving task assignees for a task belonging to a different case - Editing or deleting timeline events and timeline event links belonging to another case - Editing or removing case connectors belonging to another case - Invoking connector module operations (MISP, generic connectors, worker calls) by combining an authorized case with a connector link from a different case The root cause is that the application authorized the parent resource (case or task) in the URL but then fetched or operated on the child record independently without verifying the child's ownership relationship to the authorized parent. Security impact: an authenticated user can exfiltrate sensitive threat intelligence data from cases they do not have access to, and can modify or delete timeline entries, connector configurations, and other records in unauthorized cases, leading to data integrity loss and potential disruption of incident response workflows. Affected versions: flowintel prior to 4.1.0 | ||||
| CVE-2026-133843 | 1 Flowintel | 1 Flowintel | 2026-11-21 | N/A |
| flowintel contains a vulnerability in the MISP correlation feature that allows unauthorized disclosure of case identifiers. The application failed to enforce proper access controls when generating correlation lists for MISP attributes. Specifically, the system did not verify whether the requesting user had permission to view the source case or the matching cases returned in the correlation results. This lack of authorization checks allowed authenticated users to potentially discover the existence of cases they do not have access to, leading to information disclosure. The vulnerability affects the following components: - Case correlation logic - API endpoints for retrieving correlation attributes - MISP object handling Affected versions: < 4.1.0 | ||||
| CVE-2026-133849 | 1 Flowintel | 1 Flowintel | 2026-11-21 | N/A |
| A vulnerability exists in the flowintel application's calendar functionality that allows unauthorized access to private case data. The task calendar queries failed to enforce visibility checks on the parent case associated with tasks. Specifically, tasks assigned to a user or belonging to the user's organization were returned in calendar views (including browser and API ICS feeds) without verifying whether the user had permission to view the parent case. This allowed users to potentially discover and access details of private cases they were not authorized to view, leading to information disclosure. The issue affected the default task visibility logic and the assigned-only task queries. The fix ensures that case visibility is rechecked in addition to task assignment or organization membership, preventing the exposure of private case data in calendar outputs. Affected versions: flowintel < 4.1.0 | ||||