Threats Tagged 'cve-2026-45363'

Red Hat Satellite 6.16.13 for RHEL 8 and 9 addresses multiple security vulnerabilities including arbitrary code execution, authentication bypass, denial of service, HTTP request smuggling, and information disclosure. These issues affect components such as jackson-databind, ruby-jwt, python-aiohttp, Eclipse Jetty, and jackson-core. The update fixes these vulnerabilities and also resolves a bug related to content view filtering.

Red Hat Satellite 6.19.0 through 6.19.4 for RHEL 9 contains multiple security vulnerabilities affecting components such as ansible-core, openvox-server, puppetserver, rubygem-jwt, python-aiohttp, and python-gitpython. These vulnerabilities include arbitrary code execution, authentication bypass, denial of service, HTTP request smuggling, information disclosure, and arbitrary file overwrite. Red Hat has released an update (6.19.4) addressing these issues.

Red Hat Satellite 6.17.11 update addresses multiple security vulnerabilities affecting components such as jackson-databind, jackson-core, AIOHTTP, ruby-jwt, Eclipse Jetty, and ansible-core. These vulnerabilities include arbitrary code execution, denial of service, authentication bypass, HTTP request smuggling, and information disclosure. The update also fixes several bugs related to upgrade and migration issues. The vulnerabilities affect Red Hat Satellite 6.17 versions from 6.17.0 up to but not including 6.17.11.

Red Hat Satellite 6.18 prior to 6.18.9 contains multiple security vulnerabilities including HTTP request smuggling, denial of service, information disclosure, arbitrary code execution, and authentication bypass. These issues affect components such as aiohttp, Eclipse Jetty, jackson-core, ansible-core, puppetserver, and ruby-jwt. The update to version 6.18.9 addresses these vulnerabilities and several bugs related to upgrade and functionality issues.

ruby-jwt is a Ruby implementation of the RFC 7519 OAuth JSON Web Token standard. Prior to 2.10.3 and 3.2.0, JWT.decode(token, '', true, algorithm: 'HS256') accepts an attacker-forged token because OpenSSL::HMAC.digest('SHA256', '', payload) returns a valid digest under an empty key and no empty-key precondition exists in the HMAC algorithm. The same path is reached when a keyfinder block or key_finder: argument returns an empty string, nil, or an array containing nil for an unknown key, affecting HS256, HS384, and HS512 verification through JWT.decode and JWT::EncodedToken#verify_signature!. This issue is fixed in versions 2.10.3 and 3.2.0.