Skip to content

← Actionable
High, CVSS 7.1amended

OpenStack Mistral DoS

CVE-2018-16848GHSA-443j-6p7g-6v4w

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (mistral 10.0.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • PyPI mistral

    Affected
    < 10.0.0
    Fixed in
    10.0.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2018-16848: 1.19% estimated exploitation activity in the next 30 days; percentile 67.88 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

A Denial of Service (DoS) condition is possible in OpenStack Mistral in versions up to and including 7.0.3. Submitting a specially crafted workflow definition YAML file containing nested anchors can lead to resource exhaustion culminating in a denial of service.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-443j-6p7g-6v4w

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-443j-6p7g-6v4w

Agent brief

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

# Patch Next advisory brief: CVE-2018-16848

Advisory: OpenStack Mistral DoS
IDs: CVE-2018-16848, GHSA-443j-6p7g-6v4w
Record: https://patchnext.com/advisories/cve-2018-16848 (revision 3, source checked 26 Oct 2026, 13:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mistral 10.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI mistral: affected < 10.0.0; fixed in 10.0.0

## Suggested inspection (read-only)
- `python -m pip show mistral`: 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 mistral.
- 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-443j-6p7g-6v4w (OSV record GHSA-443j-6p7g-6v4w lists affected ranges: PyPI mistral >=0 <10.0.0 (fixed))
- Verified: https://github.com/advisories/GHSA-443j-6p7g-6v4w (GitHub-reviewed advisory GHSA-443j-6p7g-6v4w lists affected ranges: PyPI mistral >=0 <10.0.0)

Commands are suggestions: review each one before running it.

Loading voting…