CVE-2026-97851

waiting for further signalsZero needs more public information before it can validate it.

EUVD-2026-102890 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
J4Care dcm4chee-arc-light 5.35.1
CWE-862 Missing Authorization
ETK-2026-1781Zero's internal tracking ID, independent of the CVE number., permanent identifier
5d 02h 45msince last run
17mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h56m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

dcm4chee-arc-light's storage status-change REST service can allow location records linked to DICOM instances to be moved to deletion-related states. An attacker with access to that service can trigger removal of referenced stored objects while the corresponding instance records remain in the database.

mitigation

Restrict access to the storage status-change REST service to trusted, authorized administrators and networks. Prevent untrusted users or systems from changing location status until a vendor fix is available.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.32%23rd percentile
agent run time
17m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 14:16Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-16 14:16Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-97851

{
  "etk_id": "ETK-2026-1781",
  "cve_id": "CVE-2026-97851",
  "display_id": "CVE-2026-97851",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-102890",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authorization in dcm4chee-arc-light storage status service",
  "summary": "dcm4chee-arc-light's storage status-change REST service can allow location records linked to DICOM instances to be moved to deletion-related states. An attacker with access to that service can trigger removal of referenced stored objects while the corresponding instance records remain in the database.",
  "mitigation": "Restrict access to the storage status-change REST service to trusted, authorized administrators and networks. Prevent untrusted users or systems from changing location status until a vendor fix is available.",
  "vendor": "J4Care",
  "product": "dcm4chee-arc-light",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "5.35.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "dcm4chee-arc-light",
      "purl": null
    }
  ],
  "cwes": [
    862
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_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",
  "epss_score": 0.0032,
  "epss_percentile": 0.2326,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 17.19877393333333,
  "t0_at": "2026-10-16T14:16:55.229000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-16T14:16:55.229000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T14:16:55.229000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-97851"
    }
  }
}

published 2026-10-16 14:55Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.