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

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

GHSA-8r3h-vc36-6xpx ↗

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-863 Incorrect Authorization
ETK-2026-3039Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:golang/github.com/lxc/incus/v7/cmd/incusd
3h 25msince last run
7mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+5h40m
0
+2h
+4h
+8h
+10h

description

Incus versions before v7.6.0 may allow restricted-certificate clients to read named resources in the default project despite lacking an inheriting project relationship. In affected access paths, viewers may also export custom volume or bucket backups, exposing stored data or credentials when they know the resource name.

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
7m
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:18Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3039",
  "cve_id": null,
  "display_id": "ETK-2026-3039",
  "ghsa_id": "GHSA-8r3h-vc36-6xpx",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Cross-project authorization flaw in Incus default-project access",
  "summary": "Incus versions before v7.6.0 may allow restricted-certificate clients to read named resources in the default project despite lacking an inheriting project relationship. In affected access paths, viewers may also export custom volume or bucket backups, exposing stored data or credentials when they know the resource name.",
  "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": [
    863
  ],
  "cvss_score": 7.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 7.277808716666667,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-29T22:18:13+00:00",
      "days": -0.37894674150462965,
      "is_lower_bound": true,
      "measured_at": "2026-10-30T07:23:54.069085+00:00",
      "url": "https://github.com/lxc/incus/security/advisories/GHSA-8r3h-vc36-6xpx"
    }
  }
}

published 2026-10-30 05:14Z
last change 2026-10-30 07:21Z

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.