{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-117613 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-117613 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-117613 is a vulnerability in Jenkins, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-117613 and fix it if it is affected.\n\nWhat it is: CVE-2026-117613 is a vulnerability in Jenkins, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-117613 in the wild and no public exploit code.\n\nAffected product: Jenkins. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-117613/ (Markdown: https://insights.sbomify.com/CVE-2026-117613/index.md)","id":"CVE-2026-117613","markdown":"https://insights.sbomify.com/CVE-2026-117613/index.md","name":"CVE-2026-117613","record":{"aliases":["GHSA-xjjc-6r4m-w362"],"analysis":null,"analysis_generated_by":null,"assigner":"jenkins","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Jenkins 2.587 and earlier, LTS 2.580.1 and earlier does not restrict item types in collections after deserialization, allowing attackers with access to POST config.xml API endpoints to submit crafted `config.xml` files that can lead to, e.g., stored cross-site scripting (XSS) vulnerabilities.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Jenkins 2.587 and earlier, LTS 2.580.1 and earlier does not restrict item types in collections after deserialization, allowing attackers wit","id":"CVE-2026-117613","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Jenkins 2.587 and earlier, LTS 2.580.1 and earlier converts the launch commands in older agent configurations into launchers provided by the","id":"CVE-2026-117614"},"packages":[],"prev":{"headline":"Jenkins 2.587 and earlier, LTS 2.580.1 and earlier does not apply its deserialization filter to classes referenced by the `resolves-to` attr","id":"CVE-2026-117612"},"products":["Jenkins"],"published":"2026-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-28","vendors":["Jenkins Project"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-117613/"}