ETK-2026-3034Zero's internal tracking ID, independent of the CVE number.

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

GHSA-p45f-gqqj-6qq3 ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
go:github.com/lxc/incus/v7/cmd/incusd < v7.6.0
fixed in >= v7.6.0
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
ETK-2026-3034Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:golang/github.com/lxc/incus/v7/cmd/incusd
3h 48msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+6h16m
0
+2h
+4h
+8h
+10h

description

Incus daemon releases before v7.6.0 insufficiently validate snapshot names during custom volume backup import. A user authorized to import custom volumes can cause later volume actions to operate on host paths outside the intended storage pool. Exploitation requires custom-volume import access.

mitigation

Upgrade github.com/lxc/incus/v7/cmd/incusd to >= v7.6.0 or later.

fixed in >= v7.6.0

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-29 22:17Z

this entry in the feed

GET /api/v1/feed/ETK-2026-3034

{
  "etk_id": "ETK-2026-3034",
  "cve_id": null,
  "display_id": "ETK-2026-3034",
  "ghsa_id": "GHSA-p45f-gqqj-6qq3",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Path traversal in Incus custom volume backup imports",
  "summary": "Incus daemon releases before v7.6.0 insufficiently validate snapshot names during custom volume backup import. A user authorized to import custom volumes can cause later volume actions to operate on host paths outside the intended storage pool. Exploitation requires custom-volume import access.",
  "mitigation": "Upgrade github.com/lxc/incus/v7/cmd/incusd to >= v7.6.0 or later.",
  "vendor": "go",
  "product": "go:github.com/lxc/incus/v7/cmd/incusd",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< v7.6.0"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        ">= v7.6.0"
      ],
      "package_name": "github.com/lxc/incus/v7/cmd/incusd",
      "purl": "pkg:golang/github.com/lxc/incus/v7/cmd/incusd"
    }
  ],
  "cwes": [
    22
  ],
  "cvss_score": 9.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 15.455560116666666,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-29T22:17:30+00:00",
      "days": -0.4198816360185185,
      "is_lower_bound": true,
      "measured_at": "2026-10-30T08:22:07.869230+00:00",
      "url": "https://github.com/lxc/incus/security/advisories/GHSA-p45f-gqqj-6qq3"
    }
  }
}

published 2026-10-30 04:42Z
last change 2026-10-30 08:07Z

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.