{"resourceId":"rhsa-2026-96333-rhel-ai-3-5-3-critical-60-cves-20261109","versions":[{"version":"external-4a6a1ee1bffb497b34af983e6cf03fe94b36baa0e391dc4cf4f485b5ecd889bb","resource":{"id":"rhsa-2026-96333-rhel-ai-3-5-3-critical-60-cves-20261109","title":"RHSA-2026:96333: Critical-rated RHEL AI 3.5.3 container image update lists 60 CVEs, including the vLLM multimodal RCE CVE-2026-114053","organization":"Red Hat Product Security","sector":"AI platform vendor security advisory","geography":"Global product","publishedAt":"2026-11-09","publicationDate":"2026-11-09","eventDate":"2026-11-09","sourceName":"Red Hat Customer Portal errata","sourceLabel":"Vendor security advisory","sourceUrl":"https://access.redhat.com/errata/RHSA-2026:96333","evidenceClass":"vendor-claim","outcomeClass":"cautionary","topics":["data-security","infrastructure"],"finding":"Red Hat issued RHSA-2026:96333 on 2026-11-09, rated Critical, providing updated RHEL AI 3.5.3 container images. The advisory lists 60 CVE identifiers, including CVE-2026-114053 (the vLLM multimodal remote-code-execution flaw archived on 21 Oct, when RHEL AI was listed as Affected), CVE-2026-115915 and CVE-2026-93592. The 'Fixes' field reads '(none)', and the advisory points to RHEL AI release notes for changes. On retrieval, the CVE-2026-114053 record (last changed 4 Nov) did not yet reference this advisory, so per-CVE fix status for RHEL AI could not be confirmed from that record.","sledRelevance":"Agencies and universities running RHEL AI for on-premises model serving (often chosen to keep sensitive data local) need to track this image update. Critical-rated AI-stack advisories with dozens of CVEs show the patch cadence such deployments must resource.","evidence":"Opened the advisory page and counted the 60 CVE IDs it lists. I also opened the CVE-2026-114053 record to check cross-references: it lists five other RHSAs but not 96333. I did not inspect individual CVE details beyond those already archived.","architectureImplications":"RHEL AI deployments pull updated container images from registry.redhat.io. Disconnected sites need mirroring workflows to apply them promptly.","governanceImplications":"Patch SLAs for AI-serving images should follow the agency's critical-vulnerability timelines. Advisory and CVE records may lag one another, so reconcile both.","securityPrivacyImplications":"The bundle includes CVE IDs this archive already covers as vLLM flaws (114053 code execution; 115915). Until updated images are deployed, internet- or tenant-exposed inference endpoints remain at risk.","caveats":"An advisory lists CVEs but does not by itself state exploitability in a given configuration. The cross-reference between advisory and CVE record was inconsistent at retrieval. I did not check NVD.","streamIds":["red-hat"],"roles":{"sales":"Sales framing: use this advisory to raise operational readiness, not fear. Customers who chose RHEL AI to keep data on-premises have taken on responsibility for patching the AI stack, and a Critical 60-CVE image update shows the cadence. Offer image-update automation and validation as a service conversation. Do not claim the update fixes any specific CVE until per-CVE records confirm it (interpretation).","engineering":"Engineering framing: inventory RHEL AI 3.5 deployments and pull the 3.5.3 images, mirroring them for disconnected sites. Reconcile the advisory's CVE list against individual CVE records, which at retrieval did not yet reference this advisory. Re-run model smoke tests after updating, and limit inference endpoint exposure to trusted clients until updated. Record the image digests deployed on each host (interpretation).","delivery":"Delivery framing: run this as a tracked change. Inventory the affected images, schedule the update within the agency's critical-patch window, mirror images where needed, and run regression checks on model outputs. Record which CVEs are confirmed fixed per CVE record. Acceptance is all RHEL AI hosts on 3.5.3 images within the agreed window, with test evidence (interpretation)."},"roleDetails":{"sales":{"customerProblem":"SLED teams running on-premises RHEL AI must absorb Critical, high-volume AI-stack patch bundles.","stakeholders":["AI platform owner","Vulnerability management lead","Research computing operations","Change manager"],"discoveryQuestions":["Where is RHEL AI 3.5 deployed, and are any hosts disconnected?","What is your critical-patch window for AI-serving images?","Are inference endpoints exposed beyond trusted clients?"],"valueHypothesis":"Bounded: automated image updates reduce exposure windows; value depends on local process.","potentialEngagement":"A patch-readiness review and image-update automation for RHEL AI hosts.","unsupportedClaims":["That every listed CVE is fixed for every configuration","That on-premises AI removes security maintenance"]},"engineering":{"fit":"Directly relevant to any RHEL AI 3.5 deployment.","architectureIntegration":"Container image update from registry.redhat.io; mirror for disconnected environments.","prerequisites":["RHEL AI 3.5 inventory","Registry access or mirror","Model regression tests"],"constraints":["Advisory and CVE record cross-references inconsistent at retrieval","Disconnected sites need mirroring"],"security":"Restrict inference endpoints to trusted clients until updated; verify image digests.","proofOfValue":["Confirm 3.5.3 image digests on all hosts","Verify CVE-2026-114053 status per CVE record once updated","Model output regression check after update"]},"delivery":{"work":"Plan and apply the RHEL AI 3.5.3 image update across hosts.","dependencies":["Change approval","Image mirroring","Test datasets for regression"],"ownership":"AI platform owner with vulnerability management oversight.","skillsAdoption":"Automate image tracking; train operators on advisory and CVE reconciliation.","governanceCheckpoints":["Change approval before update","Post-update regression sign-off"],"acceptanceCriteria":["Proposed: 100% of RHEL AI hosts on 3.5.3 images within the critical-patch window","Proposed: regression tests pass on agreed model prompts"],"risks":["Update breaking model behavior","Missed disconnected hosts","Assuming fixes not yet confirmed"]}},"retrievedAt":"2026-11-10T22:12:51-06:00","enrichedAt":"2026-11-10T22:35:00-06:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Small teams running RHEL AI need automated image update and rebuild pipelines, because manual tracking of 60-CVE bundles is impractical.","procurementImplications":"Support contracts and managed-service agreements for on-premises AI should define patch timelines for AI-serving images, not only the base OS.","operatingModelImplications":"AI platform owners need a recurring image-update cadence with regression testing of model behavior after each update.","sourceVerification":{"openedUrl":"https://access.redhat.com/errata/RHSA-2026:96333","referenceExcerpt":"Updated Red Hat Enterprise Linux AI 3.5.3 container images are now available.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}