Skip to main content
CVE-2026-97687VulnerabilityPublished

Red Hat Security Advisory: Red Hat AI Base Images 3.0.10 (ROCm)

Affects Red HatSource GCVE Database

0
Compare

Not known to be exploited.

Data as of 13 Nov 2026, 14:48 UTC

Severity
High

Rated by Threat Radar · CVSS not yet scored by NVD

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 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

Red Hat has not provided a fix for this vulnerability in Red Hat AI Base Images 3.0.10 (ROCm) as of the advisory date. Users should evaluate their application architectures to determine if they use HTTPS-capable proxies with customized TLS parameters that override proxy verification. Default deployments communicating directly with endpoints or using standard HTTP proxies with CONNECT tunneling are not vulnerable. Monitoring Red Hat advisories for updates or patches is recommended. Customers with a Technical Account Manager (TAM) can consult directly for tailored guidance. No generic mitigations are specified beyond avoiding vulnerable proxy configurations.

Description

A vulnerability in urllib3 used by Red Hat AI Base Images 3.0.10 (ROCm) allows a remote network attacker to intercept and modify HTTPS proxy traffic. The flaw arises when TLS settings for the target server overwrite the proxy's TLS configuration, disabling certificate verification on reused connections. This enables an attacker to impersonate the proxy, potentially capturing or altering sensitive data and client credentials. Default Red Hat deployments that do not use customized TLS parameters with HTTPS proxies are not affected.

References

Community reviews

Loading reviews…