Latest

Most recently published vulnerabilities

Back to overview
PrioritiseCVE-2026-129713danfoss · ak-sm8xxaStack-based buffer overflow in Danfoss AK-SM8xxA unauthenticated CGI handlerA stack-based buffer overflow in an unauthenticated CGI handler of the Danfoss AK-SM 8xxA Series controller allows remote attackers to send specially crafted HTTP/S POST requests, leading to memory corruption, webserver restart and hypothetically potential arbitrary code execution with webserver privileges. Authentication is not required to exploit this vulnerability.CVSS9.3CriticalPrioritiseCVE-2026-124770xone · xonemanagerMultiple Vulnerabilities in XOne's XOneManagerAuthorization bypass in the ‘tablesData’ operation of the POST request to ‘/xmanagercore/api/services/’ in XOneManager 3.8.3.0. An authenticated project member can execute SQL queries using ‘filter’ without the server verifying their execution permissions. The queries use the service account’s permissions. During testing, databases outside the project were queried, including the authentication database.CVSS9.4CriticalRoutineCVE-2026-133661flowintelFlowIntel: Missing Authorization and Credential Scope Enforcement in Connector and Template FeaturesFlowIntel contains multiple authorization and credential management vulnerabilities affecting connector instances, MISP helper tools, and case templates. - Connector instance metadata, connectivity checks, and case listings accepted instance IDs without verifying if the acting user had visibility or ownership rights, allowing unauthorized access to sensitive configuration and data. - Case template serialization and creation processes exposed connector instances attached to templates regardless of the user's permissions, potentially leaking credentials or instance details to users who should not have access. - Editing connector instances allowed changes to URLs or sharing scopes without requiring re-authentication of API keys, enabling the reuse of another user's credentials in a new context or the leakage of shared keys to unauthorized endpoints. - Outbound MISP connector keys were incorrectly accepted for authenticating incoming alerts, bypassing the intended separation between outbound integration credentials and inbound alert source authentication. These issues allow authenticated users to access unauthorized connector data, manipulate credential scopes, and potentially exploit credential confusion between different security contexts. Affected versions: < 4.1.0CVSS5.3MediumRoutineCVE-2026-133660flowintelFlowIntel Cross-Organisation User Directory and Assignment Information DisclosureFlowIntel contains an authorization bypass in its user directory and assignment endpoints that allows authenticated users to access data belonging to other organisations. When the LIMIT_USER_VIEW_TO_ORG setting is enabled to restrict directory visibility to the caller's organisation, several API endpoints (user lookup by ID, last name, Matrix ID, and role-based listings) did not consistently enforce the organisation boundary. An authenticated non-admin user could retrieve profiles of users in other organisations by supplying their identifiers. Additionally, OrgAdmin users could retrieve the task assignments of any user in the system, including tasks and case titles from private cases to which they had no access. The assignment endpoints did not verify that the requested user belonged to the caller's organisation or that the underlying cases were visible to the caller. Security impact: - Exposure of user identities (names, Matrix IDs, roles) across organisation boundaries - Disclosure of task assignments, case titles, and workflow details from private cases - Potential enumeration of other organisations' membership and case activity Affected versions: FlowIntel prior to 4.1.0CVSS7.1HighRoutineCVE-2026-133659flowintelFlowintel SSO Identity and Organisation Trust Boundary Violations Allow Account Takeover, Privilege Escalation, and Unauthorized Case AccessFlowintel 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.CVSS8.6HighRoutineCVE-2026-133658flowintelFlowintel Matrix Relay Authorization Bypass Allows Privilege Escalation and Bot ImpersonationFlowintel contains a privilege escalation vulnerability in its Matrix relay (bot) integration. When the relay forwarded API requests on behalf of a represented user, the authorization and permission checks evaluated the relay bot's elevated role while the request handlers acted as the lower-privileged represented user. This mismatch allowed users with restricted roles (e.g., Read Only) to perform write operations, directory lookups, calendar modifications, assignment changes, template creation, and import actions they were not authorized to perform. Additionally, relay authority was determined by matching editable user profile fields (name and email) rather than a protected, non-spoofable identifier. An ordinary user who modified their profile to match the expected bot name could be recognized as the trusted relay, enabling impersonation of the bot and potential access to its elevated privileges. Preconditions: - A valid Flowintel user account with a restricted role (e.g., Read Only) - Access to the Matrix relay integration or the ability to send API requests with the relay's API key and a MATRIX-ID header - For the impersonation vector: ability to edit one's own profile name fields Security impact: - Unauthorized write operations by users with read-only or otherwise restricted permissions - Potential impersonation of the trusted relay bot by ordinary users - Bypass of organization-level access controls and role-based restrictions - Unauthorized modification of cases, tasks, calendar events, templates, and user directory entries Affected versions: Flowintel prior to 4.1.0CVSS6.3MediumPrioritiseCVE-2026-127057danfoss · ak-sc 355 +1 moreExploitation of Weak or Known Passwords in Danfoss AK-SC 355 and AK-SM 800 SeriesThe Danfoss legacy AK-SC 355 and AK-SM 800 Series are vulnerable to unauthorized access when default credentials or known passwords are used for authentication. These products were manufactured with default credentials documented in the product manual. All versions are affected.CVSS9.9CriticalRoutineCVE-2026-124771xone · xonemanagerMultiple Vulnerabilities in XOne's XOneManagerAuthorization omission in the 'admusers' operation of the POST request to '/xmanagercore/api/services/' in XOneManager 3.8.3.0. The API fails to verify the required role for querying the directory. An authenticated member of the project can obtain the list of platform accounts—including administrative accounts—along with details such as email addresses, roles, and associated companies.CVSS5.3MediumRoutineGCVE-1-2026-20396flowintelflowintel flowintelFlowIntel, a MISP-based threat intelligence platform, contains an authorization bypass vulnerability affecting multiple case-related endpoints and shared alert operations. The vulnerability stems from missing role and case-membership checks on several server-side routes: - Connector module execution endpoints lacked a write-permission (editor) check, allowing read-only users to trigger connector modules that access external platform credentials and perform data synchronization. - Standalone MISP attribute creation, editing, and deletion endpoints verified case visibility but did not require the acting user to be a member of an organization assigned to the case, permitting non-members to modify public cases and trigger MISP send schedules. - Sync automation and conflict-resolution endpoints accepted requests from read-only users who held the MISP-editor role, bypassing the intended write-permission gate. - Shared case-alert read and delete actions were accessible to any authenticated user without write permission. An authenticated user with a read-only role, or a user not assigned to a case's organization, could therefore perform write operations on cases, execute connector modules, alter MISP attributes, and trigger outbound data synchronization to external MISP instances. Security impact includes unauthorized modification of threat-intel case data, unauthorized triggering of data exfiltration to external MISP or connector platforms, and disruption of shared alert state for all users. Affected versions: FlowIntel prior to 4.1.0.CVSS8.3HighRoutineGCVE-1-2026-20397flowintelflowintel flowintelflowintel contains an access-control flaw in its case-creation-from-template workflow. When a case is created via a template, the requested privacy flag is silently discarded, causing the new case to be visible to other organisations that should not have access to it. Additionally, the shared template factory ignores the ENFORCE_PRIVILEGED_CASE configuration, allowing both the template-creation path and the MISP event-conversion path to bypass the enforced four-eye (privileged-case) workflow. A secondary timing issue exists in the MISP event conversion path: the case is first committed to the database without the private flag and only marked private in a subsequent write, creating a window during which the case and its contents are accessible to unauthorised organisations. Impact: - Cases intended to be private are exposed to other organisations. - The enforced privileged-case (four-eye) workflow can be bypassed when cases are created through templates or MISP conversion. - A brief visibility window exists during MISP-driven case creation. Affected versions: flowintel prior to 4.1.0.CVSS7.1HighRoutineGCVE-1-2026-20398flowintelflowintel flowintelFlowintel contains an access control vulnerability in the case history and audit log endpoints. The application failed to enforce role-based authorization checks, allowing any authenticated user with visibility to a case to access sensitive audit data and case history, regardless of their assigned role (e.g., Admin, Case Admin, or Audit Viewer). Additionally, the audit log retrieval mechanism was susceptible to injection and ambiguous matching. The previous implementation relied on simple string matching for case identifiers, which could be manipulated to expose logs belonging to other cases or bypass intended scoping restrictions. Furthermore, the AI report generation feature inadvertently exposed protected case data. The system included full case history and stored prompts in the input for AI models and exposed legacy automatic prompt metadata in API responses and exports. This allowed users with access to shared AI reports to view sensitive case details that they were not explicitly authorized to see. Affected versions: < 4.1.0CVSS7.1HighRoutineCVE-2026-133503modelcloud · gptqmodelModelCloud GPTQModel Adapter Resolution Pipeline remote.py gptqmodel.adapter.remote.resolve_path input validationA security vulnerability has been detected in ModelCloud GPTQModel up to 7.6.0. Affected by this vulnerability is the function gptqmodel.adapter.remote.resolve_path of the file gptqmodel/adapter/remote.py of the component Adapter Resolution Pipeline. Such manipulation of the argument adapter.path leads to improper input validation. The attack may be launched remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 7.7.0 addresses this issue. The name of the patch is ed99ac8d59940bf27bb24ce2e80002ae9e44469f. It is advisable to upgrade the affected component.CVSS7.5HighRoutineCVE-2026-131761magepeople inc. · booking and rental managerWordPress Booking and Rental Manager plugin <= 2.8.5 - Broken Access Control vulnerabilityMissing Authorization vulnerability in Magepeople inc. Booking and Rental Manager booking-and-rental-manager-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Booking and Rental Manager: from n/a through 2.8.5.CVSS5.3MediumRoutineCVE-2026-131716awesomemotive · charitableWordPress Charitable plugin <= 1.8.15.1 - Cross Site Request Forgery (CSRF) vulnerabilityCross-Site Request Forgery (CSRF) vulnerability in Awesomemotive Charitable charitable allows Cross Site Request Forgery.This issue affects Charitable: from n/a through 1.8.15.1.CVSS4.3MediumRoutineCVE-2026-131715kaliforms · kali formsWordPress Kali Forms plugin <= 2.4.32 - Broken Access Control vulnerabilityMissing 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.CVSS5.3MediumRoutineCVE-2026-129044brainstorm force · starter templatesWordPress Starter Templates plugin <= 4.7.11 - Broken Access Control vulnerabilityMissing Authorization vulnerability in Brainstorm Force Starter Templates astra-sites allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Starter Templates: from n/a through 4.7.11.CVSS5.4MediumRoutineCVE-2026-133631flowintelFlowIntel Insecure Note Variable Resolution, Over-Permissive Chatbot API Access, and Credential Exposure in Process ArgumentsFlowIntel contains multiple security flaws in its note variable resolution, chatbot API tooling, and AI report generation. - Note variable references (e.g. cross-case or cross-task lookups) were resolved using the viewing user's privileges rather than the destination case's audience. An authenticated user with access to a shared or imported note could embed references to private cases, causing sensitive case data to be pulled into AI report requests, exports, and MISP sends without the referenced case's audience having granted read access. - The chatbot API tool permitted the language model to invoke any FlowIntel API endpoint, including administrative routes and state-changing GET operations, without an allow-list or path validation. An attacker who can influence the model's instructions (e.g. via untrusted case content) could induce data modification or access restricted endpoints. - AI report generation passed the Ollama bearer token and full case content as command-line arguments to a child process, exposing them in the system process table to any local user. Affected versions: FlowIntel prior to 4.1.0.CVSS7.1HighRoutineCVE-2026-133630flowintelflowintel CI/CD Workflow Exposes Checkout Credentials in Docker Build CacheThe flowintel Docker build workflow used the GitHub Actions checkout action with default credential persistence, causing the job authentication token to be written into the repository's Git configuration file. This file became part of the Docker build context and could be retained in exported build cache layers, even though Git metadata was stripped from the final runtime image. An attacker with access to the CI/CD build cache or build environment could extract the persisted token and use it to gain unauthorized access to the private source repository. Impact: - Exposure of a valid authentication token to the private repository - Potential unauthorized read access to source code and repository metadata Affected versions: flowintel < 4.1.0CVSS5.9MediumPrioritiseCVE-2026-96771lbell · hydrogen calendar embedsHydrogen Calendar Embeds <= 3.0.3 - Unauthenticated Stored DOM-Based Cross-Site Scripting via ICS Feed Event Fields (SUMMARY/DESCRIPTION/LOCATION)The Hydrogen Calendar Embeds plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via ICS Feed Event Fields (SUMMARY/DESCRIPTION/LOCATION) in all versions up to, and including, 3.0.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the attacker to have write access to an ICS feed that has been configured as a calendar source on the target WordPress site.CVSS7.2HighRoutineCVE-2026-86587ezviz · certain ezviz devicesezviz certain ezviz devicesCertain EZVIZ devices are affected by an improper certificate validation issue (CWE-295). An attacker may intercept communication traffic to conduct a man-in-the-middle attack.CVSS5.3Medium