# Jenkins Remoting library arbitrary file read vulnerability Advisory record · `GHSA-h856-ffvv-xvr4` - **Identifiers:** `GHSA-h856-ffvv-xvr4` · `BIT-jenkins-2024-43044` · `CVE-2024-43044` - **State:** Confirmed - **Severity:** CVSS 9.0 Critical - **Critical:** Yes: CVSS 9+, CVSS 7+ and EPSS - **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html) · [CWE-754](https://cwe.mitre.org/data/definitions/754.html) - **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md) · [CWE-754](https://agentprime.io/advisories/tag/cwe-754.md) - **Published:** 7 Aug 2024 - **Updated:** 7 Aug 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 7 Aug 2024, 15:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 9.0: 9.0 or more. - CVSS score 9.0 (7.0 or more) and EPSS 0.29 (0.1 or more): a high score and a real chance of exploitation in the next 30 days. How we decide what’s critical: ## Affected packages - `org.jenkins-ci.main:remoting` (Maven): affected `<3206.3208 || >=3248, <3248.3250 || >=3256, <3256.3258`; fixed in `3206.3208`, `3248.3250`, `3256.3258` - `org.jenkins-ci.main:jenkins-core` (Maven): affected `<2.452.4 || >=2.460, <2.462.1 || >=2.470, <2.471`; fixed in `2.452.4`, `2.462.1`, `2.471` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Remoting versions before 3206.3208, from 3248 before 3248.3250, and from 3256 before 3256.3258 are affected, as are jenkins-core versions before 2.452.4, from 2.460 before 2.462.1, and from 2.470 before 2.471. An attacker with Agent/Connect permission, or code running on an agent, can read arbitrary files from the Jenkins controller file system. Upgrade jenkins-core to 2.452.4, 2.462.1, or 2.471, or Remoting to 3206.3208, 3248.3250, or 3256.3258. Written 2 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 9.0 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`, from GitHub Advisory Database - **CISA KEV:** Not listed. - **EPSS:** 0.29, the 98th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:19 UTC: First seen by agentprime - 31 Oct 2026, 14:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-h856-ffvv-xvr4) ## Sources - [GitHub Advisory Database: GHSA-h856-ffvv-xvr4](https://github.com/advisories/GHSA-h856-ffvv-xvr4) - [OSV: GHSA-h856-ffvv-xvr4](https://osv.dev/vulnerability/GHSA-h856-ffvv-xvr4) - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .