SQLite versions prior to 3.54.0 that are built with the session extension contain a heap buffer overflow vulnerability in the sqlite3changeset_apply() function. This flaw allows attackers to corrupt heap memory by providing crafted changesets that exploit the sessionUpdateFind() function's improper handling of repeated table names with larger column counts. The vulnerability is fixed in version 3.54.0.
SQLite versions prior to 3.54.0 have a stack exhaustion vulnerability due to improper counting of common table expressions (CTEs) against the SQLITE_LIMIT_EXPR_DEPTH nesting limit. An attacker can exploit this by supplying a WITH clause chaining tens of thousands of CTEs, causing unbounded recursion in the selectExpander() function and crashing the process.
This vulnerability exists in e-Sushrut HMIS due to the exposure of internal hospital operational statistics through data structure embedded in the HTML response of the login page. An unauthenticated remote attacker could exploit this vulnerability by accessing the affected login page and extracting the returned HTML content.
Successful exploitation of this vulnerability could allow the attacker to gain unauthorized access to internal hospital operational information associated with the targeted healthcare organization.
A critical vulnerability in GitLab CE/EE versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 allows unauthenticated users to execute arbitrary code on the GitLab server. This occurs due to insufficient validation of specially crafted regular expressions in CI/CD configurations, leading to integer overflow or wraparound issues in Ruby versions 3.3.0 to before 3.3.13, 3.4.0 to before 3.4.12, and 4.0.0 to before 4.0.8. Public exploit code is available via Metasploit. Fixed versions have been released.
Moodle versions up to 5.3.0, including specific subversions of 5.2, 5.1, 5.0, and 4.5, contain a path traversal vulnerability in the Blackboard question import feature. This flaw allows teachers with import or lesson edit permissions to upload crafted zip files that exploit directory traversal sequences to copy sensitive server files such as config.php into their draft area.
phpMyAdmin versions up to 5.2.3 have an SQL injection vulnerability in the /database/central-columns endpoint. Authenticated users can exploit this by supplying unescaped values in the col_extra and col_attribute parameters. This allows injection into INSERT and UPDATE queries executed with controluser privileges, potentially enabling unauthorized reading or modification of other users' configuration-storage data.
phpMyAdmin versions up to 5.2.3 have an authentication bypass vulnerability in the WebAuthn two-factor authentication implementation. The flaw exists in CustomServer::parseAndValidateAssertionResponse(), which fails to verify WebAuthn assertion signatures against stored public keys. An attacker who already has a victim's MySQL credentials can exploit this by sending a crafted WebAuthn response with matching challenge, origin, and rpIdHash to bypass the second factor and gain unauthorized database access.
phpMyAdmin versions up to 5.2.3 contain an SQL injection vulnerability in the Designer saveSetting() function. Authenticated users can exploit this flaw by sending crafted parameters to the /database/designer endpoint, potentially overwriting other users' designer settings or executing controluser subqueries.
Kyverno versions from 1.19.1 before 1.19.2 contain a namespace isolation bypass vulnerability in the APICall Fetch() function. This occurs because the path.Clean function incorrectly treats the '?' character as part of the path, allowing a crafted URLPath query string to bypass namespace restrictions. An attacker with permission to create namespaced policies can exploit this to access cluster-scoped resources outside their namespace.
Kyverno versions from 1.19.1 up to but not including 1.19.2 contain a privilege escalation vulnerability. This flaw allows a namespace-scoped user who can create a Policy to exploit improper validation of the Policy's context.apiCall urlPath. By hiding '../' segments behind URL fragments or queries, the user can access cluster-scoped endpoints using Kyverno's ServiceAccount, effectively gaining cluster admin privileges. 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 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 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.
An authenticated Kafka principal without authorization can exploit a flaw in IncrementalAlterConfigs or AlterConfigs requests to read arbitrary broker files or environment variables. This occurs because configuration validation happens before authorization checks, allowing resolution of configuration variables that expose sensitive data. The issue affects Kafka versions before 4.2.2 and between 4.3.0 and 4.3.2. The vulnerability is mitigated by upgrading to versions 4.2.2, 4.3.2, or 4.4.0, which enforce authorization before configuration validation and restrict config-provider usage.
Apache Kafka versions prior to 4.2.2 and between 4.3.0 and 4.3.2 have a vulnerability in the parsing of flexible protocol request headers. An attacker can send a request with a large declared count of tagged fields, causing excessive memory allocation and potentially exhausting broker heap memory or causing process-wide garbage collection stalls. This can lead to denial of service on the broker. The issue occurs before authentication and authorization, so no ACL or quota is required to exploit it. Fixed in versions 4.2.2, 4.3.2, and 4.4.0.
Apache Kafka contains a vulnerability in its code-generated protocol readers where an attacker can cause the broker to allocate excessive heap memory by declaring an array length much larger than the actual request buffer size. This leads to an OutOfMemoryError and broker crash. The issue affects all Kafka API types with array fields and occurs before authorization checks, allowing unauthenticated attackers on unauthenticated listeners to exploit it. The vulnerability is fixed in Apache Kafka versions 4.2.2, 4.3.2, and 4.4.0.
Grafana contains an authorization bypass vulnerability (CVE-2026-100105) where users with permission to edit contact points but not their protected fields can exploit a schema downgrade to modify protected settings. This allows changing sensitive configurations such as destination URLs, potentially exposing stored credentials and redirecting alert notifications. The issue affects multiple versions prior to fixed releases in 12.4.14, 13.0.12, 13.1.9, and 13.2.5.
HashiCorp Consul and Consul Enterprise contain an authorization bypass vulnerability in health check registration. This flaw allows an authenticated user to modify health checks of another service on the same node. The issue affects versions from 0.7.2 up to but not including 2.1.0. The vulnerability is fixed in Consul Community Edition 2.1.0 and Consul Enterprise 2.1.0 and 1.21.19. No public exploit or in-the-wild exploitation has been reported. The severity is assessed as medium based on the impact described.
CVE-2026-128125 is a vulnerability in aiohttp's client CookieJar where unbounded cookie storage occurs due to improper Set-Cookie parsing and lack of limits on stored cookies. A malicious server can exploit this to cause excessive memory and CPU usage on the client by forcing it to store a very large number of cookies and send oversized Cookie headers on subsequent requests.