Jenkins Git server Plugin does not perform a permission check

Exploitation

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

CVSS

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

EPSS

• CVE-2024-34146: 0.52% estimated exploitation activity in the next 30 days; percentile 44.33 (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 114.v068ac7cc2574 and earlier does not perform a permission check for read access to a Git repository over SSH. This allows attackers with a previously configured SSH public key but lacking Overall/Read permission to access Git repositories. Git server Plugin 117.veb68868fa027 requires Overall/Read permission to access Git repositories over SSH.

Published by the source

2 May 2024, 15:30 UTC

Last modified by the source

3 Jul 2024, 20:10 UTC

Source last checked

26 Oct 2026, 16:30 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xh9c-vcf9-h94m

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

# Patch Next advisory brief: CVE-2024-34146

Advisory: Jenkins Git server Plugin does not perform a permission check
IDs: CVE-2024-34146, GHSA-xh9c-vcf9-h94m
Record: https://patchnext.com/advisories/cve-2024-34146 (revision 1, source checked 26 Oct 2026, 16:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
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 117.veb. A vendor fix does not mean a deployment is fixed.

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

## 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-xh9c-vcf9-h94m (GitHub-reviewed advisory GHSA-xh9c-vcf9-h94m lists affected ranges: Maven org.jenkins-ci.plugins:git-server >=0 <117.veb)

Commands are suggestions: review each one before running it.