CVE-2026-115373: Incus before 6.0.7, 6.1.0 before 7.0.2, and 7.1.0 before 7.5.0 Authorization Bypass via GET /1.0/operations/{uuid}

Published Oct 22, 2026
·
Updated

Incus before 6.0.7, 6.1.0 before 7.0.2, and 7.1.0 before 7.5.0 contains a missing authorization vulnerability in GET /1.0/operations/{uuid} that lets project-restricted clients read operations in other projects. Attackers holding a restricted certificate and a known operation UUID can retrieve command lines, environment secrets, websocket secrets, and trust enrolment tokens.

Affected Software

7 affected componentsFixes available
Linux Containers Incus<6.0.7, >=6.1.0<7.0.2, >=7.1.0<7.5.0
ubuntu/incus*
ubuntu/incus*
ubuntu/incus*
debian/incus<6.0.4-2+deb13u11
6.0.4-2+deb13u11
debian/incus<7.0.1-5
7.0.1-5
debian/incus<=6.0.4-2+deb13u10
6.0.4-2+deb13u127.0.2-27.0.2-3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/incus to a version that resolves this vulnerability.

    Fixed in 6.0.4-2+deb13u11
  2. Upgrade

    Upgrade debian/incus to a version that resolves this vulnerability.

    Fixed in 7.0.1-5
  3. Upgrade

    Upgrade Incus to a version that resolves this vulnerability.

    Fixed in 6.0.7
  4. Upgrade

    Upgrade Incus to a version that resolves this vulnerability.

    Fixed in 7.0.2
  5. Upgrade

    Upgrade Incus to a version that resolves this vulnerability.

    Fixed in 7.5.0

Event History

Oct 22, 2026
CVE Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·07:13 PM
Data Sourced
via MITRE·07:13 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·07:17 PM
Affected Software
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

Which deployments are exposed?

Incus deployments running a version earlier than 6.0.7, versions from 6.1.0 earlier than 7.0.2, or versions from 7.1.0 earlier than 7.5.0 are affected. Exposure is relevant where project-restricted client certificates are issued.

2

What does an attacker need to exploit this issue?

The attacker needs a restricted certificate and the UUID of an operation in another project. No user interaction is required, but the attack complexity is high.

3

What information could be disclosed?

A successful request can disclose command lines, environment secrets, websocket secrets, and trust enrolment tokens from operations belonging to other projects.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203