Jenkins Remoting library arbitrary file read vulnerability
CVE-2024-43044GHSA-h856-ffvv-xvr4
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.jenkins-ci.main:jenkins-core 2.471, 2.462.1, 2.452.4; org.jenkins-ci.main:remoting 3256.3258, 3248.3250, 3206.3208), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.jenkins-ci.main:jenkins-core
- Affected
- < 2.452.4>= 2.460, < 2.462.1>= 2.470, < 2.471
- Fixed in
- 2.452.4, 2.471, 2.462.1
Maven org.jenkins-ci.main:remoting
- Affected
- < 3206.3208>= 3248, < 3248.3250>= 3256, < 3256.3258
- Fixed in
- 3206.3208, 3248.3250, 3256.3258
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-h856-ffvv-xvr4 lists affected ranges: Maven org.jenkins-ci.main:remoting >=0 =3248 =3256 =0 =2.460 =2.470 <2.471
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 7.1 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H · score source
- EPSS
- CVE-2024-43044: 28.78% estimated exploitation activity in the next 30 days; percentile 98.15 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Jenkins uses the Remoting library (typically agent.jar or remoting.jar) for the communication between controller and agents. This library allows agents to load classes and classloader resources from the controller, so that Java objects sent from the controller (build steps, etc.) can be executed on agents. In addition to individual class and resource files, Remoting also allows Jenkins plugins to transmit entire jar files to agents using the Channel#preloadJar API. As of publication of this advisory, this feature is used by the following plugins distributed by the Jenkins project: bouncycastle API, Groovy, Ivy, TeamConcert In Remoting 3256.v88af6e922152 and earlier, except 3206.3208.v409508a675ff and 3248.3250.v3277a8e88c9b, included in Jenkins 2.470 and earlier, LTS 2.452.3 and earlier, calls to Channel#preloadJar result in the retrieval of files from the controller by the agent using ClassLoaderProxy#fetchJar. Additionally, the implementation of ClassLoaderProxy#fetchJar invoked on…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-h856-ffvv-xvr4
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2024-43044 Advisory: Jenkins Remoting library arbitrary file read vulnerability IDs: CVE-2024-43044, GHSA-h856-ffvv-xvr4 Record: https://patchnext.com/advisories/cve-2024-43044 (revision 1, source checked 26 Oct 2026, 16:31 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.main:jenkins-core 2.471, 2.462.1, 2.452.4; org.jenkins-ci.main:remoting 3256.3258, 3248.3250, 3206.3208. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.jenkins-ci.main:jenkins-core: affected < 2.452.4; >= 2.460, < 2.462.1; >= 2.470, < 2.471; fixed in 2.452.4, 2.471, 2.462.1 - Maven org.jenkins-ci.main:remoting: affected < 3206.3208; >= 3248, < 3248.3250; >= 3256, < 3256.3258; fixed in 3206.3208, 3248.3250, 3256.3258 ## Suggested inspection (read-only) - Maven org.jenkins-ci.main:jenkins-core: check the installed version with your package manager. - Maven org.jenkins-ci.main:remoting: 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.main:jenkins-core, org.jenkins-ci.main:remoting. - 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-h856-ffvv-xvr4 (GitHub-reviewed advisory GHSA-h856-ffvv-xvr4 lists affected ranges: Maven org.jenkins-ci.main:remoting >=0 =3248 =3256 =0 =2.460 =2.470 <2.471) Commands are suggestions: review each one before running it.
Loading voting…