CVE-2026-130778

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

EUVD-2026-129123 ↗

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 < v7.6.0
fixed in >= v7.6.0
CWE-287 Improper Authentication
ETK-2026-4853Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:golang/github.com/lxc/incus/v7/cmd/incusd
1h 45msince last run
54mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h02m
0
+2h
+6h
+8h
+10h
+12h

description

Incus versions before 7.6.0 incorrectly validate TLS client certificate chains. A remote attacker able to connect to the service may be treated as a trusted certificate identity, potentially obtaining cluster-level access and changing authorization-related settings.

mitigation

Upgrade Incus to version 7.6.0 or later. Restrict network access to the Incus API until the update is complete.

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.
–
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.
–
agent run time
54m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-18 19:02Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-11-18 19:02Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4853",
  "cve_id": "CVE-2026-130778",
  "display_id": "CVE-2026-130778",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-129123",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Certificate-chain authentication bypass in Incus",
  "summary": "Incus versions before 7.6.0 incorrectly validate TLS client certificate chains. A remote attacker able to connect to the service may be treated as a trusted certificate identity, potentially obtaining cluster-level access and changing authorization-related settings.",
  "mitigation": "Upgrade Incus to version 7.6.0 or later. Restrict network access to the Incus API until the update is complete.",
  "vendor": "lxc",
  "product": "incus",
  "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": [
    287
  ],
  "cvss_score": 10,
  "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:H/SI:H/SA:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 54.32963715,
  "t0_at": "2026-11-18T19:02:47.802000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-18T19:02:47.802000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T19:02:47.802000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-130778"
    }
  }
}

published 2026-11-18 22:10Z
last change 2026-11-18 23:58Z

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.