A path traversal vulnerability in the Kibana Fleet feature allows a low-privileged user with write access to Fleet agent policies to cause an administrator to delete unintended resources. This can lead to unauthorized deletion of Kibana spaces and other organizational assets that the low-privileged user cannot delete directly. Exploitation requires an administrator to interact with the affected Fleet interface.
Kyverno versions before 1.19.2 have a denial of service vulnerability in the substituteVariablesIfAny function. This flaw allows low-privileged users to cause the admission webhook to hang by creating self-referential variable templates that lead to unbounded substitution loops. These loops exhaust CPU and memory resources, blocking cluster-wide admission. The issue is fixed in version 1.19.2.
A vulnerability in Kibana Observability onboarding allows an authenticated user with onboarding privileges to obtain credentials embedded in Elasticsearch host URLs. These credentials are used by Kibana to connect to Elasticsearch. Exploiting this flaw enables the user to access Elasticsearch with the Kibana service account's privileges, which exceed their own. Fixed versions are available.
Kyverno versions from 1.17.0 up to but not including 1.19.2 contain an authorization bypass vulnerability that permits namespace administrators to escape their namespace confinement. This occurs because the cleanup controller constructs its context loader with a nil policy, allowing attackers to create a namespaced CleanupPolicy with specific context entries to read Secrets across namespaces and modify validating webhook configurations using the cleanup controller's ServiceAccount. The vulnerability is fixed in version 1.19.2.
CVE-2026-115292 is an authorization bypass vulnerability in Kibana Machine Learning that allows an authenticated user with Machine Learning read access in one Kibana space to access audit and error messages of data frame analytics jobs in other unauthorized spaces. This can lead to information disclosure of job details such as destination index names, analyzed field names, and failure information. The issue affects multiple Kibana versions prior to fixed releases 8.19.24, 9.4.9, and 9.5.6.
Kyverno versions from 1.17.0 up to but not including 1.19.2 contain an authorization bypass vulnerability. This flaw allows namespace tenants to overwrite resources in other namespaces via the NamespacedMutatingPolicy mutate-existing targetMatchConstraints.expression. Attackers can craft a CEL map literal that specifies an arbitrary metadata.namespace, enabling the privileged background controller to overwrite Secrets, Deployments, or policies across the cluster. The issue is fixed in version 1.19.2.
Kyverno versions before 1.19.2 have a critical privilege escalation vulnerability. Namespace administrators can exploit generate-rule admission checks that incorrectly verify the controller's permissions instead of the policy author's. This flaw allows attackers to create policies with generate rules that affect other namespaces or cluster-scoped resources, enabling unauthorized cluster-wide resource creation or cloning.
This vulnerability exists in e-Sushrut HMIS due to insufficient authentication and session validation in the dashboard functionality. An unauthenticated remote attacker could exploit this vulnerability by sending specially crafted HTTP requests to the affected endpoint.
Successful exploitation of this vulnerability could allow the attacker to gain unauthorized access to the dashboard information associated with the targeted healthcare organization.
Jenkins versions 2.587 and earlier, including LTS 2.580.1 and earlier, have a vulnerability where file paths attempting path traversal are improperly identified in the file browser for workspaces and $JENKINS_HOME/userContent/. This allows attackers with Overall/Read permission to obtain metadata such as names, sizes, and last modification times of files within $JENKINS_HOME. Additionally, attackers with Item/Workspace permission can obtain the names of jobs that have a workspace on the same agent. The issue is fixed in Jenkins 2.588.0 and LTS 2.580.2.
A missing permission check vulnerability in Jenkins versions 2.587 and earlier, including LTS 2.580.1 and earlier, allows attackers with Overall/Read permission to access sensitive HTTP proxy configuration details such as server, port, user name, and no-proxy host list.
Jenkins versions 2.587 and earlier, including LTS 2.580.1 and earlier, have a vulnerability where the restriction on deserializing certain nested configuration objects is not consistently enforced. This flaw allows attackers to bypass root element checks and potentially inject nested objects into the configuration.
Jenkins versions 2.587 and earlier, including LTS 2.580.1 and earlier, contain a stored cross-site scripting (XSS) vulnerability due to improper escaping of text in the tooltips of breadcrumb bar overflow menu entries. This flaw can be exploited by attackers who have Overall/Read permission to execute malicious scripts in the context of the Jenkins web interface. Fixed versions 2.588.0 and 2.580.2 address this issue.
Jenkins versions 2.587 and earlier, including LTS 2.580.1 and earlier, contain a vulnerability that allows agents to send exceptions implementing the Stapler HttpResponse interface to the controller. This behavior results in a cross-site scripting (XSS) vulnerability that can be exploited by attackers who control agent processes. The issue is fixed in Jenkins versions 2.588.0 and 2.580.2.
Jenkins versions 2.587 and earlier, including LTS 2.580.1 and earlier, have a cross-site scripting (XSS) vulnerability. This flaw arises because the URL of the link shown in the workspace browser for each file and directory is computed on the agent side, allowing attackers controlling agent processes to exploit this behavior. The vulnerability is fixed in Jenkins 2.588.0 and LTS 2.580.2.
Jenkins versions 2.587 and earlier, including LTS 2.580.1 and earlier, contain a vulnerability that allows attackers with Overall/Read permission to trigger warnings in the 'Manage Old Data' feature. These warnings can be exploited by administrators to inject attacker-controlled data, potentially overriding existing user account information such as login passwords. Fixed versions 2.588.0 and 2.580.2 address this issue.
Jenkins versions 2.587 and earlier, including LTS 2.580.1 and earlier, have a vulnerability where requests authenticated using HTTP Basic authentication with an API token can obtain a "remember me" cookie. This allows attackers who have obtained a user's API token to maintain access to Jenkins via the "remember me" cookie even after the API token is revoked or expires.
Jenkins versions 2.587 and earlier, including LTS 2.580.1 and earlier, contain a vulnerability in the HTTP endpoint used for creating the first user account. This endpoint does not verify whether the setup wizard has been completed, leading to a race condition. An unauthenticated attacker can exploit this flaw to create an administrator account during the initial user account replacement process.
Jenkins versions 2.587 and earlier, including LTS 2.580.1 and earlier, have a vulnerability in how symbolic links are checked during artifact extraction. The software only checks for symbolic links in the path before creating parent directories, not immediately before writing the extracted file. This flaw allows attackers with Item/Configure permission to write files to arbitrary locations on the Jenkins controller file system by exploiting symbolic links in artifacts.
Jenkins versions 2.587 and earlier, including LTS 2.580.1 and earlier, have an HTTP endpoint that loads agents by name without validating the name. This flaw allows attackers with Overall/Read permission to load any config.xml file on the controller filesystem as an agent configuration and overwrite arbitrary config.xml files when saving the agent, potentially leading to arbitrary code execution.
Jenkins versions 2.587 and earlier, including LTS 2.580.1 and earlier, have a vulnerability where symbolic links are followed when copying the directory of an item being renamed. This behavior allows attackers with Item/Create and Item/Configure permissions to read arbitrary files on the Jenkins controller file system. The issue is fixed in Jenkins 2.588.0 and LTS 2.580.2.