CVE-2026-115375

validatingZero is analyzing and reversing it now.

GHSA-f963-f2v2-v6x5 ↗EUVD-2026-108298 ↗

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.
lxc incus >= 7.0.0, < 7.0.2; >= 7.1.0, < 7.5.0
fixed in 7.0.2, 7.5.0
ETK-2026-2512Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Incus versions 7.0.0 through 7.0.1 and 7.1.0 through 7.4.x mishandle volume names supplied in instance backup metadata. An attacker with permission to create instances may import a malicious backup and cause files or directories to be written on the host, potentially resulting in host compromise.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade the 7.0 release line to Incus 7.0.2 or later, or the 7.1 release line to Incus 7.5.0 or later. Until upgraded, restrict instance-creation and backup-import permissions to trusted administrators.

fixed in 7.0.2, 7.5.0

check
building now
exploit
not yet
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.
–
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
–
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

Run in progress: no artifact yet.

source signals

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

  1. 2026-10-22 19:13Z
    ghsa: trigger signal, started the run
  2. 2026-10-22 19:13Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2512",
  "cve_id": "CVE-2026-115375",
  "display_id": "CVE-2026-115375",
  "ghsa_id": "GHSA-f963-f2v2-v6x5",
  "euvd_id": "EUVD-2026-108298",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Path traversal in Incus instance backup imports",
  "summary": "Incus versions 7.0.0 through 7.0.1 and 7.1.0 through 7.4.x mishandle volume names supplied in instance backup metadata. An attacker with permission to create instances may import a malicious backup and cause files or directories to be written on the host, potentially resulting in host compromise.",
  "mitigation": "Upgrade the 7.0 release line to Incus 7.0.2 or later, or the 7.1 release line to Incus 7.5.0 or later. Until upgraded, restrict instance-creation and backup-import permissions to trusted administrators.",
  "vendor": "lxc",
  "product": "incus",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 7.0.0, < 7.0.2",
        ">= 7.1.0, < 7.5.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "7.0.2",
        "7.5.0"
      ],
      "package_name": "incus",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-10-22T19:13:44.760000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T19:13:44.760000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T19:13:44.760000+00:00",
      "url": "https://github.com/advisories/GHSA-f963-f2v2-v6x5"
    }
  }
}

published 2026-10-22 21:52Z
last change 2026-10-22 22:41Z

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.