CVE-2026-12392 json
RPC secret disclosure via vendor data endpoint in Canonical MAAS
published 2026-10-02 37 d ago modified 2026-10-06 33 d ago also EUVD-2026-91775
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
An information exposure vulnerability in Canonical MAAS prior to versions 3.4.10, 3.5.14, 3.6.5, 3.7.3, and 3.8.0 allows an unauthenticated attacker to retrieve the RPC secret in plaintext via the vendor data metadata endpoint. If a target machine was deployed with the 'register as rack' option enabled, an attacker who obtains or infers the machine's system ID can query the preseed/metadata server to leak the secret.
Patch / fix
- Canonical MAAS 3.4.10, 3.5.14, 3.6.5, 3.7.3, 3.8.0
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 36 d ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- Canonical MAAS
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
github.com
/canonical/maas/commit/8489979d64b0e7f124e7cef66d02b21263918f9b
patch
-
github.com
/canonical/maas/commit/a9486ad0cc90f4571142c1bea13f02d1361cb31e
patch
-
github.com
/canonical/maas/commit/ead659f70224538517c80478c3fd8c9e730aae79
patch
-
github.com
/canonical/maas/commit/3864ef9dca54e36e3d34d18233b87666b8ee1dc8
patch
-
github.com
/canonical/maas/commit/65e89c05970f4514f9e6de043c2779017b43ad9d
patch
-
bugs.launchpad.net
/maas/+bug/2153942
vendor-advisory, issue-tracking
Sources
- CVE List CVE-2026-12392
- NVD CVE-2026-12392
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.