CVE-2026-110123

HIGHPre-NVD 7.17.1
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: a secondary CVSS source
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Makunet maku-boot 4.3.0 through 5.0.0 contains a missing authorization vulnerability that allows authenticated users to read mail and SMS configurations by calling /sys/mail/config/list and /sys/sms/config/list without the required authority checks. Attackers can retrieve unmasked SMTP passwords and Aliyun, Tencent Cloud, Qiniu or Huawei Cloud access keys, and abuse /sys/mail/config/send to send mail to arbitrary recipients.

CVSS v3
7.1
EG Score
7.1HIGHlow confidence
EG Risk
32
EG Risk 32/100

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 computed (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0% × 40%
No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 13, 2026

Last Modified

October 13, 2026

Advisory Details (6)

Auto-updated Oct 13, 2026
Patch available. Sources: github_release.
Web page

Makunet maku-boot 4.3.0 through 5.0.0 Missing Authorization via Mail and SMS Config Endpoints | Advisories | VulnCheck

https://www.vulncheck.com/advisories/makunet-maku-boot-4.3.0-through-5.0.0-missing-authorization-via-mail-and-sms-config-endpoints
GitHub release Patch Available

v5.0.0

Patch available: makunet/maku-boot v5.0.0

https://github.com/makunet/maku-boot/releases/tag/v5.0.0
Web page

maku-boot/maku-boot-system/src/main/java/net/maku/system/controller/SysSmsConfigController.java at 4cd202b037e2ac47e366d4b0691fb387c764d308 · makunet/maku-boot · GitHub

https://github.com/makunet/maku-boot/blob/4cd202b037e2ac47e366d4b0691fb387c764d308/maku-boot-system/src/main/java/net/maku/system/controller/SysSmsConfigController.java#L53-L59
Web page

maku-boot/maku-boot-system/src/main/java/net/maku/system/controller/SysMailConfigController.java at 4cd202b037e2ac47e366d4b0691fb387c764d308 · makunet/maku-boot · GitHub

https://github.com/makunet/maku-boot/blob/4cd202b037e2ac47e366d4b0691fb387c764d308/maku-boot-system/src/main/java/net/maku/system/controller/SysMailConfigController.java#L79-L84
Web page

maku-boot/maku-boot-system/src/main/java/net/maku/system/controller/SysMailConfigController.java at 4cd202b037e2ac47e366d4b0691fb387c764d308 · makunet/maku-boot · GitHub

https://github.com/makunet/maku-boot/blob/4cd202b037e2ac47e366d4b0691fb387c764d308/maku-boot-system/src/main/java/net/maku/system/controller/SysMailConfigController.java#L53-L59
Web page

maku-boot returns SMTP and cloud SMS credentials to any authenticated user through notification-config endpoints that skip the authority check - HackMD

https://hackmd.io/@1ExmmukzRMWN7B4gQ4W-4Q/maku-boot-mail-sms-config-bfla

Vendor Advisories for CVE-2026-110123(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 3× in last 7d / 3× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 17:28 UTCEG score recompute
  2. 2026-10-13 17:05 UTCEG score recomputeFirst assessed: 7.1 HIGH
  3. 2026-10-13 17:04 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-110123?
CVE-2026-110123 is a high-severity vulnerability; its CVE record was published on October 13, 2026. Makunet maku-boot 4.3.0 through 5.0.0 contains a missing authorization vulnerability that allows authenticated users to read mail and SMS configurations by calling /sys/mail/config/list and /sys/sms/config/list without the required authority checks. Attackers can retrieve unmasked SMTP passwords…
When was CVE-2026-110123 made public?
CVE-2026-110123 was made public on October 13, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 13, 2026. EchelonGraph's copy of the record carries a last-modified date of October 13, 2026; the record at its source may have been updated since.
What is the CVSS score of CVE-2026-110123?
CVE-2026-110123 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-110123?
A fix for CVE-2026-110123 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-110123 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-110123

Explore →

Is Your Infrastructure Affected by CVE-2026-110123?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.