Deis Workflow Manager race condition vulnerability

Exploitation

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

CVSS

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

EPSS

• CVE-2016-15036: 0.40% estimated exploitation activity in the next 30 days; percentile 34.20 (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.

UNSUPPORTED WHEN ASSIGNED A vulnerability was found in Deis Workflow Manager up to 2.3.2. It has been classified as problematic. This affects an unknown part. The manipulation leads to race condition. The complexity of an attack is rather high. The exploitability is told to be difficult. Upgrading to version 2.3.3 is able to address this issue. The patch is named 31fe3bccbdde134a185752e53380330d16053f7f. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-248847. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Published by the source

23 Dec 2023, 21:30 UTC

Last modified by the source

27 Dec 2023, 15:06 UTC

Source last checked

26 Oct 2026, 15:03 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jpfp-xq3p-4h3r

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

# Patch Next advisory brief: CVE-2016-15036

Advisory: Deis Workflow Manager race condition vulnerability
IDs: CVE-2016-15036, GHSA-jpfp-xq3p-4h3r
Record: https://patchnext.com/advisories/cve-2016-15036 (revision 1, source checked 26 Oct 2026, 15:03 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/deis/workflow-manager 2.3.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/deis/workflow-manager: affected < 2.3.3; fixed in 2.3.3

## Suggested inspection (read-only)
- Go github.com/deis/workflow-manager: check the installed version with your package manager.

## 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 github.com/deis/workflow-manager.
- 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://github.com/advisories/GHSA-jpfp-xq3p-4h3r (GitHub-reviewed advisory GHSA-jpfp-xq3p-4h3r lists affected ranges: Go github.com/deis/workflow-manager >=0 <2.3.3)

Commands are suggestions: review each one before running it.