CVE-2026-34006

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

GHSA-8rwv-63p7-cjc6 ↗EUVD-2026-101974 ↗

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.
QNAP Systems Inc. sMedio DTCP MOVE >= 1.4.x, < 1.4.5
fixed in 1.4.5
ETK-2026-1680Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 06h 11msince last run
29mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+53h11m
0
+2h
+4h
+6h
+8h
+10h

description

sMedio DTCP MOVE before version 1.4.5 lacks authentication for a critical function. A remote attacker may be able to gain access to the system if they can reach the affected service.

mitigation

Upgrade sMedio DTCP MOVE to version 1.4.5 or later. Restrict network access to the affected service until the update is installed.

fixed in 1.4.5

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.53%43rd percentile
agent run time
29m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-15 09:30Z
Δ 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-15 09:30Z
    ghsa: trigger signal, started the run
  2. 2026-10-15 09:30Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1680",
  "cve_id": "CVE-2026-34006",
  "display_id": "CVE-2026-34006",
  "ghsa_id": "GHSA-8rwv-63p7-cjc6",
  "euvd_id": "EUVD-2026-101974",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authentication in sMedio DTCP MOVE",
  "summary": "sMedio DTCP MOVE before version 1.4.5 lacks authentication for a critical function. A remote attacker may be able to gain access to the system if they can reach the affected service.",
  "mitigation": "Upgrade sMedio DTCP MOVE to version 1.4.5 or later. Restrict network access to the affected service until the update is installed.",
  "vendor": "QNAP Systems Inc.",
  "product": "sMedio DTCP MOVE",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.4.x, < 1.4.5"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.4.5"
      ],
      "package_name": "sMedio DTCP MOVE",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
  "epss_score": 0.0053,
  "epss_percentile": 0.4397,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 28.7204928,
  "t0_at": "2026-10-15T09:30:03.388000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-15T09:30:03.388000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T09:30:03.388000+00:00",
      "url": "https://github.com/advisories/GHSA-8rwv-63p7-cjc6"
    }
  }
}

published 2026-10-15 13:16Z
last change 2026-10-21 05:31Z

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.