Security readout for executives and security teams
Plain-English summary
CVE-2026-1237 affects Canonical Juju cross-model authorization. If permissions for a charm are revoked or expire, a user with database record update capability could cause Juju to continue accepting invalid authorization, letting the charm keep using another charm’s workload without permission. The published severity is low, and no fix is available in the provided sources.
Executive priority
Treat as a low-priority but relevant access-control issue for Juju deployments using cross-model relations. It matters most where database access controls are weak or many teams share models. Prioritize hardening privileged data access and monitoring until vendor guidance or a patch is available.
Technical view
The issue is improper validation of macaroons after cross-model permissions are revoked or expire. A malicious low-privileged user who can update database records can mint an invalid macaroon that the Juju controller incorrectly validates. This can preserve cross-model relation access beyond authorization. Listed CWEs are CWE-347 and CWE-672. CVSS v4.0 score is 2.1.
Likely exposure
Exposure is limited to environments using Canonical Juju with cross-model relations where an attacker already has low privilege and can update relevant database records. The source bundle lists Juju as affected but does not provide precise vulnerable version ranges beyond the affected product entry.
Exploitation context
The CVSS indicates adjacent attack vector, high attack complexity, required attack conditions, low privileges, and no user interaction. No active exploitation is reported in the provided sources, and the CVE is not listed as KEV in the source bundle.
Researcher notes
Evidence is limited to the CVE description, CVSS data, CWE mappings, and the GitHub advisory reference. The root issue combines invalid authorization validation with retention of permissions after expiry or revocation. The advisory states no fix is available at publication time; do not assume affected version boundaries beyond the supplied Juju product entry.
Mitigation direction
- Check Canonical’s Juju advisory for updates because no fix is currently listed.
- Restrict database record update access to trusted administrators only.
- Review cross-model relation permissions and remove unnecessary relations.
- Monitor for unexpected continued relations after permission revocation or expiry.
- Apply vendor updates promptly if Canonical publishes a fix.
Validation and detection
- Inventory Juju controllers and models using cross-model relations.
- Identify accounts or services able to update Juju database records.
- Confirm whether revoked or expired cross-model permissions remain effective.
- Review audit logs for unexpected relation activity after revocation.
- Track the GitHub advisory for version-specific remediation guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-347: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-672: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-1237 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 2.1 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:A/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:A/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
2.1LowVector: CVSS:4.0/AV:A/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/juju/juju/security/advisories/GHSA-j477-6vpg-6c8xCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Verification of Cryptographic Signature
Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Operation on a Resource after Expiration or Release
Operation on a Resource after Expiration or Release represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.