CVE-2026-43003: An issue was discovered in OpenStack ironic-python-agent 1.0.0 through 11.5.0.
An issue was discovered in OpenStack ironic-python-agent 1.0.0 through 11.5.0. Ironic Python Agent (IPA) sometimes executes grub-install from within a chroot of the deployed partition image, leading to code execution in the case of a malicious image.
Security readout for executives and security teams
Plain-English summary
A malicious deployment image can cause OpenStack Ironic’s provisioning agent to execute attacker-controlled code while preparing a server. Successful exploitation could compromise confidentiality, integrity, and availability beyond the vulnerable component. The issue is serious, but exploitation requires control of an image and the affected grub-install workflow.
Executive priority
Prioritize remediation for multi-tenant or delegated image-management environments because successful exploitation could cross component boundaries and fully compromise systems. Confirm exposure promptly, restrict untrusted images, and schedule vendor-supported updates. Controlled-image environments still require validation because the impact remains high.
Technical view
In ironic-python-agent 1.0.0 through 11.5.0, IPA sometimes runs grub-install inside a chroot created from the deployed partition image. This crosses a trust boundary because malicious image content can influence executed code. CVSS 3.1 rates it 8.5: network-accessible, high complexity, low privileges, no user interaction, and changed scope.
Likely exposure
Exposure is most likely where untrusted or lower-privileged users can provide or modify images deployed through OpenStack Ironic, and provisioning reaches the affected grub-install path. Environments using only tightly controlled images may have lower practical risk. The supplied affected-version data is inconsistent, so inventories should use the broader 1.0.0-through-11.5.0 description pending vendor confirmation.
Exploitation context
The supplied record is not in CISA KEV and provides no evidence of active exploitation. Exploitation requires a malicious image, low privileges according to the CVSS vector, and specific deployment behavior, reflected by high attack complexity. No exploit procedure or proof-of-concept status is established by the supplied sources.
Researcher notes
CWE-78 and CWE-829 support command or externally controlled code execution concerns. The narrative affects 1.0.0 through 11.5.0, while the structured affected list contains only 0, 11.0.0, and 11.3.0; this discrepancy requires vendor confirmation. Red Hat errata are referenced, but the bundle does not identify their fixed package versions or applicability.
Mitigation direction
Inventory ironic-python-agent deployments and treat versions 1.0.0 through 11.5.0 as potentially affected.
Review OpenStack and downstream vendor advisories for confirmed fixed packages, then apply applicable updates.
Restrict image submission and modification to trusted administrators until remediation is confirmed.
Verify image provenance and integrity before bare-metal deployment.
Consider pausing deployment of tenant-controlled images through affected provisioning workflows.
Validation and detection
Record installed IPA versions and compare them with OpenStack and downstream vendor advisories.
Identify every account and service permitted to upload, replace, or modify deployment images.
Confirm whether deployments invoke grub-install within the deployed image chroot.
Review provisioning logs for unexpected grub-install execution or anomalous image-related failures.
After updating, verify package versions against the applicable vendor erratum.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
3ADP providers
10Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-78 · source CWE mapping
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Inclusion of Functionality from Untrusted Control Sphere
Inclusion of Functionality from Untrusted Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.