CVE-2026-1237: GO-2026-4388 - Juju has broken CMR authorization in github.com/juju/juju

CVE-2026-1237 · Severity: medium · CVSS 4 · Published 2026-02-02

Juju has broken CMR authorization in github.com/juju/juju

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

Quick answers

Is CVE-2026-1237 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-1237 being exploited in the wild.
How severe is CVE-2026-1237?
Medium severity, with a CVSS score of 4, published 2 February 2026.
Which products and versions are affected?
github.com/juju/juju (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=0.0.0-20260127110037-9b1a0e53a4a4.
Is there a fix for CVE-2026-1237?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-1237?
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.

Affected products

  • github.com/juju/juju (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=0.0.0-20260127110037-9b1a0e53a4a4

Identifiers

  • CVE-2026-1237
  • GHSA-j477-6vpg-6c8x
  • GO-2026-4388

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