What is CVE-2016-5363?

CVE-2016-5363 is a high-severity security vulnerability in neutron (pip), affecting versions <= 7.0.4. It is fixed in 7.1.0, 8.1.0.

How severe is CVE-2016-5363?

CVE-2016-5363 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of neutron are affected by CVE-2016-5363?

neutron (pip) versions <= 7.0.4 is affected.

Is there a fix for CVE-2016-5363?

Yes. CVE-2016-5363 is fixed in 7.1.0, 8.1.0. Upgrade to this version or later.

Is CVE-2016-5363 exploitable, and should I be worried?

Whether CVE-2016-5363 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2016-5363 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2016-5363?

Upgrade: neutron to 7.1.0 or later, neutron to 8.1.0 or later.

CVE-2016-5363 in neutron

Q: How severe is CVE-2016-5363?

CVE-2016-5363 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of neutron are affected by CVE-2016-5363?

neutron (pip) versions <= 7.0.4 is affected.

Q: Is there a fix for CVE-2016-5363?

Yes. CVE-2016-5363 is fixed in 7.1.0, 8.1.0. Upgrade to this version or later.

Q: Is CVE-2016-5363 exploitable, and should I be worried?

Whether CVE-2016-5363 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2016-5363 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2016-5363?

Upgrade: neutron to 7.1.0 or later, neutron to 8.1.0 or later.

Summary

OpenStack Neutron Intended MAC-spoofing protection mechanism bypass

The IPTables firewall in OpenStack Neutron up to 7.0.4 and 8.x before 8.1.0 allows remote attackers to bypass an intended MAC-spoofing protection mechanism and consequently cause a denial of service or intercept network traffic via (1) a crafted DHCP discovery message or (2) crafted non-IP traffic.

Impact

CVE-2016-5363 has a CVSS score of 8.2 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (7.1.0, 8.1.0); upgrading removes the vulnerable code path.

Affected versions

neutron (<= 7.0.4) neutron (>= 8.0.0, < 8.1.0)

Security releases

neutron → 7.1.0 (pip) neutron → 8.1.0 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

neutron to 7.1.0 or later; neutron to 8.1.0 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2016-5363? CVE-2016-5363 is a high-severity security vulnerability in neutron (pip), affecting versions <= 7.0.4. It is fixed in 7.1.0, 8.1.0.
How severe is CVE-2016-5363? CVE-2016-5363 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of neutron are affected by CVE-2016-5363? neutron (pip) versions <= 7.0.4 is affected.
Is there a fix for CVE-2016-5363? Yes. CVE-2016-5363 is fixed in 7.1.0, 8.1.0. Upgrade to this version or later.
Is CVE-2016-5363 exploitable, and should I be worried? Whether CVE-2016-5363 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2016-5363 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2016-5363?
- Upgrade neutron to 7.1.0 or later
- Upgrade neutron to 8.1.0 or later

Other vulnerabilities in neutron

CVE-IDSeverityPackage summary

CVE-2026-49299Mediumneutron: OpenStack Neutron has an Incorrect Authorization issue CVE-2024-53916Mediumneutron: OpenStack Neutron can use an incorrect ID during policy enforcement CVE-2023-3637Mediumneutron: Denial of service in neutron CVE-2022-3277Mediumneutron: openstack-neutron uncontrolled resource consumption flaw CVE-2021-40797Highneutron: OpenStack Neutron Denial of Service vulnerability