IBM Guardium Data Protection version 12.2 contains a path traversal vulnerability in its datasource functionality. This flaw allows an authenticated attacker to delete arbitrary files on the appliance, potentially impacting the integrity and availability of the system. The vulnerability has a high severity rating with a CVSS score of 8.1.
IBM Guardium Data Protection version 12.2 has a vulnerability in the SharePoint S-TAP RelayService due to missing authentication. This flaw allows an unauthenticated network attacker to inject forged audit events and access the active monitoring policy. The vulnerability is rated critical with a CVSS score of 9.1, indicating high impact on confidentiality and integrity without requiring user interaction or privileges.
IBM Guardium Data Protection version 12.2 contains a critical SQL injection vulnerability in its edge-controller component. This flaw allows an unauthenticated remote attacker to potentially access or modify sensitive database information without any user interaction or privileges.
On Intel-based macOS systems, the Okta Device Access (ODA) component of Okta Verify for macOS configures a LaunchDaemon service that uses a symbolic link in /usr/local/bin for its program path. If local non-root users have write permissions to this directory, they can modify the symbolic link target. This allows execution of an arbitrary binary when the LaunchDaemon service restarts.
IBM Guardium Data Protection version 12.2 contains a stack-based buffer overflow vulnerability triggered by processing a specially crafted PROXY protocol v1 header. This flaw allows a remote attacker to cause denial of service or potentially execute arbitrary code on the affected system.
IBM Guardium Data Protection 12.2 contains a vulnerability that could allow a remote attacker to inject forged audit records. This issue arises from improper output neutralization for logs, potentially impacting the integrity of audit data. The vulnerability has a medium severity rating with a CVSS score of 5.9.
IBM Guardium Data Protection 12.2 contains a vulnerability in its GDP Terraform provider related to improper TLS certificate validation. This flaw allows a network attacker positioned for man-in-the-middle attacks to intercept sensitive credentials sent to the Guardium appliance. The vulnerability has a high severity rating with a CVSS score of 8.1.
IBM watsonx.data versions 2.4.0 through 2.4.0 patch 8 contain a vulnerability that allows a remote authenticated attacker to cause a denial of service. This issue arises from client-side enforcement of business rules, which can be bypassed or exploited to disrupt service availability.
IBM watsonx.data versions 2.4.0 through 2.4.0 patch 8 contain a server-side request forgery (SSRF) vulnerability that could allow a remote authenticated attacker to induce the server to make unauthorized requests. The vulnerability has a CVSS score of 4.3, indicating medium severity, and impacts the integrity of the system without affecting confidentiality or availability.
IBM Guardium Data Protection 12.2 contains an insecure deserialization vulnerability in the SharePoint Tap MulticastTransceiver component. This flaw allows an unauthenticated remote attacker to execute arbitrary code on the affected system. The vulnerability has a critical severity with a CVSS score of 9.8, indicating high impact on confidentiality, integrity, and availability.
IBM API Connect versions 10.0.8.0 through 10.0.8.13 contain an authorization vulnerability that allows a remote authenticated attacker to delete API keys belonging to other users. This flaw arises from improper authorization checks within the affected versions.
A high-severity vulnerability (CVE-2026-133201) exists in smartalock wireguard-lwip affecting the mul function in src/crypto/refc/x25519.c within the X25519 Ladder component. The flaw allows a remote attacker to cause an out-of-bounds write, potentially impacting availability. The project uses a rolling release model, so specific affected or fixed versions are not available. No vendor response or patch has been provided yet.
IBM watsonx.data versions 2.4.0 through 2.4.0 patch 8 contain a vulnerability that could allow unauthorized network access due to insufficient network segmentation controls. The vulnerability has a medium severity rating with a CVSS score of 5.3. No public exploits or known active exploitation have been reported. No patch or remediation details are provided in the available data.
Okta Privileged Access (OPA) Gateway uses a version of the FreeRDP library that has memory management vulnerabilities in its smartcard redirection feature. Under certain session conditions, this flaw may allow command execution with the local Gateway service account privileges. The vulnerability has a high severity score of 8.5 and impacts confidentiality, integrity, and availability. No specific affected versions or patches are currently provided.
CVE-2026-130236 is a high-severity vulnerability in the Auth0 Authorization Extension where request authentication handling can process claims from query parameters without proper header validation. This flaw may allow an authenticated tenant user to access administrative endpoints improperly. Additionally, input handling during rule generation can enable modification of the tenant login rule published by the extension.
IBM watsonx.data versions 2.4.0 through 2.4.0 patch 8 contain a vulnerability where sessions are not invalidated after logout. This flaw could allow an authenticated user to impersonate another user on the system.
IBM watsonx.data versions 2.4.0 through 2.4.0 patch 8 contain an improper access control vulnerability that could allow a remote attacker to obtain sensitive information. The vulnerability is identified as CVE-2026-14885 and has a medium severity rating with a CVSS score of 4.8. No public exploits or known active exploitation have been reported. No patch or remediation details are currently provided.
Splunk Enterprise versions below 9.4.17, 10.0.12, 10.2.9, and 10.4.5 contain a vulnerability where users without 'admin' or 'power' roles can configure metric alerts via the REST API that execute searches with elevated privileges. This occurs due to improper enforcement of role-based authorization during metric alert configuration, allowing unauthorized users to access or modify data and disrupt the Splunk instance.
Splunk Enterprise versions prior to 10.6.0, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 contain a vulnerability where users with the "power" role can inject attacker-controlled Search Processing Language (SPL) into shared data model calculations. When other users run searches against these shared data models, the injected SPL executes with their permissions, potentially exposing sensitive credentials. This occurs because Splunk does not properly neutralize data model calculation fields before including them in generated searches.
A vulnerability in Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.16 allows non-admin and non-power users to execute arbitrary Search Processing Language (SPL) commands via scheduled metric alert searches. This flaw arises from insufficient validation of metric alert filter inputs and requires at least one non-internal metric index on the instance.