CVE-2026-42997
HIGHCVE-2026-42997 is a high-severity (CVSS 7.7) CWE-669 vulnerability in ironic-python-agent. O3 Security confirms whether CVE-2026-42997 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OpenStack Ironic has an Incorrect Resource Transfer Between Spheres
Blast Radius
ironic-python-agent🐍ironic-python-agent🐍ironic-python-agent🐍ironic-python-agentReal-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 idrac in OpenStack Ironic before 35.0.1. During import, a user invoking molds can request authorization to be sent to a remote endpoint. The credential forwarded is a time-limited Keystone token (which provides access to all OpenStack services Ironic is authorized for); or basic credentials configured for molds storage. The fixed versions are 26.1.6, 29.0.5, 32.0.1, and 35.0.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | ironic-python-agent | ≥ 33.0.0&&< 35.0.1 | 35.0.1 |
| 🐍PyPI | ironic-python-agent | ≥ 30.0.0&&< 32.0.1 | 32.0.1 |
| 🐍PyPI | ironic-python-agent | ≥ 27.0.0&&< 29.0.5 | 29.0.5 |
| 🐍PyPI | ironic-python-agent | all versions | 26.1.6 |
Detection & mitigation playbook
Open-source dependencyDetect
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 35.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-42997 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 CVE-2026-42997 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 CVE-2026-42997. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-42997 in your dependencies?
O3 detects CVE-2026-42997 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.