Jenkins File Parameter Plugin arbitrary file write vulnerability

Exploitation

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

CVSS

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

EPSS

• CVE-2023-32986: 60.68% estimated exploitation activity in the next 30 days; percentile 99.15 (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.

Jenkins File Parameter Plugin 285.v757c5b67ac25 and earlier does not restrict the name (and resulting uploaded file name) of Stashed File Parameters. This allows attackers with Item/Configure permission to create or replace arbitrary files on the Jenkins controller file system with attacker-specified content. File Parameter Plugin 285.287.v4b7b29d3469d restricts the name (and resulting uploaded file name) of Stashed File Parameters.

Published by the source

16 May 2023, 18:30 UTC

Last modified by the source

4 Jan 2024, 12:12 UTC

Source last checked

26 Oct 2026, 16:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-46f2-x6h2-x9hx

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

# Patch Next advisory brief: CVE-2023-32986

Advisory: Jenkins File Parameter Plugin arbitrary file write vulnerability
IDs: CVE-2023-32986, GHSA-46f2-x6h2-x9hx
Record: https://patchnext.com/advisories/cve-2023-32986 (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.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.jenkins.plugins:file-parameters 285.287.v4b. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.jenkins.plugins:file-parameters: affected < 285.287.v4b; fixed in 285.287.v4b

## Suggested inspection (read-only)
- Maven io.jenkins.plugins:file-parameters: 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 io.jenkins.plugins:file-parameters.
- 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-46f2-x6h2-x9hx (GitHub-reviewed advisory GHSA-46f2-x6h2-x9hx lists affected ranges: Maven io.jenkins.plugins:file-parameters >=0 <285.287.v4b)

Commands are suggestions: review each one before running it.