CVE-2019-10876 — neutron
MEDIUMCVE-2019-10876 is a medium-severity (CVSS 6.5) vulnerability in neutron. A fix is available for neutron — see the affected versions and patch details below.
OpenStack Neutron overlapping security group rules prevents compute node network configuration
EPSS Exploitation Probability
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-10876 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
neutron🐍neutron🐍neutronReal-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 Neutron 11.x before 11.0.7, 12.x before 12.0.6, and 13.x before 13.0.3. By creating two security groups with separate/overlapping port ranges, an authenticated user may prevent Neutron from being able to configure networks on any compute nodes where those security groups are present, because of an Open vSwitch (OVS) firewall KeyError. All Neutron deployments utilizing neutron-openvswitch-agent are affected.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | neutron | ≥ 11.0.0&&< 11.0.7 | 11.0.7pip install --upgrade 'neutron==11.0.7' |
| 🐍PyPI | neutron | ≥ 12.0.0&&< 12.0.6 | 12.0.6pip install --upgrade 'neutron==12.0.6' |
| 🐍PyPI | neutron | ≥ 13.0.0&&< 13.0.3 | 13.0.3pip install --upgrade 'neutron==13.0.3' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for neutron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update neutron to 11.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10876 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2019-10876 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2019-10876. 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.
The pre-requisites for this vulnerability are not in Red Hat OpenStack prior to version 11, hence these versions are not affected.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenStack Platform 13.0 (Queens) | openstack-neutron-1:12.0.5-11.el7ost | RHSA-2019:0935 |
| Red Hat OpenStack Platform 14.0 (Rocky) | openstack-neutron-1:13.0.3-0.20190313155649.00b63be.el7ost | RHSA-2019:0879 |
Frequently Asked Questions
Is CVE-2019-10876 in your dependencies?
O3 Security finds CVE-2019-10876 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.