VulnerabilityPublished 6 Jun 2025Updated 9 Jun 2025

CVE-2025-49599: Huawei EG8141A5 · Incorrect Authorization

Affects Huawei EG8141A5Source CVE Database V5

Not known to be exploited · CVSS 4.1 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

4.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Huawei EG8141A5	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2025-49599, European organizations should first verify if their Huawei ONT devices are among the affected models and firmware versions. Immediate steps include: 1) Restricting access to the Epuser account by changing default credentials and enforcing strong, unique passwords; 2) Disabling or limiting the use of the Epuser account if possible; 3) Implementing network segmentation to isolate ONT devices from critical internal networks; 4) Monitoring network traffic for unusual activity on SSH and TELNET ports; 5) Applying any available firmware updates or patches from Huawei as soon as they are released; 6) Employing multi-factor authentication for device management interfaces if supported; 7) Conducting regular audits of device configurations to detect unauthorized changes to firewall settings; 8) Coordinating with ISPs or service providers to ensure secure provisioning and management of ONT devices. Since no patches are currently listed, organizations should engage with Huawei support for timelines and interim protective measures.

Description

Huawei EG8141A5 devices through V5R019C00S100, EG8145V5 devices through V5R019C00S100, and EG8145V5-V2 devices through V5R021C00S184 allow the Epuser account to disable ONT firewall functionality, e.g., to remove the default blocking of the SSH and TELNET TCP ports, aka HWNO-56Q3.

Impact

For European organizations, especially those relying on Huawei ONT devices for fiber broadband connectivity, this vulnerability poses a risk of unauthorized modification of device firewall settings. If an attacker gains access to the Epuser account—potentially through credential compromise or insider threat—they could disable firewall protections, exposing the device and connected networks to remote attacks via SSH or TELNET. This could lead to unauthorized configuration changes, installation of malware, or pivoting attacks into internal networks. The impact is particularly relevant for enterprises and critical infrastructure operators using Huawei ONTs in their network edge, as it could undermine network integrity and trust. Additionally, given the widespread deployment of Huawei equipment in various European countries, this vulnerability could affect a significant number of endpoints. The lack of confidentiality impact reduces the risk of data leakage directly from this vulnerability, but integrity compromise can facilitate further attacks. The medium severity suggests that while exploitation is not trivial, the consequences warrant attention, especially in regulated sectors such as finance, healthcare, and government services.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

youtube.com/watch?v=l1eYpcNvZdQ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 07:55 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats