RHSA-2026:98440HighCVSS 8.8

Red Hat Security Advisory: Red Hat AI Base Images 3.5.7 (CUDA 12.9)

Published
November 11, 2026
Last Modified
November 17, 2026

🔗 CVE IDs covered (17)

📋 Description

CVE-2026-1965 — curl: curl: Authentication bypass due to incorrect connection reuse with Negotiate authentication CVE-2026-3783 — curl: curl: Information disclosure via OAuth2 bearer token leakage during HTTP(S) redirect CVE-2026-8286 — curl: curl: Insecure connection establishment due to TLS configuration mismatch CVE-2026-8458 — curl: libcurl: Unauthorized connection reuse due to a logical error CVE-2026-8924 — curl: curl: Cookie injection via malicious HTTP server using super cookies CVE-2026-8927 — curl: Information disclosure due to uncleared proxy authentication state CVE-2026-8932 — libcurl: libcurl: Security feature bypass due to improper mTLS connection reuse CVE-2026-9547 — curl: curl: Man-in-the-middle attack via SSH host key bypass CVE-2026-11856 — curl: curl: Information disclosure via incorrect Digest authentication header reuse CVE-2026-13732 — gdb: gdb: Out-of-bounds write in STABS parser read_member_functions() via crafted ELF CVE-2026-64832 — ffmpeg: FFmpeg: Arbitrary code execution via crafted video file in NVDEC hardware decoder CVE-2026-64833 — ffmpeg: FFmpeg: Information disclosure and denial of service via out-of-bounds read in S/PDIF muxer CVE-2026-70628 — ffmpeg: FFmpeg: Arbitrary code execution via crafted WTV file in DVB subtitle parser CVE-2026-75142 — ffmpeg: FFmpeg: Stack Buffer Overflow in MPEG-PS Muxer CVE-2026-75144 — ffmpeg: FFmpeg: Memory corruption via crafted Dirac data unit CVE-2026-75146 — ffmpeg: FFmpeg: Information disclosure and denial of service via out-of-bounds read in DASH demuxer CVE-2026-88806 — libX11: libX11: Heap-based buffer overflow via malicious X server

🎯 Affected products3

  • Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhai/base-image-cuda-12.9-rhel9@sha256:1003a99a6bc111d833fa94c56c6b99f9adf23cf81693ebda9188e4fe2371574a_amd64 as a component of Red Hat OpenShift AI 3.5
  • registry.redhat.io/rhai/base-image-cuda-12.9-rhel9@sha256:493172c398ec4f133523bb69b8b198741f9e5246ab98efe3b4b1f83879cb02ac_arm64 as a component of Red Hat OpenShift AI 3.5

✅ Remediation

For more information visit https://access.redhat.com/errata/RHSA-2026:98440 Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Workaround: To prevent the leakage of OAuth2 bearer tokens, ensure that `.netrc` files are carefully managed. Avoid configuring `.netrc` entries for untrusted or unknown hostnames, particularly when `curl` is used with OAuth2 bearer tokens and is configured to follow redirects. Regularly review and restrict the scope of credentials stored in `.netrc` files to only explicitly trusted destinations. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: Do not use trailing-dot hostnames in URLs passed to curl. Trailing dots are uncommon and incompatible with TLS SNI. Upgrade to curl 8.21.0 to resolve Workaround: To mitigate this issue, applications utilizing libcurl should avoid reusing handles when switching between different proxy configurations. This operational control prevents the unintended leakage of `Proxy-Authorization` headers to incorrect proxies. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Correct usage of the library: Create a fresh handle for a different origin, or explicitly clear authentication-related state before reuse: ```c // req.A curl = curl_easy_init(); ... curl_easy_cleanup(curl); // req.B curl = curl_easy_init(); ... curl_easy_cleanup(curl); ``` Fixed in libcurl 8.21.0; affected range: 7.10.6 – 8.20.0 Workaround: The following practices would help for avoiding exposure and mitigate this flaw: - Do not open untrusted or unknown ELF binaries in GDB without first stripping debug sections. Use `objcopy --remove-section=.stab --remove-section=.stabstr <binary>` before debugging. - Use `readelf -S <binary> | grep stab` to check for the presence of STABS sections before opening a binary in GDB. Legitimate modern binaries use DWARF, not STABS. - Consider using LLDB or other debuggers that do not support STABS for analysis of untrusted binaries. - For automated environments (CI, test farms) that invoke GDB on potentially untrusted binaries, run GDB in a sandboxed or containerized environment with restricted filesystem access. - GDB 17+ deprecates STABS support but still parses it. GDB 18 (expected late 2026/2027) will remove STABS support entirely. - GCC removed STABS emitting in GCC 13 (2023), so legitimately compiled binaries from recent GCC versions will not contain STABS data. Workaround: No mitigation is currently available for this flaw. Workaround: To mitigate this issue, avoid processing untrusted WTV (Windows Recorded TV Show) files, especially those containing DVB subtitles. Exercise caution when handling multimedia files from unknown or suspicious sources. Workaround: To mitigate this issue, users should avoid connecting to untrusted X servers. When using SSH, ensure that X11 forwarding (`ssh -X` or `ssh -Y`) is only enabled for trusted remote hosts. To prevent X11 forwarding for specific hosts, add `ForwardX11 no` to the relevant host entry in `~/.ssh/config` or `/etc/ssh/ssh_config`. Alternatively, disable X11 forwarding globally by setting `ForwardX11 no` in `/etc/ssh/ssh_config`.

🔗 References (21)