SB20261022296 - Multiple vulnerabilities in IBM Guardium Data Protection
Published: October 22, 2026
Breakdown by Severity
- Low
- Medium
- High
- Critical
Description
This security bulletin contains information about 3 vulnerabilities.
1) Use of Non-Canonical URL Paths for Authorization Decisions (CVE-ID: CVE-2026-8384)
CWE-ID: CWE-647 - Use of Non-Canonical URL Paths for Authorization Decisions
CVSSv4: 6.9 [CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N]
The vulnerability allows a remote attacker to bypass path-based security constraints.
The vulnerability exists due to use of non-canonical url paths for authorization decisions in org.eclipse.jetty.util.URIUtil.canonicalPath() when processing request paths containing semicolon path parameters followed by slash-dot segments. A remote attacker can send a specially crafted request path to bypass path-based security constraints.
This can occur when Jetty SecurityHandler.PathMapped is used to protect a path prefix such as /admin/*, causing the non-normalized canonical path to be matched against security constraints.
2) Missing Release of Resource after Effective Lifetime (CVE-ID: CVE-2026-45536)
CWE-ID: CWE-772 - Missing Release of Resource after Effective Lifetime
CVSSv4: 4.8 [CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N]
The vulnerability allows a remote attacker to cause a denial of service.
The vulnerability exists due to improper resource shutdown in netty_unix_socket_recvFd when receiving SCM_RIGHTS control messages containing two file descriptors over a unix domain socket. A remote attacker can send a specially crafted message to cause a denial of service.
The issue is reachable via Epoll/KQueue DomainSocketChannel only when the application enables DomainSocketReadMode.FILE_DESCRIPTORS.
3) Incorrect authorization (CVE-ID: CVE-2026-41115)
CWE-ID: CWE-863 - Incorrect Authorization
CVSSv4: 5.3 [CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N]
The vulnerability allows a remote user to disclose sensitive group metadata.
The vulnerability exists due to improper access control in the CONSUMER_GROUP_DESCRIBE API when handling consumer group describe requests. A remote user can send a request to the API with DESCRIBE permission on the GROUP resource to disclose sensitive group metadata.
The issue stems from a discrepancy between the documented permission model and the implemented authorization check, which can lead to misconfigured ACLs.
Remediation
Install update from vendor's website.