{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-22155 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-22155 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-22155 is a vulnerability."},"fix_prompt":"Check this codebase for CVE-2025-22155 and fix it if it is affected.\n\nWhat it is: CVE-2025-22155 is a vulnerability. \nExploitation: There is no known exploitation of CVE-2025-22155 in the wild and no public exploit code.\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-2025-22155/ (Markdown: https://insights.sbomify.com/CVE-2025-22155/index.md)","id":"CVE-2025-22155","markdown":"https://insights.sbomify.com/CVE-2025-22155/index.md","name":"CVE-2025-22155","record":{"aliases":["GHSA-v6h4-h294-v39r"],"analysis":null,"analysis_generated_by":null,"assigner":"atlassian","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.","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":"To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.","id":"CVE-2025-22155","indexable":false,"kev":null,"kind":"cve_rejected","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2025"},"n_packages":0,"n_references":0,"next":{"headline":"This High severity PrivEsc (Privilege Escalation) vulnerability was introduced in versions: 9.12.0, 10.3.0, 10.4.0, and 10.5.0 of Jira Core","id":"CVE-2025-22157"},"packages":[],"prev":{"headline":"To maintain compliance with CNA rules, we have rejected this CVE record because it has not been used.","id":"CVE-2025-22154"},"products":[],"published":null,"related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"REJECTED","updated":"2026-01-01","vendors":[]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-22155/"}