{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97851 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-97851 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-97851 is a high-severity missing authorization vulnerability in J4Care dcm4chee-arc-light, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-97851 and fix it if it is affected.\n\nWhat it is: CVE-2026-97851 is a high-severity missing authorization vulnerability in J4Care dcm4chee-arc-light, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-97851 in the wild and no public exploit code.\n\nAffected product: J4Care dcm4chee-arc-light. 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-97851/ (Markdown: https://insights.sbomify.com/CVE-2026-97851/index.md)","id":"CVE-2026-97851","markdown":"https://insights.sbomify.com/CVE-2026-97851/index.md","name":"CVE-2026-97851","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"DICOM archive server","requires_auth":"none","summary":"Attackers can delete DICOM objects from storage by changing location records to deletion states without proper authorization.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The storage status-change REST service allows location records still associated with DICOM instances to be changed to deletion-related states. Changing a location to TO_DELETE causes PurgeStorageScheduler to delete the referenced object from storage even though the corresponding instance record remains in the database.","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":"J4Care dcm4che Missing Authorization","id":"CVE-2026-97851","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Unbounded allocation in decimal Decimal.round/3 driven by the places argument enables DoS","id":"CVE-2026-97853"},"packages":[],"prev":{"headline":"Keycloak-services: keycloak-services: standard token exchange v2 bypasses mtls holder-of-key binding","id":"CVE-2026-97846"},"products":["dcm4chee-arc-light"],"published":"2026-10-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["J4Care"]},"summary":"Attackers can delete DICOM objects from storage by changing location records to deletion states without proper authorization.","url":"https://insights.sbomify.com/CVE-2026-97851/"}