Arbitrary file read vulnerability in Git server Plugin can lead to RCE

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-2024-23899: 1.26% estimated exploitation activity in the next 30 days; percentile 69.68 (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 Git server Plugin uses the args4j library to parse command arguments and options on the Jenkins controller when processing Git commands received via SSH. This command parser has a feature that replaces an @ character followed by a file path in an argument with the file’s contents (expandAtFiles). This feature is enabled by default and Git server Plugin 99.va0826abcdfad and earlier does not disable it. This allows attackers with Overall/Read permission to read the first two lines of arbitrary files on the Jenkins controller file system using the default character encoding of the Jenkins controller process. See SECURITY-3314 for further information about the potential impact of being able to read files on the Jenkins controller, as well as the limitations for reading binary files. Note that for this issue, unlike SECURITY-3314, attackers need Overall/Read permission. Fix Description Git server Plugin 99.101.v720e86326c09 disables the command parser feature that replaces an @…

Published by the source

24 Jan 2024, 18:31 UTC

Last modified by the source

4 Jun 2025, 22:48 UTC

Source last checked

26 Oct 2026, 16:36 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-vph5-2q33-7r9h

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

# Patch Next advisory brief: CVE-2024-23899

Advisory: Arbitrary file read vulnerability in Git server Plugin can lead to RCE
IDs: CVE-2024-23899, GHSA-vph5-2q33-7r9h
Record: https://patchnext.com/advisories/cve-2024-23899 (revision 1, source checked 26 Oct 2026, 16:36 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: org.jenkins-ci.plugins:git-server 99.101.v720e86326c09. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins:git-server: affected < 99.101.v720e86326c09; fixed in 99.101.v720e86326c09

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins:git-server: 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:git-server.
- 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-vph5-2q33-7r9h (GitHub-reviewed advisory GHSA-vph5-2q33-7r9h lists affected ranges: Maven org.jenkins-ci.plugins:git-server >=0 <99.101.v720e86326c09)

Commands are suggestions: review each one before running it.