OpenStack Nova Filter Scheduler Bypass

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

EPSS

• CVE-2017-16239: 1.42% estimated exploitation activity in the next 30 days; percentile 72.88 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

In OpenStack Nova through 14.0.9, 15.x through 15.0.7, and 16.x through 16.0.2, by rebuilding an instance, an authenticated user may be able to circumvent the Filter Scheduler bypassing imposed filters (for example, the ImagePropertiesFilter or the IsolatedHostsFilter). All setups using Nova Filter Scheduler are affected. Because of the regression described in Launchpad Bug #1732947, the preferred fix is a 14.x version after 14.0.10, a 15.x version after 15.0.8, or a 16.x version after 16.0.3.

Published by the source

13 May 2022, 01:44 UTC

Last modified by the source

6 Jul 2026, 08:11 UTC

Source last checked

26 Oct 2026, 13:13 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-w2wf-cgwh-vpqg

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-w2wf-cgwh-vpqg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2017-16239

Advisory: OpenStack Nova Filter Scheduler Bypass
IDs: CVE-2017-16239, GHSA-w2wf-cgwh-vpqg
Record: https://patchnext.com/advisories/cve-2017-16239 (revision 2, source checked 26 Oct 2026, 13:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nova 16.0.3, 15.0.8, 14.0.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI nova: affected >= 16.0.0, < 16.0.3; >= 15.0.0, < 15.0.8; >= 14.0.0, < 14.0.10; fixed in 16.0.3, 15.0.8, 14.0.10

## Suggested inspection (read-only)
- `python -m pip show nova`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nova.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-w2wf-cgwh-vpqg (OSV record GHSA-w2wf-cgwh-vpqg lists affected ranges: PyPI nova >=16.0.0 =15.0.0 =14.0.0 <14.0.10 (fixed))
- Verified: https://github.com/advisories/GHSA-w2wf-cgwh-vpqg (GitHub-reviewed advisory GHSA-w2wf-cgwh-vpqg lists affected ranges: PyPI nova >=16.0.0 =15.0.0 =14.0.0 <14.0.10)

Commands are suggestions: review each one before running it.