High [CVE-2026-58659] Remote code execution via malicious checkpoint files
This high-severity Red Hat Linux advisory covers CVE-2026-58659 affecting Red Hat AI Inference Server 3.3, Red Hat AI Inference Server 3.4, Red Hat Enterprise Linux AI (RHEL AI) 3.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
PyTorch Lightning through 2.6.5, fixed in commit d710d68, contains a remote code execution vulnerability in the _load_state function that imports and executes attacker-controlled module names from checkpoint _instantiator hyperparameters.
Attackers can craft malicious checkpoint files that bypass weights_only=True protections to execute arbitrary code when LightningModule.load_from_checkpoint is called. This vulnerability allows attackers to achieve remote code execution by crafting malicious checkpoint files.
The vulnerability arises from the _load_state function's ability to import and execute attacker-controlled module names from maliciously crafted checkpoint files, even when weights_only=True is enabled. Exploitation requires a local attacker to trick a user into loading a specially crafted checkpoint file.
Red Hat severity: Important — CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Weakness: CWE-502.
Affected Red Hat products: Red Hat AI Inference Server 3.3; Red Hat AI Inference Server 3.4; Red Hat AI Inference Server; Red Hat Enterprise Linux AI (RHEL AI) 3; Red Hat OpenShift AI (RHOAI). Red Hat lists Red Hat OpenShift AI (RHOAI) as not affected.
Will not fix / out of support: Red Hat AI Inference Server. Red Hat fixing advisory: RHSA-2026:68698, RHSA-2026:68699, RHSA-2026:69466, RHSA-2026:69467, RHSA-2026:70965, RHSA-2026:70979.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 19 days ago·verify at source
- 2.6.5
- rhaiis/vllm-rocm-rhel9:1789504371
- rhaiis/vllm-cuda-rhel9:1789582776
- rhaii/vllm-cpu-rhel9:1789681128
- rhaii/vllm-cuda-rhel9:1789681126
- rhaii/vllm-cpu-rhel9:1790075793
- rhaii/vllm-cuda-rhel9:1790090131
- RHSA-2026:68698
- RHSA-2026:68699
- RHSA-2026:69466
- RHSA-2026:69467
- RHSA-2026:70965
- RHSA-2026:70979
Official advisory · high-confidence parse· fetched 19 days ago·verify at source
Mitigation
Upgrade to a fixed release: 2.6.5, rhaiis/vllm-rocm-rhel9:1789504371, rhaiis/vllm-cuda-rhel9:1789582776, rhaii/vllm-cpu-rhel9:1789681128, rhaii/vllm-cuda-rhel9:1789681126, rhaii/vllm-cpu-rhel9:1790075793. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 19 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.