How severe is GHSA-453r-g2pg-cxxq?

GHSA-453r-g2pg-cxxq has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-453r-g2pg-cxxq?

GHSA-453r-g2pg-cxxq affects the following packages: github.com/lxc/incus/v6/cmd/incus (Go). Ecosystems affected: Go.

How do I fix GHSA-453r-g2pg-cxxq?

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 GHSA-453r-g2pg-cxxq is resolved across your whole dependency graph.

How do I detect GHSA-453r-g2pg-cxxq in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/lxc/incus/v6/cmd/incus. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-453r-g2pg-cxxq if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-453r-g2pg-cxxq?

O3 pinpoints whether GHSA-453r-g2pg-cxxq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-453r-g2pg-cxxq actively exploited in the wild?

No public exploit code has been indexed for GHSA-453r-g2pg-cxxq yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-453r-g2pg-cxxq?

GHSA-453r-g2pg-cxxq has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 26th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-453r-g2pg-cxxq?

GHSA-453r-g2pg-cxxq is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-453r-g2pg-cxxq published, and has it been updated?

GHSA-453r-g2pg-cxxq was published on March 27, 2026 and was last updated on April 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-453r-g2pg-cxxq

HIGH

Local Incus UI web server vulnerable to nuthentication bypass

Also known asCVE-2026-33898GO-2026-4879

Published

Mar 27, 2026

Updated

Apr 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk26th percentile+0.33%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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

Summary

The web server spawned by incus webui incorrectly validates the authentication token such that an invalid value will be accepted.

Details

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.

Credit

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/lxc/incus/v6/cmd/incus`	all versions	6.23.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/lxc/incus/v6/cmd/incus. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-453r-g2pg-cxxq is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-453r-g2pg-cxxq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-453r-g2pg-cxxq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary The web server spawned by `incus webui` incorrectly validates the authentication token such that an invalid value will be accepted. ### Details `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

O3 Security · Impact-Aware SCA

Is GHSA-453r-g2pg-cxxq in your dependencies?

O3 detects GHSA-453r-g2pg-cxxq across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works