CVE-2026-33897: Incus vulnerable to arbitrary file read and write through pongo templates

Published Mar 26, 2026
·
Updated

Summary Instance template files can be used to cause arbitrary read or writes as root on the host server.

Details Incus allows for pongo2 templates within instances which can be used at various times in the instance lifecycle to template files inside of the instance. This particular implementation of pongo2 within Incus allowed for file read/write but with the expectation that the pongo2 chroot feature would isolate all such access to the instance's filesystem.

This was allowed such that a template could theoretically read a file and then generate a new version of said file.

Unfortunately the chroot isolation mechanism is entirely skipped by pongo2 leading to easy access to the entire system's filesystem with root privileges.

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

Other sources

Incus is a system container and virtual machine manager. Prior to version 6.23.0, instance template files can be used to cause arbitrary read or writes as root on the host server. Incus allows for pongo2 templates within instances which can be used at various times in the instance lifecycle to template files inside of the instance. This particular implementation of pongo2 within Incus allowed for file read/write but with the expectation that the pongo2 chroot feature would isolate all such access to the instance's filesystem. This was allowed such that a template could theoretically read a file and then generate a new version of said file. Unfortunately the chroot isolation mechanism is entirely skipped by pongo2 leading to easy access to the entire system's filesystem with root privileges. Version 6.23.0 patches the issue.

MITRE

Affected Software

4 affected componentsFixes available
Canonical Incus<6.23.0
go/github.com/lxc/incus<=0.7.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·10:43 PM
Data Sourced
via MITRE·10:43 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:16 PM
DescriptionSeverityWeaknessAffected Software
Mar 27, 2026
Advisory Published
via GitHub·05:17 PM
Data Sourced
via GitHub·05:17 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-33897?

CVE-2026-33897 has a high severity due to its potential for arbitrary file read and write as root.

2

How do I fix CVE-2026-33897?

To fix CVE-2026-33897, upgrade your Incus installation to version 6.23.0 or later.

3

What versions of Incus are affected by CVE-2026-33897?

CVE-2026-33897 affects all versions of Incus prior to 6.23.0.

4

What types of systems are vulnerable with CVE-2026-33897?

Systems using Incus as a system container and virtual machine manager before version 6.23.0 are vulnerable.

5

What are the implications of CVE-2026-33897 for system security?

The implications of CVE-2026-33897 include potential unauthorized access to sensitive files and modification of system configurations.

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