NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2024-43044 — remoting

HIGHFix: jenkinsci/jenkins@3f54c41

CVE-2024-43044 is a high-severity (CVSS 8.8) CWE-754 vulnerability in org.jenkins-ci.main:remoting. 6 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.jenkins-ci.main:remoting — see the affected versions and patch details below.

Jenkins Remoting library arbitrary file read vulnerability

Also known asBIT-jenkins-2024-43044GHSA-h856-ffvv-xvr4
Published
Updated
Affected
6 pkgs
Patched
6 / 6
Exploits
6 known
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-43044.

EPSS Exploitation Probability

via FIRST.org ↗
28.8%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk
17.6%37.4%57.2%77.0%65.9%28.8%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

6 pkgs affected
☕org.jenkins-ci.main:remoting☕org.jenkins-ci.main:remoting☕org.jenkins-ci.main:remoting☕org.jenkins-ci.main:jenkins-core☕org.jenkins-ci.main:jenkins-core☕org.jenkins-ci.main:jenkins-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.v88a_f6e922152 and earlier, except 3206.3208.v409508a_675ff and 3248.3250.v3277a_8e88c9b_, 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 the controller does not restrict paths that agents could request to read from the controller file system.

This allows agent processes, code running on agents, and attackers with Agent/Connect permission to read arbitrary files from the Jenkins controller file system.

The Remoting library in Jenkins 2.471, LTS 2.452.4, LTS 2.462.1 now sends jar file contents with Channel#preloadJar requests, the only use case of ClassLoaderProxy#fetchJar in agents, so that agents do not need to request jar file contents from controllers anymore.

To retain compatibility with older versions of Remoting in combination with the plugins listed above, ClassLoaderProxy#fetchJar is retained and otherwise unused, just deprecated. Its implementation in Jenkins 2.471, LTS 2.452.4, LTS 2.462.1 was changed so that it is now limited to retrieving jar files referenced in the core classloader or any plugin classloader.

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.jenkins-ci.main:remotingall versions3206.3208org.jenkins-ci.main:remoting:3206.3208
☕Mavenorg.jenkins-ci.main:remoting≥ 3248&&< 3248.32503248.3250org.jenkins-ci.main:remoting:3248.3250
☕Mavenorg.jenkins-ci.main:remoting≥ 3256&&< 3256.32583256.3258org.jenkins-ci.main:remoting:3256.3258
☕Mavenorg.jenkins-ci.main:jenkins-coreall versions2.452.4org.jenkins-ci.main:jenkins-core:2.452.4
☕Mavenorg.jenkins-ci.main:jenkins-core≥ 2.460&&< 2.462.12.462.1org.jenkins-ci.main:jenkins-core:2.462.1
☕Mavenorg.jenkins-ci.main:jenkins-core≥ 2.470&&< 2.4712.471org.jenkins-ci.main:jenkins-core:2.471

Affected Products

1 product · 2 configurations
Application
jenkinsjenkins
< 2.471
range
Exploits & PoCs
6

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Jenkins 2.470 and earlier, LTS 2.452.3 and earlier allows agent processe…

github.comGithubAug 2024

Report on github.com

github.comGithubAug 2024

Report on github.com

github.comGithubAug 2024

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.main:remoting, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.jenkins-ci.main:remoting to 3206.3208 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-43044 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatCritical

This vulnerability is classified as critical because it could allow remote code execution (RCE). Additionally, this vulnerability may enable an attacker to read arbitrary files from the Jenkins controller, resulting in a significant exposure of confidential information, compromising the overall integrity of the…

Workaround published by Red Hat
Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.
Source: Red Hat security advisory for CVE-2024-43044 (CC BY 4.0)
ProductFixed inAdvisory
OCP-Tools-4.12-RHEL-8jenkins-0:2.462.1.1723550696-3.el8RHSA-2024:5410
OCP-Tools-4.13-RHEL-8jenkins-0:2.462.1.1723445923-3.el8RHSA-2024:5406
OCP-Tools-4.14-RHEL-8jenkins-0:2.462.1.1723225151-3.el8RHSA-2024:5411
OCP-Tools-4.15-RHEL-8jenkins-0:2.462.1.1723440104-3.el8RHSA-2024:5405

Frequently Asked Questions

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: bounc
O3 Security · Impact-Aware SCA

Is CVE-2024-43044 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2024-43044: remoting — Fixed in 3206.3208