NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

CVE-2026-33898 — incus

HIGHFix: lxc/incus@d81d49e

CVE-2026-33898 is a high-severity (CVSS 8.8) Improper Authentication vulnerability in github.com/lxc/incus/v6/cmd/incus. A fix is available for github.com/lxc/incus/v6/cmd/incus — see the affected versions and patch details below.

Local Incus UI web server vulnerable to nuthentication bypass

Also known asGHSA-453r-g2pg-cxxqGO-2026-4879
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-33898.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs29th percentile — riskier than 29% of all scored CVEsHighest risk
0.00%0.33%0.66%0.98%0.0%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐹github.com/lxc/incus/v6/cmd/incus

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Incus is a system container and virtual machine manager. Prior to version 6.23.0, the web server spawned by incus webui incorrectly validates the authentication token such that an invalid value will be accepted. incus webui runs a local web server on a random localhost port. For authentication, it provides the user with a URL containing an authentication token. When accessed with that token, Incus creates a cookie persisting that token without needing to include it in subsequent HTTP requests. While the Incus client correctly validates the value of the cookie, it does not correctly validate the token when passed int the URL. This allows for an attacker able to locate and talk to the temporary web server on localhost to have as much access to Incus as the user who ran incus webui. This can lead to privilege escalation by another local user or an access to the user's Incus instances and possibly system resources by a remote attack able to trick the local user into interacting with the Incus UI web server. Version 6.23.0 patches the issue.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/lxc/incus/v6/cmd/incusall versions6.23.0go get github.com/lxc/incus/v6/cmd/incus@v6.23.0

Affected Products

1 product · 1 configurations
Application
incuslinuxcontainers
< 6.23.0
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/lxc/incus/v6/cmd/incus, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/lxc/incus/v6/cmd/incus to 6.23.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-33898 is resolved across your whole dependency graph.

  3. Workarounds

    Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Important: This flaw in the `incus webui` component allows for privilege escalation and unauthorized access. The vulnerability arises from improper authentication token validation when tokens are passed in the URL, enabling a local attacker or a remote attacker (via user interaction) to gain access to Incus instances…

Workaround published by Red Hat
To mitigate this issue, avoid running the `incus webui` command if the web interface functionality is not required. The `incus webui` component spawns a local web server, and refraining from its use eliminates the attack vector. If `incus webui` must be used, ensure that only trusted users have access to the system where it is run and exercise caution with any remote interactions that might trick a local user into accessing the Incus UI web server.
Source: Red Hat security advisory for CVE-2026-33898 (CC BY 4.0)

Frequently Asked Questions

Incus is a system container and virtual machine manager. Prior to version 6.23.0, the web server spawned by `incus webui` incorrectly validates the authentication token such that an invalid value will be accepted. `incus webui` runs a local web server on a random localhost port. For authentication, it provides the user with a URL containing an authentication token. When accessed with that token, Incus creates a cookie persisting that token without needing to include it in subsequent HTTP requests. While the Incus client correctly validates the value of the cookie, it does not correctly validat
O3 Security · Impact-Aware SCA

Is CVE-2026-33898 in your dependencies?

Find it across Go, including transitive dependencies.

CVE-2026-33898: incus PrivEsc — Fixed in 6.23.0