{"answers":{"affected":"1 open source package ship an affected version, including jenkins. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-84655 in the wild and no public exploit code.","fix":"Upgrade jenkins to a fixed version for your release line: 2.568.3 or 2.580.0.","what":"CVE-2026-84655 is a medium-severity vulnerability in Jenkins Jenkins, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-84655 and fix it if it is affected.\n\nWhat it is: CVE-2026-84655 is a medium-severity vulnerability in Jenkins Jenkins, published on 2 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-84655 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- jenkins (Bitnami): affected all versions; fixed in 2.568.3, 2.580.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-84655/ (Markdown: https://insights.sbomify.com/CVE-2026-84655/index.md)","id":"CVE-2026-84655","markdown":"https://insights.sbomify.com/CVE-2026-84655/index.md","name":"CVE-2026-84655","record":{"aliases":["BIT-jenkins-2026-84655","GHSA-g8v4-mgp3-5f84","MINI-477x-3q5j-fc42","MINI-8gch-mr9w-xmxm","MINI-g92v-9qgp-95rx","MINI-mx7r-jfw3-r6mq","MINI-qq8j-vvhr-3677","MINI-x49j-qcfp-x5x7","MINI-x8vh-xj2r-f8wx"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins automation server","requires_auth":"low_privilege","summary":"Attackers can inject arbitrary fields into JSON and Python API responses by controlling map property names due to improper escaping in Jenkins.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"jenkins","vendor":"jenkins"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"Jenkins 2.579 and earlier, LTS 2.568.2 and earlier does not escape map keys when serializing objects as JSON and Python through its REST API, allowing attackers able to control map property names to inject arbitrary fields into JSON and Python API responses.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Other in Jenkins","id":"CVE-2026-84655","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"jenkins:jenkins","products":["jenkins:jenkins"],"type":"other","year":"2026"},"n_packages":1,"n_references":1,"next":{"headline":"Missing authorization in Jenkins","id":"CVE-2026-84656"},"packages":[{"ecosystem":"Bitnami","fixed":["2.568.3","2.580.0"],"introduced":["0","2.569.0"],"last_affected":[],"package":"jenkins","purl":"pkg:bitnami/jenkins","source":"BIT-jenkins-2026-84655"}],"prev":{"headline":"Business logic in Jenkins","id":"CVE-2026-84654"},"products":["Jenkins"],"published":"2026-09-02","related":[{"cvss_score":9.8,"headline":"Jenkins Command Line Interface (CLI) Path Traversal","id":"CVE-2024-23897","kev_date_added":"2024-08-19","published":"2024-01-24"},{"cvss_score":9.8,"headline":"Jenkins Stapler Web Framework Deserialization of Untrusted Data","id":"CVE-2018-1000861","kev_date_added":"2022-02-10","published":"2018-12-10"},{"cvss_score":9.8,"headline":"Jenkins Remote Code Execution","id":"CVE-2017-1000353","kev_date_added":"2025-10-02","published":"2018-01-29"},{"cvss_score":7.5,"headline":"Jenkins User Interface (UI) Information Disclosure","id":"CVE-2015-5317","kev_date_added":"2023-05-12","published":"2015-11-25"},{"cvss_score":9.8,"headline":"Multiple vulnerabilities allow bypassing path filtering of agent-to-controller access control in Jenkins","id":"CVE-2021-21690","kev_date_added":null,"published":"2021-11-04"},{"cvss_score":9.8,"headline":"Multiple vulnerabilities allow bypassing path filtering of agent-to-controller access control in Jenkins","id":"CVE-2021-21691","kev_date_added":null,"published":"2021-11-04"},{"cvss_score":9.8,"headline":"Multiple vulnerabilities allow bypassing path filtering of agent-to-controller access control in Jenkins","id":"CVE-2021-21692","kev_date_added":null,"published":"2021-11-04"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-02","vendors":["Jenkins Project"]},"summary":"Attackers can inject arbitrary fields into JSON and Python API responses by controlling map property names due to improper escaping in Jenkins.","url":"https://insights.sbomify.com/CVE-2026-84655/"}