Is CVE-2026-5774 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-5774 being exploited in the wild.

How severe is CVE-2026-5774?

Medium severity, with a CVSS score of 6.4, published 10 April 2026.

Which products and versions are affected?

github.com/juju/juju (Go) < 0.0.0-20260408003526-d395054dc2c3, SEMVER:introduced=0,fixed=0.0.0-20260408003526-d395054dc2c3.

Is there a fix for CVE-2026-5774?

Yes. github.com/juju/juju (Go): upgrade to 0.0.0-20260408003526-d395054dc2c3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2026-5774?

Check whether you run github.com/juju/juju (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-5774: Canonical Juju race condition in API server userTokens map

Q: Is there a fix for CVE-2026-5774?

Yes. github.com/juju/juju (Go): upgrade to 0.0.0-20260408003526-d395054dc2c3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: Am I affected by CVE-2026-5774?

Check whether you run github.com/juju/juju (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-5774 · Severity: medium · CVSS 6.4 · Published 2026-04-10

A race condition in the Canonical Juju API server's token management allows authenticated users to cause a denial of service or reuse single-use discharge tokens.

Technologies: github.com/juju/juju (Go). Vendors: Go.

Quick answers

Is CVE-2026-5774 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-5774 being exploited in the wild.
How severe is CVE-2026-5774?: Medium severity, with a CVSS score of 6.4, published 10 April 2026.
Which products and versions are affected?: github.com/juju/juju (Go) < 0.0.0-20260408003526-d395054dc2c3, SEMVER:introduced=0,fixed=0.0.0-20260408003526-d395054dc2c3.
Is there a fix for CVE-2026-5774?: Yes. github.com/juju/juju (Go): upgrade to 0.0.0-20260408003526-d395054dc2c3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-5774?: Check whether you run github.com/juju/juju (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/juju/juju (Go): upgrade to 0.0.0-20260408003526-d395054dc2c3 or later
```
go get github.com/juju/juju@v0.0.0-20260408003526-d395054dc2c3
```

Affected products

github.com/juju/juju (Go) < 0.0.0-20260408003526-d395054dc2c3, SEMVER:introduced=0,fixed=0.0.0-20260408003526-d395054dc2c3

Identifiers

CVE-2026-5774
GHSA-7m55-2hr4-pw78
GO-2026-5228

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.