CVE-2026-115371

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

GHSA-6w4g-5qrv-grfx ↗EUVD-2026-108294 ↗

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.
go:github.com/lxc/incus/v7/cmd/incusd < v7.5.0
fixed in >= v7.5.0
CWE-522 Insufficiently Protected Credentials
ETK-2026-3038Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:golang/github.com/lxc/incus/v7/cmd/incusd
4h 19msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+178h08m
0
+2h
+4h
+6h
+8h
+10h

description

Incus incusd deployments using TLS-based authorization may disclose default-project storage bucket credentials to restricted TLS clients. A holder of a qualifying restricted certificate could use those credentials to access, change, or remove bucket objects through the S3 interface. Deployments using OpenFGA authorization are not affected.

mitigation

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

fixed in >= v7.5.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
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 19:13Z
Δ 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-22 19:13Z
  2. 2026-10-22 19:13Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3038",
  "cve_id": "CVE-2026-115371",
  "display_id": "CVE-2026-115371",
  "ghsa_id": "GHSA-6w4g-5qrv-grfx",
  "euvd_id": "EUVD-2026-108294",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Storage bucket key authorization flaw in incusd",
  "summary": "Incus incusd deployments using TLS-based authorization may disclose default-project storage bucket credentials to restricted TLS clients. A holder of a qualifying restricted certificate could use those credentials to access, change, or remove bucket objects through the S3 interface. Deployments using OpenFGA authorization are not affected.",
  "mitigation": "Upgrade github.com/lxc/incus/v7/cmd/incusd to >= v7.5.0 or later.",
  "vendor": "go",
  "product": "go:github.com/lxc/incus/v7/cmd/incusd",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< v7.5.0"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        ">= v7.5.0"
      ],
      "package_name": "github.com/lxc/incus/v7/cmd/incusd",
      "purl": "pkg:golang/github.com/lxc/incus/v7/cmd/incusd"
    }
  ],
  "cwes": [
    522
  ],
  "cvss_score": 8.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 10.501661433333334,
  "t0_at": "2026-10-22T19:13:41.898000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T19:13:41.898000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T19:13:41.898000+00:00",
      "url": "https://github.com/lxc/incus/security/advisories/GHSA-x8gj-2q73-qr6j"
    }
  }
}

published 2026-10-30 05:10Z
last change 2026-10-30 08:24Z

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.