Export limit exceeded: 430594 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.

Search

Search Results (430594 CVEs found)

CVE Vendors Products Updated CVSS v3.1
CVE-2026-133701 1 Free5gc 1 Smf 2026-11-21 3.1 Low
free5GC SMF through 1.4.6 contains a resource exhaustion vulnerability in HandlePDUSessionSMContextLocalRelease that orphans SM contexts and UE IP addresses when PFCP session deletion fails. Attackers can send repeated PDU session establishment requests reusing an existing SUPI and PDU Session ID during PFCP deletion failures to exhaust the DNN's UE IP pool.
CVE-2026-133699 1 Free5gc 1 Smf 2026-11-21 3.1 Low
free5GC SMF through 1.4.6 contains a resource exhaustion vulnerability because sendPDUSessionEstablishmentAccept returns early without calling RemoveSMContextFromAllNF on failures. Authenticated UEs repeatedly establishing PDU sessions during NRF or AMF failures leak SM contexts, UE IP addresses and TEIDs, exhausting the DNN IP pool.
CVE-2026-133606 1 Powerjob 1 Powerjob 2026-11-21 5.3 Medium
A weakness has been identified in PowerJob up to 5.1.7. This affects the function CustomHttpServletRequestWrapper of the file powerjob-server/powerjob-server-starter/src/main/java/tech/powerjob/server/config/CachingRequestBodyFilter.java of the component CachingRequestBodyFilter. Executing a manipulation can lead to denial of service. It is possible to launch the attack remotely.
CVE-2026-133838 1 Flowintel 1 Flowintel 2026-11-21 N/A
FlowIntel contains an authorization bypass that allows non-approver case members to modify restricted tasks (those in Requested, Rejected, or Request Review status) through several indirect code paths that lacked the required approver permission check. Affected operations include: - Self-unassignment from a restricted task - Reordering tasks, including indirectly moving restricted sibling tasks - Linking or unlinking MISP objects and attributes to/from restricted tasks - Creating MISP objects or standalone attributes with task IDs referencing restricted tasks - Deleting MISP objects or attributes that are linked to restricted tasks - Executing modules on restricted tasks A user with case member access (but without Admin, Case Admin, or Queue Admin privileges) could exploit these paths to alter the state of tasks that are supposed to be locked pending approval, effectively bypassing the intended approval workflow and potentially manipulating associated MISP data. Affected versions: FlowIntel prior to 4.1.0
CVE-2026-133839 1 Flowintel 1 Flowintel 2026-11-21 N/A
FlowIntel contains a missing authorization vulnerability in its task file deletion functionality. When a privileged task is in a restricted state (Requested, Rejected, or Request Review), any authenticated user with basic case membership (e.g., editor or queuer) was able to delete evidence files associated with that task via both the browser interface and the REST API. The deletion operation should have been restricted to users holding Admin, Case Admin, or Queue Admin roles. The vulnerability affects the core file deletion logic, the browser-facing task endpoint, and the API task endpoint. No role-based restriction was enforced prior to performing disk removal, database record deletion, timeline event removal, or history log updates. An attacker with a low-privilege case membership could destroy evidence files, corrupt investigation timelines, and alter case history, compromising the integrity of ongoing investigations. Affected versions: FlowIntel prior to 4.1.0.
CVE-2026-133840 1 Flowintel 1 Flowintel 2026-11-21 N/A
flowintel contains an authorization bypass in the file-to-note conversion feature for case tasks. When a task is in a restricted workflow state (Requested, Rejected, or Request Review) within a privileged case, the conversion endpoint did not enforce elevated role requirements. Any authenticated user with basic case membership (e.g., editor or queuer) could invoke the conversion action, causing the system to read the attached file contents and create a note on the restricted task. This bypasses the intended workflow restriction that only Admin, Case Admin, or Queue Admin roles may modify tasks in those states. An attacker with a low-privilege account in a privileged case could: - Extract file contents into note format, potentially circumventing file-level access controls - Create unauthorized notes that alter the task's note count, modification timestamp, and case history - Disrupt the review/approval workflow on restricted tasks The vulnerability requires an authenticated user with at least editor-level access to the affected case and a task in one of the restricted states. Affected versions: flowintel < 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-133846 1 Flowintel 1 Flowintel 2026-11-21 N/A
FlowIntel contains an authorization bypass in its task management workflow. When a user reopens a completed task (by toggling its completion state or changing its status to a non-finished value) or creates a new task within a completed privileged case, the parent case is automatically revived (un-completed, status reset to Created, finish date cleared). The system failed to enforce the required Admin or Case Admin privilege check before performing this case revival side effect. A user with basic task-level permissions (e.g., editor, queuer, or queue admin) could trigger the revival of a completed privileged case through the browser interface or the REST API, without holding the elevated role required for case-level operations. This could disrupt case lifecycle management, clear completion metadata, and potentially expose the case to further unauthorized modifications. The vulnerability affects both the browser-based task completion/status-change endpoints and the corresponding API endpoints, as well as the task creation flow. Affected versions: FlowIntel prior to 4.1.0.
CVE-2026-133847 1 Flowintel 1 Flowintel 2026-11-21 N/A
flowintel contains an authorization bypass in the browser-based admin user editing interface. The edit_user view in the admin panel verified that a non-platform-admin user could only edit accounts belonging to their own organization, but it did not verify that the target account was not a platform-admin account. As a result, an authenticated user holding an organization-admin role could open the edit form for any platform-admin account and submit modifications, including changes to credentials, roles, or other account attributes. The API layer already enforced a restriction preventing non-admin users from targeting admin accounts, but the browser-based admin view lacked the equivalent check, creating an inconsistent authorization boundary. Impact: - Unauthorized modification of platform-admin account data (integrity) - Potential lockout or privilege manipulation of platform administrators (availability) - Escalation of an organization-admin role to effectively control platform-level administration Affected versions: flowintel prior to 4.1.0.
CVE-2026-133848 1 Flowintel 1 Flowintel 2026-11-21 N/A
flowintel contains an authorization flaw in its user deletion functionality. Organization-scoped administrators (org admins) are able to delete platform-level administrator accounts through both the browser-based admin interface and the REST API. The existing authorization logic verified that an org admin could only target users within their own organization, but it did not enforce the privilege hierarchy between organization admins and platform admins. As a result, an authenticated org admin could issue a deletion request against any platform-admin account belonging to the same organization, causing the target account, its sessions, and related records to be permanently removed. Impact: - Loss of platform-level administrative oversight - Potential disruption of platform-wide management functions - Removal of higher-privilege accounts that should be protected from lower-privilege roles Affected versions: flowintel prior to 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
CVE-2026-133850 1 Flowintel 1 Flowintel 2026-11-21 N/A
flowintel contains an authorization flaw in its recurring reminder notification subsystem. When a user is subscribed to recurring notifications for a case, the system does not re-verify the recipient's current access rights to that case before generating or displaying the notification. As a result, a user who previously had access to a private case and later had that access revoked can still: - Receive recurring reminder notifications containing case-related content. - View stored reminder notifications in their notification list, including notification counts, even though they no longer have permission to view the underlying case. The vulnerability affects both the notification creation path (recurring reminder generation) and the notification display path (listing and counting stored reminders). The issue arises because the authorization check performed at subscription time is not re-applied at delivery or retrieval time. Security impact is limited to information disclosure: an unauthorized user may observe case titles, reminder messages, and associated metadata that they no longer have permission to access. No integrity or availability impact is indicated by the patch. Affected versions: flowintel prior to 4.1.0.
CVE-2026-133851 1 Flowintel 1 Flowintel 2026-11-21 N/A
FlowIntel's alerting module contained an authorization bypass in the alert access control logic. When an alert was linked to a private case, the system relied solely on connector ownership (user or organization) to determine access, without verifying that the requesting user still held valid membership in the associated private case. This meant that a user who was a connector owner of an alert could continue to read alert details, review history, raw payloads, and action comments, and could perform review-status updates or case-creation actions, even after their access to the linked private case had been revoked or they were never a member of that case. Additionally, a time-of-check to time-of-use (TOCTOU) gap existed: after a review-status update or a competing case-creation claim was committed, the response could disclose private case identifiers or review history to a user whose access had been concurrently removed by another session linking the alert to a private case. Impact: - Unauthorized disclosure of private case data (review comments, raw payloads, action history) through alert endpoints. - Unauthorized modification of alert review status and creation of cases from alerts the user should no longer access. - Leakage of a competing case identifier to an unauthorized user during concurrent case-creation races. Affected versions: FlowIntel prior to 4.1.0.
CVE-2026-133852 1 Flowintel 1 Flowintel 2026-11-21 N/A
flowintel is a case management application that enforces an approval workflow for tasks in privileged cases. Tasks in such cases are required to start in a Requested status, meaning they must receive explicit approval before becoming active. A logic flaw in the task-creation path allowed tasks to be initialized with a Created status (bypassing the approval step) in two scenarios: - When a task was created from a template and no acting user was supplied, the privileged-case check was skipped entirely, leaving the task in Created status. - When a case was created from a template, all copied tasks were unconditionally assigned the Created status regardless of the case's privileged designation. An authenticated user with the ability to create tasks from templates or to instantiate cases from templates could therefore place tasks directly into an active state within privileged cases, circumventing the intended approval gate. This may expose restricted case content or permit actions that should require supervisory sign-off. Affected versions: flowintel prior to 4.1.0.
CVE-2026-133853 1 Flowintel 1 Flowintel 2026-11-21 N/A
FlowIntel's chatbot component used a single shared MCP (Model Context Protocol) session and process-wide environment variable to pass per-user API credentials to a child process. Because the session and the ambient FLOWINTEL_API_KEY environment variable were shared across all concurrent requests, a user's authenticated identity could be applied to another user's tool invocation, or a stale/ambient credential could be inherited by a new request. Preconditions: - An authenticated user with access to the chatbot interface. - Concurrent or overlapping chatbot tool invocations from different users, or a request made after another user's credentials were written to the process environment. Impact: - A lower-privilege user could read data belonging to a higher-privilege user (e.g., private investigation cases). - A user whose session was invalidated (deleted, password changed, key revoked) could still operate under a previously cached ambient credential. - The parent process environment was mutated with user-specific secrets, creating a persistent credential leak surface. Affected versions: FlowIntel prior to 4.1.0.
CVE-2026-133855 1 Flowintel 1 Flowintel 2026-11-21 N/A
flowintel contains an information disclosure vulnerability in its case history feature. When a user views the history of a case they are authorized to access, the history output includes references to other cases (linked, unlinked, or forked) without verifying whether the requesting user has permission to view those referenced cases. This exposes the identifiers and titles of cases that the user should not be able to discover. The vulnerability affects multiple output paths: - Browser-based case history view - API history endpoint - Plain-text history download - Markdown history download - Report timeline generation An authenticated user with access to any single case can enumerate the existence and identifiers of other cases by reading the history of a case they can access. This bypasses the intended per-case access control model and may reveal the existence of sensitive investigations, their identifiers, and associated metadata to unauthorized users. The raw audit storage is not modified; the issue is solely in the presentation layer failing to filter references to inaccessible cases before returning history data to the user. Affected versions: flowintel prior to 4.1.0.
CVE-2026-133730 1 Redhat 3 Enterprise Linux, Openstack, Rhel Els 2026-11-21 5.9 Medium
A flaw was found in dnsmasq, where a memory handling issue exists in its Dynamic Host Configuration Protocol for IPv6 (DHCPv6) relay processing. A remote attacker can exploit this vulnerability by sending a sequence of network packets to a system configured as a DHCPv6 relay. This causes the service to write data to previously freed memory and crash, resulting in a Denial of Service (DoS).
CVE-2026-133536 2 Red Hat, Redhat 5 Red Hat Build Of Keycloak 26.4, Build Keycloak, Build Of Keycloak and 2 more 2026-11-21 4.3 Medium
A flaw was found in Keycloak. The OpenID Connect (OIDC) logout endpoint continues to honor post-logout redirect rules for disabled clients rather than rejecting the requests. If a disabled client retains permissive redirect configurations, a remote attacker can exploit this issue by supplying an arbitrary redirection target in a logout request, leading to an open redirect that can be used in phishing attacks.
CVE-2026-133537 2 Red Hat, Redhat 5 Red Hat Build Of Keycloak 26.4, Build Keycloak, Build Of Keycloak and 2 more 2026-11-21 6.8 Medium
A flaw was found in Keycloak. When evaluating access permissions, Keycloak Authorization Services improperly matches resource paths containing wildcard file extensions by evaluating only the file extension suffix and ignoring configured path prefixes. An authenticated remote attacker could exploit this vulnerability by requesting a restricted resource that shares a file extension with a more permissive resource, leading to an authorization bypass and unintended access to protected data.
CVE-2026-133482 1 Hrshadhin 1 Cloudschool 2026-11-21 2.4 Low
A vulnerability has been found in hrshadhin CloudSchool up to 3.0.1. This affects the function EventController@store of the file app/Http/Controllers/Backend/EventController.php of the component Admin Content Management. Such manipulation of the argument data leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.