Jenkins Support Core Plugin allowed users with Overall/Read permission to delete arbitrary files

Exploitation

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

CVSS

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

EPSS

• CVE-2019-16540: 1.61% estimated exploitation activity in the next 30 days; percentile 75.91 (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 Support Core Plugin did not validate the paths submitted for the "Delete Support Bundles" feature. This allowed users to delete arbitrary files on the Jenkins controller file system accessible to the OS user account running Jenkins. Additionally, this endpoint did not perform a permission check, allowing users with Overall/Read permission to delete support bundles, and any arbitrary other file, with a known name/path. Support Core Plugin now only allows the deletion of support bundles and related files listed on the UI through this feature. It also ensures that only users with "Download Bundle" permission are able to delete support bundles.

Published by the source

24 May 2022, 17:01 UTC

Last modified by the source

27 Oct 2023, 16:00 UTC

Source last checked

26 Oct 2026, 16:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2cxg-448h-4wxj

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

# Patch Next advisory brief: CVE-2019-16540

Advisory: Jenkins Support Core Plugin allowed users with Overall/Read permission to delete arbitrary files
IDs: CVE-2019-16540, GHSA-2cxg-448h-4wxj
Record: https://patchnext.com/advisories/cve-2019-16540 (revision 1, source checked 26 Oct 2026, 16:15 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: org.jenkins-ci.plugins:support-core 2.64. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins:support-core: affected <= 2.63; fixed in 2.64

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins:support-core: 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:support-core.
- 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-2cxg-448h-4wxj (GitHub-reviewed advisory GHSA-2cxg-448h-4wxj lists affected ranges: Maven org.jenkins-ci.plugins:support-core >=0 <=2.63)

Commands are suggestions: review each one before running it.