cve.bz

CVE-2026-3867 moxa: Improper Ownership Management

6.0 mediumEPSS 0.2%

Medium (6.0) in moxa. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
An improper ownership management vulnerability has been identified in Moxa’s Secure Router. Because of improper ownership management, a low-privileged authenticated user may access a configuration file containing the hashed password of the administrative account. Successful exploitation of this vulnerability could allow an attacker to obtain sensitive information. Exploitation is only possible under a specific condition — when the configuration file has been exported. This vulnerability does not impact the integrity or availability of the affected product, and no confidentiality, integrity, or availability impact to the subsequent system has been identified.

Severity

CVSS 4.0

6.0 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 15th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-04-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-282 Improper Ownership Management
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-3867 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-3867?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-3867?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-3867 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-3867

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-3867](https://cve.bz/cve/badge/CVE-2026-3867.svg)](https://cve.bz/cve/CVE-2026-3867)

HTML:

<a href="https://cve.bz/cve/CVE-2026-3867"><img src="https://cve.bz/cve/badge/CVE-2026-3867.svg" alt="CVE-2026-3867"></a>

Affected

  • moxa:edr-8010 series
  • moxa:edr-g9010 series

Versions

From the CNA's record in the CVE List.

ProductAffected
Moxa EDR-8010 Seriesfrom 1.0 through 3.23
Moxa EDR-G9010 Seriesfrom 1.0 through 3.23.1
Moxa EDR-G9010 Series3.24

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON