CVEs of 2026.
Every CVE published in 2026 that we hold, ranked by exploit odds.
-
CVE-2026-59011
In multiple locations, there is a possible permission bypass due to a logic error in the code. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
-
CVE-2026-59012
In checkLastKnownCellIdAccessPermission of TelephonyPermissions.java, there is a possible permission bypass due to a missing permission check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
-
CVE-2026-19030
Observable Discrepancy vulnerability in Drupal CAPTCHA for Drupal 7 allows unauthenticated attackers to test login credentials despite CAPTCHA protection. When CAPTCHA is enabled on Drupal login forms, normal form validation can still run after a missing or incorrect CAPTCHA response. This may expose credential validation feedback and allow an attacker to distinguish invalid credentials from valid credentials paired with a failed CAPTCHA. This issue affects CAPTCHA for Drupal 7: from 7.x-1.0 through 7.x-1.7.
-
CVE-2026-54026
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.6, POST /api/messages/:conversationId authorizes req.params.conversationId in api/server/middleware/validateMessageReq.js but persists attacker-controlled req.body.conversationId through api/server/routes/messages.js. An authenticated attacker can use an owned conversation in the URL while naming a victim conversation in the body, causing an attacker-controlled message to be stored in the victim conversation. This issue is fixed in version 0.8.6.
-
CVE-2026-134126
WPC Smart Messages for WooCommerce plugin before 4.3.6 contains a missing authorization vulnerability that allows authenticated attackers with Contributor or Author privileges to disclose arbitrary post meta and private product data by supplying attacker-controlled id and key attributes to the [wpcsm_product_field] and [wpcsm_product_data] shortcodes without any capability or protected-meta checks. Attackers can embed these shortcodes in a published post to exfiltrate sensitive order data such as billing email, phone, and address stored as post meta, as well as private or draft product descriptions and purchase notes, exposing confidential customer and business information to unauthenticated site visitors.
-
CVE-2026-54046
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.7, unauthenticated POST /api/user/verify requests in api/server/routes/user.js call api/server/services/AuthService.js verifyEmail and return distinct responses for unknown, verified, and unverified email addresses and the route lacks request throttling. A remote attacker can submit candidate addresses with invalid tokens to enumerate registered accounts and verification state, supporting targeted phishing or credential attacks. This issue is fixed in version 0.8.7.
-
CVE-2026-54039
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. From 0.7.0 until 0.8.6, when local registration is enabled and at least one social provider is configured, POST /api/auth/register passes an unparsed request object into api/server/services/AuthService.js, allowing an unauthenticated attacker to persist a forged provider value for a known victim email. The api/strategies/socialLogin.js email-fallback path then accepts the planted record when the victim signs in because it compares the stored provider name without requiring the provider subject identifier. The victim OAuth session and the attacker local-password session become bound to the same user record, giving the attacker persistent read and write access to data created by the victim. The first-user administrator role is an additional conditional impact only on a fresh deployment. This issue is fixed in version 0.8.6.
-
CVE-2026-54042
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.7, POST /api/auth/2fa/verify-temp in api/server/routes/auth.js calls verify2FAWithTempToken and accepts repeated TOTP or backup-code guesses without a dedicated attempt limiter. An attacker must first possess valid primary credentials and a valid five-minute temp token, but can then make repeated second-factor attempts and obtain a full session if a valid code is guessed. This issue is fixed in version 0.8.7.
-
CVE-2026-54043
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.7, packages/data-schemas/src/methods/file.ts updateFileUsage accepts chat attachment files[].file_id values without restricting the lookup to the authenticated owner. An authenticated attacker who obtains another user's file identifier, including through GET /api/share/{shareId} for a shared conversation, can attach that file to a chat, causing extracted document text to enter the model context. The same operation can remove expiration metadata from the victim file. This issue is fixed in version 0.8.7.
-
CVE-2026-54044
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.7, POST /api/agents/actions/:agent_id in api/server/routes/agents/actions.js loads an existing action with owner credentials and merges editor-controlled metadata.domain and metadata.raw_spec while preserving metadata.api_key and related OAuth client secrets. A collaborator with EDIT permission can repoint an action to an attacker-controlled host, and a later tool invocation decrypts and sends the retained owner credential to that destination. This issue is fixed in version 0.8.7.
-
CVE-2026-54045
LibreChat is an enhanced ChatGPT clone that supports multiple AI providers. Prior to 0.8.7, POST /api/auth/requestPasswordReset calls deleteTokens by user ID before creating a reset token, while password-reset and email-verification records in packages/data-schemas/src/methods/token.ts have no populated flow type. When password reset is enabled and email verification is enforced, an unauthenticated attacker who knows a target email can repeatedly delete pending verification tokens and prevent account verification until the unverified account expires. This issue is fixed in version 0.8.7.
-
CVE-2026-129176
U.S Department of the Interior Unstable Slope Management Program accepts a POST request from an unauthenticated user, with no cookie header, to a specific endpoint allowing for the deletion of specified users. Fixed on or around 2026-10-19.
-
CVE-2026-129177
U.S Department of the Interior Unstable Slope Management Program contains a vulnerable endpoint that allows an unauthenticated attacker, without a cookie header, to send a POST request resulting in the creation of a new user. Fixed on or around 2026-10-19.
-
CVE-2026-129179
U.S Department of the Interior Unstable Slope Management Program allows attackers with valid local application credentials to establish an application session by sending JSON POST requests to the application's login endpoint without a Referrer header or completing the intended Keycloak flow. Fixed on or around 2026-10-19.
-
CVE-2026-114497
codebase-memory-mcp provides local code intelligence for developers and AI agents through a persistent graph and MCP tools. Prior to 0.9.1-rc.1, the optional graph UI's POST /api/process-kill route omitted the indexing-job ownership check on Windows while retaining that check on POSIX systems. A requester able to reach the optional UI could supply an arbitrary process identifier, causing TerminateProcess to stop any process that the server user was permitted to terminate. The flaw affects the Windows-specific process termination path and can cause a high availability impact without disclosing or modifying data. This issue is fixed in version 0.9.1-rc.1.
-
CVE-2026-96805
The affected products have an unauthenticated command injection, which may allow an in-range BLE device to gain access to write to the control interface and influence braking with no authentication or pairing.
-
CVE-2026-94566
NukeViet CMS is a multi Content Management System. In 4.6.00, an unauthenticated attacker can rotate X-Forwarded-For because vendor/vinades/nukeviet/Core/Ips.php accepts forwarded client-IP headers without first confirming that REMOTE_ADDR is a trusted proxy. The resulting NV_CLIENT_IP keys the administrator login blocker in includes/core/admin_login.php; changing only the header value bypasses that lockout and permits effectively unlimited password guesses. The same spoofable address is also consumed by the user login blocker in modules/users/funcs/login.php, IP restrictions, bans, flood controls, and security logs, but those additional code-level effects were not dynamically demonstrated. This issue is fixed in version 4.6.01.
-
CVE-2026-106075
Rocket.Chat's POST /api/v1/chat.sendMessage endpoint improperly validates nested message properties, allowing authenticated users with standard privileges to inject arbitrary message metadata that is persisted and trusted by the server and clients. This can lead to persistent room-level denial of service, stored HTML/iframe injection, unauthorized modification of other users' private starred messages, permission bypass and attribution spoofing for pinned messages, forged edit attribution, and invisible user mentions.
-
CVE-2026-55216
Logto is the modern, open-source auth infrastructure for SaaS and AI apps. Prior to 1.46.0, social account linking can use an unverified email returned by the standard OAuth 2.0 or Azure AD connector to select an existing local account. When findSocialRelatedUser matches a victim's email and a request to POST /api/experience/identification enables linkSocialIdentity, an attacker who controls that unverified provider email can link an attacker-controlled social identity to the victim account and sign in as the victim. The issue applies when the provider does not verify email ownership or allows the value to be set freely; Google, GitHub, and default OIDC connector behavior is not affected because those paths expose only verified email. Version 1.46.0 adds an opt-in email synchronization control to the standard OAuth 2.0 connector, while the Azure AD connector has offered an equivalent opt-in control since version 1.43.0. These controls preserve existing behavior by default, so administrators must enable them on affected connectors. A configurable mitigation is available in version 1.46.0.
-
CVE-2026-104186
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.
-
CVE-2026-104184
LinkAce is a self-hosted archive to collect website links. Prior to 2.6.0, LinkController::update() in app/Http/Controllers/API/LinkController.php passes $request->all() to the repository update method even though user_id is fillable and is not an allowed field in the validated update request. An authenticated API user who is authorized to update a link can therefore assign an arbitrary or nonexistent user_id, transferring the link into another user's bookmark collection or orphaning it from any real account. The web update controller is unaffected because it passes only validated fields. This issue is fixed in version 2.6.0.
-
CVE-2026-82675
The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to donor account account takeover in all versions up to, and including, 4.17.0. This is due to the plugin not properly validating a donor's identity prior to updating the password of a linked WordPress account. The donation receipt processes an attacker-controlled first name through the V3 template engine and then reprocesses the result through the legacy `{meta_donor_*}` engine, which can disclose the donor's email-access bearer token. The donor-dashboard password endpoint accepts that token by itself and calls `wp_set_password()` for the WordPress user linked to the donor. This makes it possible for unauthenticated attackers to reset the password of any WordPress account linked to a GiveWP donor record and gain access to that account. If the linked account is an administrator, the attacker can achieve full site compromise and remote code execution through standard administrator functionality. A published GiveWP form with a usable gateway, enabled donor email access (enabled by default), knowledge of the donor email address, and an account already linked to the targeted donor record are required. NOTE: This vulnerability can be chained with CVE-2026-82676 to satisfy the administrator donor pre-requisite for a targeted administrator user attack.
-
CVE-2026-82676
The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.16.7.2. This is due to missing nonce validation on the `give_render_donor_view()` function. This makes it possible for unauthenticated attackers to reassign an arbitrary GiveWP donor record to an arbitrary WordPress user via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. The resulting association changes donor-account ownership and can satisfy the linked-donor precondition for a separately tracked account-takeover vulnerability (CVE-2026-82675).
-
CVE-2026-79751
SportEase is a web application for managing school sports events, class rosters, and competition teams. Prior to 1.3, an authenticated account with is_profile_complete=false can submit an attacker-selected class_id for any class in the currently active event to PUT /api/user/profile during first profile completion. AuthHandler.UpdateProfile accepts the class without validating the user's legitimate membership and automatically derives and assigns the corresponding {class_name}_rep role while isFirstCompletion is true. The attacker can become representative of one selected class, view roster information including email addresses, and add or remove competition-team assignments. Downstream handlers correctly reject access to other classes, so the impact is bounded to the selected class, but the representative privilege cannot be revoked through the exposed API and requires direct database intervention or another out-of-band remediation method. This issue is fixed in version 1.3.
-
CVE-2026-133878
Mattermost versions 11.11.x <= 11.11.1, 11.7.x <= 11.7.14, 11.10.x <= 11.10.4 fail to restrict the broadcast scope of group WebSocket events to sessions permitted to read the group which allows an authenticated user, including guests, to obtain the display name, description, member count and member IDs of non-referenceable groups via the received_group event emitted when a group is created, updated, deleted or restored. Mattermost Advisory ID: MMSA-2026-00731
-
CVE-2026-133879
A flaw was found in KubeVirt/containerized-data-importer. When a VirtualMachine with an embedded DataVolumeTemplate carrying the cdi.kubevirt.io/storage.checkStaticVolume annotation and a cross-namespace clone source is created by a tenant, the service-account clone authorization check can be bypassed, allowing a PVC from another namespace to be cloned into the tenant's namespace without the required permissions. This can result in cross-tenant data disclosure.
-
CVE-2026-133872
LessPass self-hosted sync server backend before commit 9469b0c lacks rate limiting on the JWT login endpoints /tokens/auth/ and /auth/jwt/create/, allowing unlimited authentication attempts. Unauthenticated remote attackers can brute force passwords or perform credential stuffing against known account emails to obtain tokens granting read and write access to stored profiles.
-
CVE-2026-133874
Iceburg CRM through 5.0.0 contains an incorrect authorization vulnerability in Module::saveRecord() that allows authenticated users to write to unauthorized modules by prefixing request body keys with another module id. Attackers with write access to one module can submit crafted requests to POST /data/save or PUT /api/crm/{id} to set their role_id to Admin and access administrative data.
-
CVE-2026-133199
Incorrect privilege assignment in the user and group reconciliation logic in AWS ssosync before 2.9.5 might allow an authenticated remote user who is assigned a reused Google Workspace e-mail address or group name to inherit the IAM Identity Center group memberships and permission set assignments of a previously synchronized, unrelated identity, via automatic synchronization of that Google Workspace account or group. To remediate this issue, users should upgrade to version 2.9.5 or later.
-
CVE-2026-122247
Budibase is an open-source low-code platform. Prior to 3.50.0, the public POST /api/global/users/init endpoint on a self-hosted single-tenant deployment accepts an attacker-controlled tenantId and evaluates checkAnyUserExists() in the selected tenant database instead of the legitimate default tenant. An unauthenticated attacker can select an unused tenant namespace to bypass the one-time initialization guard, causing packages/worker/src/api/controllers/global/users.ts to create a tenant-specific CouchDB database and a global-administrator document without a session or CSRF token. Repeating this operation with unique tenant identifiers can exhaust datastore resources and leave latent privileged records. The created administrator cannot log into the default tenant while multi-tenancy remains disabled, which limits the immediate impact to persistent writes, denial of service, and records that may become usable during later multi-tenant operation or migration. This issue is fixed in versions 3.50.0 and 4.0.0.
-
CVE-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.0
-
CVE-2026-133849
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
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
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
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-133843
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
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
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
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-133837
flowintel contains an authorization bypass in its task completion workflow for privileged cases. Users with lower-privilege roles (editor, queuer) were able to mark tasks as completed without the required approver review (Admin, Case Admin, or Queue Admin), undermining the approval workflow. The vulnerability was exploitable through multiple paths: - Direct task completion via browser UI or REST API - Changing a task's status to "Finished", which implicitly completed the task - Creating a new task in a privileged case with the completed flag already set - Using UUID aliases or Matrix delegation to reach the same endpoints Preconditions: - An authenticated user with at least editor or queuer role - A privileged case with tasks in a non-completed state Security impact: - Bypass of the mandatory approver review process for privileged cases - Unauthorized modification of task completion state - Potential to mark sensitive work as finished without proper oversight Affected versions: flowintel prior to 4.1.0
-
CVE-2026-133838
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
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
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-132665
In Postgres Enterprise Manager (PEM), the pem.deploy_job_template() function does not check that the caller can access the servers, groups and agents it deploys a job template to. When PEM teams are used to separate access, a user with the scheduled tasks role (pem_manage_schedule_task) can deploy and schedule SQL or shell job steps on agents that belong to other teams. From PEM 10.6.1, PEM checks team access for every server, group and agent a template is deployed to.
-
CVE-2026-132668
In Postgres Enterprise Manager (PEM), any PEM user can run the pem.send_webhook() function, which runs with elevated privileges and queues a payload for any configured webhook. The PEM agent then delivers it with that webhook's stored headers, OAuth token or client certificate, so a user can send forged notifications to endpoints they could not otherwise authenticate to. From PEM 10.6.1, no PEM login role can call this function directly. PEM still sends webhook notifications through its own internal paths.
-
CVE-2026-132658
In Postgres Enterprise Manager (PEM), the pem_agent role, which every PEM agent login inherits, is a member of the PostgreSQL pg_read_server_files and pg_write_server_files roles on the PEM backend database. An attacker who controls any monitored host, and so its PEM agent certificate, can read and write files on the PEM server host as the postgres operating system user. This includes the PEM certificate authority key, which lets the attacker issue certificates for other agents and act as them. From PEM 10.6.1, PEM agents no longer hold these roles.
-
CVE-2026-132659
In Postgres Enterprise Manager (PEM), the row-level security policies on pem.job and pem.jobstep that apply to PEM agents do not limit an agent to its own jobs. An attacker who controls one monitored host, and so its PEM agent certificate, can create, change or delete jobs for every other agent, including the agent on the PEM server. Agents run SQL job steps with the database credentials of the server they monitor, and shell job steps where batch jobs are enabled, so compromising one monitored host can give superuser SQL access to every monitored database and to the PEM backend. From PEM 10.6.1, PEM agents can no longer create jobs or change job definitions or job steps.
-
CVE-2026-132661
In Postgres Enterprise Manager (PEM), multi-factor authentication (MFA) is not enforced on the PEM web application's own routes. An attacker who knows the password of a user who has enrolled a second factor can skip the second factor and call PEM's pages and APIs directly, with that user's permissions. A similar issue in pgAdmin 4 was assigned CVE-2024-4215. From PEM 10.6.1, every authenticated PEM route requires a completed MFA check.
-
CVE-2026-126334
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.
-
CVE-2026-80188
The BuddyBoss Addons plugin for WordPress is vulnerable to Authentication Bypass leading to Account Takeover in versions up to, and including, 1.2.1. This is due to the Social Login REST endpoint trusting unverified Apple and Facebook identity-token claims and linking an attacker-controlled provider identifier to an existing WordPress user selected by the token’s email claim. This makes it possible for unauthenticated attackers who know a user’s email address to associate their provider identity with that account, including administrator accounts, and subsequently authenticate as the victim. Successful exploitation requires the BuddyBoss Platform plugin to be installed and active, with the Social Login module and selected provider enabled and configured. On sites with the separate BuddyBoss App JWT component, the vulnerable REST request can return an application token immediately.
CVE records published in 2026 (ids starting CVE-2026-), sorted by how likely they are to be exploited.