Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
CRITICAL severity

CVE-2019-10141 ironic-inspector

CRITICAL

CVE-2019-10141 is a critical-severity (CVSS 9.1) SQL Injection vulnerability in ironic-inspector. A fix is available for ironic-inspector — see the affected versions and patch details below.

Openstack ironic-inspector has SQL injection vulnerability in node_cache

Also known asGHSA-c7fc-cm7p-92r2PYSEC-2019-152
Published
Jul 30, 2019
Updated
Jul 8, 2026
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed
Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2019-10141 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

5 pkgs affected
🐍ironic-inspector🐍ironic-inspector🐍ironic-inspector🐍ironic-inspector🐍ironic-inspector

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

A vulnerability was found in openstack-ironic-inspector all versions excluding 5.0.2, 6.0.3, 7.2.4, 8.0.3 and 8.2.1. A SQL-injection vulnerability was found in openstack-ironic-inspector's node_cache.find_node(). This function makes a SQL query using unfiltered data from a server reporting inspection results (by a POST to the /v1/continue endpoint). Because the API is unauthenticated, the flaw could be exploited by an attacker with access to the network on which ironic-inspector is listening. Because of how ironic-inspector uses the query results, it is unlikely that data could be obtained. However, the attacker could pass malicious data and create a denial of service.

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIironic-inspectorall versions5.0.2pip install --upgrade 'ironic-inspector==5.0.2'
🐍PyPIironic-inspector5.1.0&&< 6.0.36.0.3pip install --upgrade 'ironic-inspector==6.0.3'
🐍PyPIironic-inspector6.1.0&&< 7.2.47.2.4pip install --upgrade 'ironic-inspector==7.2.4'
🐍PyPIironic-inspector8.0.0&&< 8.0.38.0.3pip install --upgrade 'ironic-inspector==8.0.3'
🐍PyPIironic-inspector8.1.0&&< 8.2.18.2.1pip install --upgrade 'ironic-inspector==8.2.1'

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ironic-inspector, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update ironic-inspector to 5.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10141 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2019-10141 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2019-10141. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant
ProductFixed inAdvisory
Red Hat OpenStack Platform 10.0 (Newton)openstack-ironic-inspector-0:4.2.2-6.el7ostRHSA-2019:1722
Red Hat OpenStack Platform 13.0 (Queens)openstack-ironic-inspector-0:7.2.3-3.el7ostRHSA-2019:1734
Red Hat OpenStack Platform 14.0 (Rocky)openstack-ironic-inspector-0:8.0.3-0.20190420013817.el7ostRHSA-2019:1669
Red Hat OpenStack Platform 9.0 (Mitaka) directoropenstack-ironic-inspector-0:3.2.2-5.el7ostRHSA-2019:2505

Frequently Asked Questions

A vulnerability was found in openstack-ironic-inspector all versions excluding 5.0.2, 6.0.3, 7.2.4, 8.0.3 and 8.2.1. A SQL-injection vulnerability was found in openstack-ironic-inspector's node_cache.find_node(). This function makes a SQL query using unfiltered data from a server reporting inspection results (by a POST to the /v1/continue endpoint). Because the API is unauthenticated, the flaw could be exploited by an attacker with access to the network on which ironic-inspector is listening. Because of how ironic-inspector uses the query results, it is unlikely that data could be obtained. Ho
O3 Security · Impact-Aware SCA

Is CVE-2019-10141 in your dependencies?

O3 Security finds CVE-2019-10141 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2019-10141: ironic DoS (Critical 9.1) | O3 Security