How severe is CVE-2017-7543?

CVE-2017-7543 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2017-7543?

CVE-2017-7543 affects the following packages: neutron (PyPI), neutron (PyPI), neutron (PyPI), neutron (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2017-7543?

Update neutron to 7.2.0-12.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-7543 is resolved across your whole dependency graph.

How do I detect CVE-2017-7543 in my PyPI dependencies?

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.

How do I mitigate CVE-2017-7543 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.

Is CVE-2017-7543 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-7543 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-2017-7543?

CVE-2017-7543 has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 79th 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-2017-7543?

CVE-2017-7543 is classified as CWE-362 (CWE-362). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2017-7543 published, and has it been updated?

CVE-2017-7543 was published on July 26, 2018 and was last updated on July 6, 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

MEDIUM severity

CVE-2017-7543 — neutron

MEDIUM

CVE-2017-7543 is a medium-severity (CVSS 5.9) CWE-362 vulnerability in neutron. A fix is available for neutron — see the affected versions and patch details below.

OpenStack Neutron Race Condition vulnerability

Also known asGHSA-hvxr-2fvv-c3wqPYSEC-2026-686

Published

Jul 26, 2018

Updated

Jul 6, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs79th percentile — riskier than 79% 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

4 pkgs affected

🐍neutron🐍neutron🐍neutron🐍neutron

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 race-condition flaw was discovered in openstack-neutron before 7.2.0-12.1, 8.x before 8.3.0-11.1, 9.x before 9.3.1-2.1, and 10.x before 10.0.2-1.1, where, following a minor overcloud update, neutron security groups were disabled. Specifically, the following were reset to 0: net.bridge.bridge-nf-call-ip6tables and net.bridge.bridge-nf-call-iptables. The race was only triggered by an update, at which point an attacker could access exposed tenant VMs and network resources.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`neutron`	all versions	7.2.0-12.1`pip install --upgrade 'neutron==7.2.0-12.1'`
🐍PyPI	`neutron`	≥ 8.0.0&&< 8.3.0-11.1	8.3.0-11.1`pip install --upgrade 'neutron==8.3.0-11.1'`
🐍PyPI	`neutron`	≥ 9.0.0&&< 9.3.1-2.1	9.3.1-2.1`pip install --upgrade 'neutron==9.3.1-2.1'`
🐍PyPI	`neutron`	≥ 10.0.0&&< 10.0.2-1.1	10.0.2-1.1`pip install --upgrade 'neutron==10.0.2-1.1'`

Affected Products

2 products · 10 configurations

Application

neutronopenstack

≥ 10.0.0 && < 10.0.2-1.1

range

Application

openstackredhat

6 versions

6.07.0891011

Detection & mitigation playbook

Open-source dependency

Detect
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 7.2.0-12.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-7543 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.

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

Workaround published by Red Hat

To determine whether your system is impacted, run: $ sudo sysctl net.bridge.bridge-nf-call-ip6tables $ sudo sysctl net.bridge.bridge-nf-call-iptables Both should be set to 1 To reset security groups to '1': 1. Apply the following configuration modification: $ sudo sed -i.back -e 's/reapply_sysctl = 0/reapply_sysctl = 1/' /etc/tuned/tuned-main.conf 2. Ensure the modification was successful: $ grep reapply_sysctl /etc/tuned/tuned-main.conf should be "reapply_sysctl = 1" 3. Check whether tuned is running: $ sudo systemctl status tuned 4. Restart tuned to apply the new configuration: $ sudo systemctl restart tuned 5. Recheck your security groups and the status of 'reapply_sysctl'.

Source: Red Hat security advisory for CVE-2017-7543 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Enterprise Linux OpenStack Platform 6.0 (Juno) for RHEL 7	`openstack-neutron-0:2014.2.3-42.el7ost`	RHSA-2017:2452
Red Hat Enterprise Linux OpenStack Platform 7.0 (Kilo) for RHEL 7	`openstack-neutron-0:2015.1.4-16.1.el7ost`	RHSA-2017:2450
Red Hat OpenStack Platform 10.0 (Newton)	`openstack-neutron-1:9.3.1-2.1.el7ost`	RHSA-2017:2448
Red Hat OpenStack Platform 11.0 (Ocata)	`openstack-neutron-1:10.0.2-1.1.el7ost`	RHSA-2017:2449
Red Hat OpenStack Platform 8.0 (Liberty)	`openstack-neutron-1:7.2.0-12.1.el7ost`	RHSA-2017:2451
Red Hat OpenStack Platform 9.0 (Mitaka)	`openstack-neutron-1:8.3.0-11.1.el7ost`	RHSA-2017:2447

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-7543 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works