CVE-2026-33945: Abitrary file write through systemd-creds option

Published Mar 26, 2026
·
Updated

Summary Incus instances have an option to provide credentials to systemd in the guest. For containers, this is handled through a shared directory. An attacker can use the name of a systemd credential to escape that directory and overwrite arbitrary files on the host system.

This can in turn be used to perform local privilege escalation or cause a DoS.

Details An attacker can set a configuration key named something like systemd.credential.../../../../../../root/.bashrc to cause Incus to write outside of the credentials directory associated with the container. This makes use of the fact that the Incus syntax for such credentials is systemd.credential.XYZ where XYZ can itself contain more periods.

While it's not possible to read any data this way, it's possible to write to arbitrary files as root, enabling both privilege escalation and denial of service attacks.

Credit This issue was discovered and reported by the team at 7asecurity

Other sources

Incus is a system container and virtual machine manager. Incus instances have an option to provide credentials to systemd in the guest. For containers, this is handled through a shared directory. Prior to version 6.23.0, an attacker can set a configuration key named something like systemd.credential.../../../../../../root/.bashrc to cause Incus to write outside of the credentials directory associated with the container. This makes use of the fact that the Incus syntax for such credentials is systemd.credential.XYZ where XYZ can itself contain more periods. While it's not possible to read any data this way, it's possible to write to arbitrary files as root, enabling both privilege escalation and denial of service attacks. Version 6.23.0 fixes the issue.

MITRE

Affected Software

3 affected componentsFixes available
Linux Containers Incus<6.23.0
go/github.com/lxc/incus/v6<6.23.0
6.23.0
linuxcontainers Incus<6.23.0

Event History

Mar 26, 2026
CVE Published
via MITRE·11:27 PM
Data Sourced
via MITRE·11:27 PM
DescriptionSeverityWeakness
Mar 27, 2026
Data Sourced
via NVD·12:16 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:16 AM
Affected Software
Advisory Published
via GitHub·05:22 PM
Data Sourced
via GitHub·05:22 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-33945?

CVE-2026-33945 is classified as a high-severity vulnerability due to the potential for arbitrary file write.

2

How do I fix CVE-2026-33945?

To mitigate CVE-2026-33945, upgrade Incus to version 6.23.0 or later.

3

What systems are affected by CVE-2026-33945?

CVE-2026-33945 affects Incus versions prior to 6.23.0 on systems using systemd.

4

What kind of attacks does CVE-2026-33945 enable?

CVE-2026-33945 enables attackers to exploit arbitrary file write capabilities, potentially compromising the system.

5

Is there a workaround for CVE-2026-33945 before upgrading?

A temporary workaround for CVE-2026-33945 is to disable the systemd-creds option in Incus configurations until an upgrade can be performed.

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