Lighthouse AdvisorySLED AI Adoption Intelligence

Strategic PartnersIssue 052 records

Red Hat

A security-led Tuesday for Red Hat AI. Red Hat pushed 18 OpenShift AI base-image advisories on Nov. 3 that carry the fix for the Brotli flaw CISA lists as known-exploited, extending the Nov. 2 TrustyAI fix to CPU, CUDA, ROCm, Gaudi, Neuron, Spyre and TPU images; one CUDA model-serving image still shows Affected, and sites must rebuild derived images. A Red Hat blog maps post-quantum cryptography onto Red Hat AI Enterprise, useful for NIST-aligned planning but mostly roadmap. No SLED deployment news or independent evaluation surfaced; OpenShift AI 3.6 GA was still not observed.

Evidence records
2
Cross-source patterns
0
Evidence classes
2 vendor claim
Outcomes
1 cautionary1 emerging
Source freshness
2 new this fortnight
Research completed
2026-11-04

Choose a role to see its takeaway beside every record in the ledger.

Patterns across the evidence

Synthesis · Lighthouse Advisory interpretation

No pattern claimed

The evidence in this edition did not support a cross-source pattern. Each record below stands on its own.

Evidence ledger

Full record · every source keeps its link and limitations

2 records
  1. Vendor claimCautionaryNew this fortnight

    Red Hat ships 18 OpenShift AI base-image advisories carrying the KEV-listed Brotli fix, but the CUDA MLServer image is still Affected

    Vendor record: on Nov. 3, 2026 Red Hat issued 18 advisories (RHSA-2026:94452 to 94469) updating Red Hat AI Base Images for OpenShift AI 3.0, 3.4 and 3.5 across CPU, CUDA 12.9/13.0, ROCm, Gaudi, Neuron, Spyre and TPU. Every listed image picks up CVE-2026-111497, the Brotli decoder flaw; the 3.0.8 CPU image is rated Critical and lists 25 CVEs, and the CUDA 13.0 image (also Critical) lists 23. Red Hat's security data, checked the same evening, still shows the odh-mlserver-cuda serving image as Affected. Independent evidence: CISA lists the flaw as known-exploited, federal due date Nov. 10. Interpretation: this widens the Nov. 2 fix from one service image to the base images most custom workbenches and serving runtimes build on.

    Red Hat Product SecurityGlobal product advisory; applies to any US SLED deployment of OpenShift AI 3.0, 3.4 or 3.5RHSA-2026:94452 to 94469 issued Nov. 3, 2026; CVE public Oct. 22, 2026; CISA KEV listing Oct. 27, 2026

    Why it matters, evidence and limitations
    Why it matters
    Universities, research computing centers and state agencies that build custom notebooks or model-serving containers on Red Hat AI base images need to rebuild on the Nov. 3 digests, not just upgrade the OpenShift AI operator. Many states and campuses use the KEV list to set patch priority even though its deadline binds only federal agencies.
    Evidence and measured results
    Read RHSA-2026:94459 and RHSA-2026:94468, the Red Hat security data JSON for CVE-2026-111497 (18 Nov. 3 affected_release entries and package states) and the CISA KEV feed entry.
    Limitations and uncertainty
    Vendor self-assessment with terse advisories; the reason for the Critical rating is not stated. Package states were observed once (Nov. 3 evening CT) and may change. KEV does not say exploitation targeted AI platforms.
    RHSA-2026:94459 - Red Hat AI Base Images 3.0.8 (CPU) (Critical) Role takeaways & implementation
  2. Vendor claimEmergingNew this fortnight

    Red Hat maps post-quantum cryptography onto Red Hat AI Enterprise, mostly as roadmap

    Vendor claim: Red Hat says Red Hat AI Enterprise inherits hybrid ML-KEM TLS from RHEL 10 and OpenShift to counter 'harvest now, decrypt later' interception of datasets and inference traffic. It describes planned ML-DSA signing of pipeline container images via Red Hat Advanced Developer Suite, with admission blocking of invalid signatures, PQC mutual TLS through the service mesh, and model-artifact signing in the model registry that it calls 'in process'. It notes larger PQC keys add handshake bandwidth overhead. Independent context: NIST IR 8547 plans to deprecate quantum-vulnerable public-key algorithms after 2030 and disallow them after 2035. Interpretation: useful as a planning map, with most AI-specific pieces still roadmap.

    Red HatGlobal vendor guidance; US SLED relevance through NIST-aligned state and campus security programsBlog displayed Nov. 3, 2026 (page metadata datePublished Oct. 29, 2026)

    Why it matters, evidence and limitations
    Why it matters
    State agencies and universities holding long-lived sensitive data (health, benefits, student and research records) face the same harvest-now risk, and many follow NIST timelines. Teams planning on-premises AI platforms can use this to add PQC readiness questions to platform roadmaps and procurement.
    Evidence and measured results
    Read the Red Hat blog in full and the transition timeline sections of NIST IR 8547.
    Limitations and uncertainty
    Vendor roadmap blog without dates, benchmarks or customer evidence; display date and metadata date differ; NIST deadlines are federal and not binding on SLED entities.
    Future-proofing enterprise AI: The impact of post-quantum cryptography on Red Hat AI Enterprise Role takeaways & implementation

How to read this edition

Source findings, measured results and limitations come from the cited publications. Patterns, operating questions, role takeaways and implementation considerations are Lighthouse Advisory interpretation, stated as questions to validate locally rather than guaranteed outcomes. Vendor and operator claims are labeled as claims. Full research method.

Vendor claim
A supplier-provided assertion that has not been upgraded to independent evidence.