Skip to content

GO-2026-5319 CVE-2026-40243 GHSA-c839-4qxr-j4x3

Incus has an OVN TLS Verification that Accepts Peer-Supplied Roots in github.com/lxc/incus

Medium Go
Severity
0.0 / 10
Medium · CVSS 4.0
Exploit chance (EPSS)
0.17%
Chance of exploitation in the next 30 days. Higher than 6.70% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-287 Improper Authentication
CWE-295 Improper Certificate Validation
Fix
Available
2 packages have a fixed version

Description

Incus has an OVN TLS Verification that Accepts Peer-Supplied Roots in github.com/lxc/incus

Affected versions

Go

PackageVulnerableFixed in
github.com/lxc/incus
all versions
No fix yet
github.com/lxc/incus/v6
all versions
No fix yet
github.com/lxc/incus/v6/cmd/incusd
< 7.0.0
7.0.0
github.com/lxc/incus/v7
< 7.0.0
7.0.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/lxc/incus/v6/cmd/incusd Go → 7.0.0

go
go get github.com/lxc/incus/v6/cmd/incusd@v7.0.0 && go mod tidy

github.com/lxc/incus/v7 Go → 7.0.0

go
go get github.com/lxc/incus/v7@v7.0.0 && go mod tidy

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Attack vector
Adjacent
Attack complexity
High
Attack requirements
None
Privileges required
None
User interaction
None
Confidentiality (vulnerable system)
Low
Integrity (vulnerable system)
Low
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

CVSS 3.1 4.8

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Weakness

CWE-287: Improper Authentication

When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

How to prevent it
  • Architecture and Design: Use an authentication framework or library such as the OWASP ESAPI Authentication feature.

CWE-295: Improper Certificate Validation

The product does not validate, or incorrectly validates, a certificate.

How to prevent it
  • Architecture and Design, Implementation: Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner's public key.
  • Implementation: If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GO-2026-6319
Incus has a project restriction bypass in instance copy across projects
High Also affects github.com/lxc/incus
GHSA-64f3-v33m-w89f
Incus has a project restriction bypass for custom volume copy across projects
High Also affects github.com/lxc/incus
GO-2026-5806
Incus has an arbitrary file write on its client due to trusted image hash
Critical Also affects github.com/lxc/incus
GO-2026-5810
Incus: CreateCustomVolumeFromBackup nil-pointer dereference on volume_snapshots[*].expires_at (sibling-field variant of GHSA-r7w7)
Low Also affects github.com/lxc/incus
GO-2026-5808
Incus has an argument injection in backup compression algorithm leading to AFW and ACE
Critical Also affects github.com/lxc/incus
GO-2026-5800
Incus: Nil-pointer dereference in createDependentVolumesFromBackup on disk.{Volume,VolumeSnapshots,Pool}
Low Also affects github.com/lxc/incus
GO-2026-5802
Incus has an arbitrary file write via path traversal in S3 multipart upload
Critical Also affects github.com/lxc/incus
GO-2026-5803
Incus has arbitrary file read+write on host via templates/ symlink in malicious image
Critical Also affects github.com/lxc/incus
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor