Openstack Aodh can be used to launder Keystone trusts

Exploitation

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

CVSS

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

EPSS

• CVE-2017-12440: 2.15% estimated exploitation activity in the next 30 days; percentile 82.12 (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.

Aodh as packaged in Openstack Ocata and Newton before change-ID I8fd11a7f9fe3c0ea5f9843a89686ac06713b7851 and before Pike-rc1 does not verify that trust IDs belong to the user when creating alarm action with the scheme trust+http, which allows remote authenticated users with knowledge of trust IDs where Aodh is the trustee to obtain a Keystone token and perform unspecified authenticated actions by adding an alarm action with the scheme trust+http, and providing a trust id where Aodh is the trustee.

Published by the source

13 May 2022, 01:42 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-86cv-9gpx-6hwj

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-86cv-9gpx-6hwj

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

# Patch Next advisory brief: CVE-2017-12440

Advisory: Openstack Aodh can be used to launder Keystone trusts
IDs: CVE-2017-12440, GHSA-86cv-9gpx-6hwj
Record: https://patchnext.com/advisories/cve-2017-12440 (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: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: aodh 6.0.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI aodh: affected < 6.0.1; fixed in 6.0.1

## Suggested inspection (read-only)
- `python -m pip show aodh`: 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 aodh.
- 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-86cv-9gpx-6hwj (OSV record GHSA-86cv-9gpx-6hwj lists affected ranges: PyPI aodh >=0 <6.0.1 (fixed))
- Verified: https://github.com/advisories/GHSA-86cv-9gpx-6hwj (GitHub-reviewed advisory GHSA-86cv-9gpx-6hwj lists affected ranges: PyPI aodh >=0 <6.0.1)

Commands are suggestions: review each one before running it.