Stored XSS vulnerability in Jenkins Pipeline: Supporting APIs Plugin

Exploitation

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

CVSS

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

EPSS

• CVE-2022-43409: 0.82% estimated exploitation activity in the next 30 days; percentile 57.38 (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.

Pipeline: Supporting APIs Plugin provides a feature to add hyperlinks, that send POST requests when clicked, to build logs. These links are used by Pipeline: Input Step Plugin to allow users to proceed or abort the build, or by Pipeline: Job Plugin to allow users to forcibly terminate the build after aborting it. Pipeline: Supporting APIs Plugin 838.va3a087b4055b and earlier does not sanitize or properly encode URLs of these hyperlinks in build logs. This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to create Pipelines. Pipeline: Supporting APIs Plugin 839.v35e2736cfd5c properly encodes URLs of these hyperlinks in build logs.

Published by the source

19 Oct 2022, 19:00 UTC

Last modified by the source

4 Jan 2024, 12:14 UTC

Source last checked

26 Oct 2026, 16:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-64r9-x74q-wxmh

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

# Patch Next advisory brief: CVE-2022-43409

Advisory: Stored XSS vulnerability in Jenkins Pipeline: Supporting APIs Plugin
IDs: CVE-2022-43409, GHSA-64r9-x74q-wxmh
Record: https://patchnext.com/advisories/cve-2022-43409 (revision 1, source checked 26 Oct 2026, 16:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.jenkins-ci.plugins.workflow:workflow-support 839.v35e2736cfd5c. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins.workflow:workflow-support: affected < 839.v35e2736cfd5c; fixed in 839.v35e2736cfd5c

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins.workflow:workflow-support: 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 org.jenkins-ci.plugins.workflow:workflow-support.
- 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-64r9-x74q-wxmh (GitHub-reviewed advisory GHSA-64r9-x74q-wxmh lists affected ranges: Maven org.jenkins-ci.plugins.workflow:workflow-support >=0 <839.v35e2736cfd5c)

Commands are suggestions: review each one before running it.