Skip to main content
Menu
CVEs

CVE

Incus memory exhaustion in S3 storage bucket listener

Only affects Incus before 7.6.0 with the local S3 listener for storage buckets enabled, meaning core.storage_buckets_address is set. Fixed in 7.6.0.

CVE-2026-130781EUVD-2026-129128Published Updated Summary written by a model

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 7.6.0
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. The local S3 listener for storage buckets is enabled and reachable (core.storage_buckets_address is set).

Summary

Incus before 7.6.0 contains a resource exhaustion vulnerability in the storage bucket S3 listener, which buffers entire signed request bodies in memory before verifying the signature or credential role. Attackers knowing only a valid access key, or holding a read-only credential, can send many concurrent large requests to exhaust daemon memory.

cve.now Index

25Pcve.now Index 25 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Go packages
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 32 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    The local S3 listener for storage buckets is enabled and reachable (core.storage_buckets_address is set).
  • Upgrade to a fixed version: 7.6.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130781 (Incus before 7.6.0 Memory Exhaustion via S3 Listener Pre-Authentication Buffering), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130781 (entry last updated 2026-11-18):
Affected:
- Go package github.com/lxc/incus/v7/cmd/incusd: fixed in 7.6.0
Fixed versions: 7.6.0.
Conditions (all must be true for the bug to be hit):
- The local S3 listener for storage buckets is enabled and reachable (core.storage_buckets_address is set). (source: https://github.com/lxc/incus/security/advisories/GHSA-8mgx-h4v8-xqv2)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130781 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130781 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/lxc/incus/security/advisories/GHSA-8mgx-h4v8-xqv2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130781
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130781"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · lxc/incus · Advisory GHSA-8mgx-h4v8-xqv2
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130781
RecordNVD · CVE-2026-130781

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130781

Is CVE-2026-130781 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The local S3 listener for storage buckets reads the entire request body, so large bodies are buffered in the daemon's memory before access is checked. Enough concurrent requests can exhaust that memory and cause a denial of service. A valid access key, even a read-only one, is needed to send these requests.Source: github.com

Which versions are affected by CVE-2026-130781?

github.com/lxc/incus/v7/cmd/incusd (Go): before 7.6.0.Source: cve.now feed data

Am I affected, and how do I check?

Incus versions before 7.6.0 that have the local S3 listener for storage buckets enabled and reachable, which means core.storage_buckets_address is set. Check the core.storage_buckets_address server setting and the installed Incus version to see which case applies.Source: github.com

How do I fix CVE-2026-130781?

Upgrade to Incus 7.6.0 or later, the first fixed version.Source: github.com

More CVEs