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.
CVE-2026-12392
MEDIUMPre-NVD 5.35.3—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 5.3 from GitHub Security Advisory published 2026-10-02. A secondary CVSS source baseline 5.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.3Exploit: None knownExposed services: Not assessed
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3MEDIUMhigh confidence
- EG Risk
- 39EG Risk 39/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release. - EPSS PROB
- 0.3%
- EPSS %ILE
- 17th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).
An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 2, 2026
Last Modified
October 4, 2026
Advisory Details (6)
Auto-updated Oct 2, 2026Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit
commit 65e89c05970f (canonical/maas)
Fix landed in canonical/maas commit 65e89c05970f — awaiting tagged release
https://github.com/canonical/maas/commit/65e89c05970f4514f9e6de043c2779017b43ad9dgithub_commit
commit 3864ef9dca54 (canonical/maas)
Fix landed in canonical/maas commit 3864ef9dca54 — awaiting tagged release
https://github.com/canonical/maas/commit/3864ef9dca54e36e3d34d18233b87666b8ee1dc8github_commit
commit ead659f70224 (canonical/maas)
Fix landed in canonical/maas commit ead659f70224 — awaiting tagged release
https://github.com/canonical/maas/commit/ead659f70224538517c80478c3fd8c9e730aae79github_commit
commit a9486ad0cc90 (canonical/maas)
Fix landed in canonical/maas commit a9486ad0cc90 — awaiting tagged release
https://github.com/canonical/maas/commit/a9486ad0cc90f4571142c1bea13f02d1361cb31egithub_commit
commit 8489979d64b0 (canonical/maas)
Fix landed in canonical/maas commit 8489979d64b0 — awaiting tagged release
https://github.com/canonical/maas/commit/8489979d64b0e7f124e7cef66d02b21263918f9bVendor Advisories for CVE-2026-12392(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-04 23:21 UTCEPSS rescore
- 2026-10-04 16:25 UTCEG score recompute
- 2026-10-04 16:25 UTCGHSA enrichment
- 2026-10-04 15:58 UTCEG score recompute
- 2026-10-04 15:58 UTCGHSA enrichment
- 2026-10-03 16:23 UTCEG score recompute
- 2026-10-03 16:23 UTCGHSA enrichment
- 2026-10-03 16:11 UTCEG score recompute
- 2026-10-03 16:11 UTCGHSA enrichment
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-02 20:20 UTCEG score recompute
- 2026-10-02 19:36 UTCEG score recompute
- 2026-10-02 19:35 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-12392?
CVE-2026-12392 is a medium vulnerability published on October 2, 2026. 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…
When was CVE-2026-12392 disclosed?
CVE-2026-12392 was first published on October 2, 2026, with the most recent update on October 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12392 actively exploited?
CVE-2026-12392 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-12392?
CVE-2026-12392 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-12392?
An upstream fix for CVE-2026-12392 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-12392 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-12392
Is Your Infrastructure Affected by CVE-2026-12392?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.