CVE-2026-131715
Missing Authorization vulnerability in Kaliforms Kali Forms kali-forms allows Exploiting Incorrectly Configured Access Control Security Leve
CVSS
5.3
Média
EPSS
—
KEV
—
Exploit Today
0
0-100
Publicado: 20 de nov. de 2026 · Última mod.: 20 de nov. de 2026 · CWE-862
Ainda não há histórico EPSS suficiente.
Missing Authorization vulnerability in Kaliforms Kali Forms kali-forms allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Kali Forms: from n/a through 2.4.32.
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-1041864.3 MÉD—
———LinkAce is a self-hosted archive to collect website links. Prior to 2.6.0, the authenticated GET /lists/{list}/feed and GET /tags/{tag}/feed handlers in app/Http/Controllers/App/FeedController.php use integer route model binding without an object-level authorization or visibility check. Unlike the web list controller, which invokes LinkListPolicy::view(), the feed controller lets a normal authenticated user enumerate another user's private list or tag and receive its name and feed metadata, along with public or internal bookmark entries associated with that taxonomy. The existing per-link visibility filter still excludes PRIVATE link records, so the disclosure is limited to the private taxonomy and its non-private member links. This issue is fixed in version 2.6.0.2hCVE-2026-133855——
———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.3hCVE-2026-133854——
———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.03hCVE-2026-133852——
———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.3hCVE-2026-133851——
———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.3hCVE-2026-133850——
———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.3h