How severe is CVE-2019-10141?

CVE-2019-10141 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-10141?

CVE-2019-10141 affects the following packages: ironic-inspector (PyPI), ironic-inspector (PyPI), ironic-inspector (PyPI), ironic-inspector (PyPI), ironic-inspector (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2019-10141?

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.

How do I detect CVE-2019-10141 in my PyPI dependencies?

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.

How do I mitigate CVE-2019-10141 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2019-10141 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-10141 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.

What is the EPSS score for CVE-2019-10141?

CVE-2019-10141 has an EPSS (Exploit Prediction Scoring System) score of 2.5%, placing it in the 85th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-10141?

CVE-2019-10141 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2019-10141 published, and has it been updated?

CVE-2019-10141 was published on July 30, 2019 and was last updated on October 24, 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

Not in CISA KEV

CRITICAL severity

CVE-2019-10141 — ironic-inspector

CRITICALFix: openstack/ironic-inspector@17c796b

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

Oct 24, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 4, 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 CVEs85th percentile — riskier than 85% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

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

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`ironic-inspector`	all versions	5.0.2`pip install --upgrade 'ironic-inspector==5.0.2'`
🐍PyPI	`ironic-inspector`	≥ 5.1.0&&< 6.0.3	6.0.3`pip install --upgrade 'ironic-inspector==6.0.3'`
🐍PyPI	`ironic-inspector`	≥ 6.1.0&&< 7.2.4	7.2.4`pip install --upgrade 'ironic-inspector==7.2.4'`
🐍PyPI	`ironic-inspector`	≥ 8.0.0&&< 8.0.3	8.0.3`pip install --upgrade 'ironic-inspector==8.0.3'`
🐍PyPI	`ironic-inspector`	≥ 8.1.0&&< 8.2.1	8.2.1`pip install --upgrade 'ironic-inspector==8.2.1'`

Affected Products

2 products · 9 configurations

Application

ironic-inspectoropenstack

≥ 8.1.0 && < 8.2.1

range

Application

openstackredhat

4 versions

9101314

Detection & mitigation playbook

Open-source dependency

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.
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.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

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

Product	Fixed in	Advisory
Red Hat OpenStack Platform 10.0 (Newton)	`openstack-ironic-inspector-0:4.2.2-6.el7ost`	RHSA-2019:1722
Red Hat OpenStack Platform 13.0 (Queens)	`openstack-ironic-inspector-0:7.2.3-3.el7ost`	RHSA-2019:1734
Red Hat OpenStack Platform 14.0 (Rocky)	`openstack-ironic-inspector-0:8.0.3-0.20190420013817.el7ost`	RHSA-2019:1669
Red Hat OpenStack Platform 9.0 (Mitaka) director	`openstack-ironic-inspector-0:3.2.2-5.el7ost`	RHSA-2019:2505

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-10141 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works