Skip to main content
CVE-2026-1965VulnerabilityPublished Updated

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

Affects Red HatSource GCVE Database

0
Compare

Mentioned vulnerabilities

Not known to be exploited · fixed in Red Hat package updates : patch Red Hat soon.

Data as of 13 Nov 2026, 14:48 UTC

Severity
High

Rated by Threat Radar · CVSS not yet scored by NVD

Patch
Available – fixed in 8.21.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

AI-suggested

Mitigation requires application developers to avoid reusing libcurl easy handles across different HTTP origins when Digest authentication is used. Alternatively, applications should explicitly clear authentication-related state before reusing handles. Upgrading to libcurl 8.21.0 or later, where the issue is fixed, is recommended when possible. Red Hat Product Security notes that currently available mitigations may not meet criteria for ease of use or widespread applicability.

Description

A vulnerability (CVE-2026-11856) was found in libcurl used in Red Hat AI Base Images 3.5.7 (CUDA 12.9). When libcurl reuses the same connection handle for HTTP Digest authentication transfers to different origins, it may incorrectly send authentication headers intended for the first origin to a second origin, potentially disclosing sensitive authentication state. This flaw affects libcurl versions from 7.10.6 up to 8.20.0 and is fixed in libcurl 8.21.0. The vulnerability requires a specific programming pattern of handle reuse and does not leak credentials themselves but the authenticated state header. Mitigation involves correct usage of libcurl by creating fresh handles for different origins or clearing authentication state before reuse.

References

Community reviews

Loading reviews…