How severe is GHSA-rmxr-45gj-889w?

GHSA-rmxr-45gj-889w has a CVSS score of 8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-rmxr-45gj-889w?

GHSA-rmxr-45gj-889w affects the following packages: ironic-python-agent (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-rmxr-45gj-889w?

Update ironic-python-agent to 11.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rmxr-45gj-889w is resolved across your whole dependency graph.

How do I detect GHSA-rmxr-45gj-889w in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ironic-python-agent. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-rmxr-45gj-889w if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-rmxr-45gj-889w?

O3 pinpoints whether GHSA-rmxr-45gj-889w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-rmxr-45gj-889w actively exploited in the wild?

No public exploit code has been indexed for GHSA-rmxr-45gj-889w yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-rmxr-45gj-889w published, and has it been updated?

GHSA-rmxr-45gj-889w was published on May 1, 2026 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-rmxr-45gj-889w

HIGH

GHSA-rmxr-45gj-889w is a high-severity (CVSS 8) remote code execution vulnerability in ironic-python-agent. O3 Security confirms whether GHSA-rmxr-45gj-889w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenStack Ironic Python Agent Includes Functionality from Untrusted Control Sphere

Also known asCVE-2026-43003PYSEC-2026-205

Published

May 1, 2026

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

🐍ironic-python-agent

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`ironic-python-agent`	≥ 1.0.0&&< 11.6.0	11.6.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ironic-python-agent. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update ironic-python-agent to 11.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rmxr-45gj-889w is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-rmxr-45gj-889w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-rmxr-45gj-889w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-rmxr-45gj-889w in your dependencies?

O3 detects GHSA-rmxr-45gj-889w across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works