Git LFS versions from 0.5.0 up to 2.13.3 and from 3.0.0 up to 3.8.0 may incorrectly forward Cookie HTTP headers to unintended hosts after HTTP redirections. Authorization headers are not forwarded incorrectly. This issue is fixed in version 3.8.1, which prevents forwarding Cookie and Authorization headers to hosts different from the original request. Users should upgrade to 3.8.1 to mitigate this risk.
Git LFS versions from 0.5.0 up to 2.13.3 and from 3.0.0 up to 3.8.0 contain a vulnerability where the path component of SSH URLs is not properly quoted when used in remote commands. This allows an attacker to inject shell meta-characters and potentially execute arbitrary commands on the remote host if the host executes these commands without proper sanitization. The issue is fixed in version 3.8.1. Users can mitigate by upgrading or configuring Git LFS to avoid SSH transfers, though authentication requests over SSH remain.
A flaw has been found in shader-slang slangpy up to 0.43.1. This vulnerability affects the function tinyexr::DecodePixelData in the library external/include/tinyexr.h of the component EXR Image Loader. Executing a manipulation can lead to out-of-bounds read. The attack may be performed from remote.
TeamPass versions prior to 3.2.2.0 contain an authorization bypass vulnerability in the update_folder action. Authenticated non-read-only users can rename, re-parent, and convert any folder to personal, effectively taking ownership of another team's credential subtree and removing it from the organization's view. This occurs because the update_folder action lacks proper authorization checks on the folder ID and new parent ID. The vulnerability allows unauthorized access to credential metadata and denies access to legitimate owners. A fix is available in version 3.2.2.0.
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.
flowintel contains a vulnerability in the case and task classification usage endpoints that allows authenticated users to view classification data associated with cases they do not have permission to access.
The affected endpoints, which provide lists of used taxonomies, tags, galaxies, clusters, and custom tags, did not properly enforce object-level access controls. While the endpoints required authentication, they failed to filter the returned data based on the requesting user's visibility permissions for the underlying cases. This allowed any authenticated user to enumerate classification usage across all cases, including private or restricted cases belonging to other organizations or users.
This issue could lead to the disclosure of sensitive information, such as the existence of specific cases, the types of threats or indicators associated with them, and the relationships between different classification elements, potentially aiding an attacker in reconnaissance or targeting.
Affected versions: < 4.1.0
Incorrect Authorization vulnerability in phoenixframework phoenix_live_view allows an authenticated user to mount a router-mounted LiveView without the on_mount hooks of its live_session via a phx_join message that carries neither a "url" nor a "redirect" key.
The catch-all clause of the private Phoenix.LiveView.Channel.authorize_session/3 in lib/phoenix_live_view/channel.ex accepts a join without a URL for any session, including a root LiveView mounted at the router. The channel then mounts the LiveView with no route, and only a route adds the live_session hooks to the mount lifecycle. Checks that those hooks perform on the connected mount do not run, and event checks that they attach through attach_hook/4 are never attached. The attacker needs a valid session token for the LiveView, which only the HTTP render issues, after the hooks pass there. on_mount hooks declared in the LiveView module still run.
This issue affects phoenix_live_view: from 0.16.0 before 1.0.20, from 1.1.0-rc.0 before 1.1.34, and from 1.2.0-rc.0 before 1.2.14.
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.
aMQTT versions 0.11.0 through 0.11.3 contain a denial-of-service vulnerability due to improper MQTT topic-filter validation combined with catastrophic regular-expression backtracking. A malicious client can freeze the broker by sending a crafted SUBSCRIBE packet with malformed topic filters containing multiple '+' wildcards, causing the broker's event loop to block. This results in complete broker unavailability until the process is restarted. The issue is patched in version 0.11.4.
A vulnerability in the go-guerrilla SMTP server allows a remote unauthenticated client to crash the SMTP daemon by sending a bare XCLIENT command without arguments. This triggers a slice bounds out-of-range panic due to an off-by-one error in command parsing when the xclient_on feature is enabled. The panic occurs in the per-connection goroutine without recovery, causing the entire server process to crash.
Poste.io is vulnerable to remote code execution in DMARC report processing. Email sent to dmarc-reports@<domain> is saved without sender verification. Script that runs as root unpacks the attachments using unsafe shell commands, allowing command injection through crafted attachments (e.g. file names or archive contents). A remote unauthenticated attacker who can send an email to the server's port 25 can execute arbitrary commands as root within the Poste.io container.
This issue was fixed in version 2.5.22.
CVE-2026-104129 is a SQL injection vulnerability in the _groupby function-expression of the pREST project. The vulnerability arises because the _groupby parameter is filtered by a weaker validation function (isSafeSQLExpression) compared to the stricter sanitizeSelectField used for _select, allowing nested subqueries and UNION SELECT statements to pass. This flaw permits attackers to inject arbitrary SQL expressions in the GROUP BY clause, potentially exposing sensitive data. The issue was introduced as an incomplete fix of CVE-2025-58450 and affects pREST versions up to 1.5.5 and before 2.4.0. A fix is available in version 2.4.0, which routes _groupby through the stricter validation gate.
The js-toml library's load() function parses TOML input using recursive parsing and interpretation without enforcing a maximum nesting depth. Deeply nested arrays, inline tables, or dotted keys cause recursion to exceed the V8 JavaScript engine's call stack limit, triggering an uncaught RangeError. This error differs from the expected SyntaxParseError, breaking error handling contracts and potentially crashing Node.js processes if unhandled. The issue affects versions prior to 1.1.3 and is fixed in 1.1.3.
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.
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.
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.
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
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
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.
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.