# CVE-2025-49599: Security feature bypass in EG8141A5

> The Epuser account can disable the ONT firewall, removing default blocks on SSH and TELNET ports, exposing the device to unauthorized access.

- **Severity:** Medium 4.1 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jun 2025
- **Updated:** 9 Jun 2025
- **Also known as:** GHSA-mvv2-f7c3-j32m

## What is CVE-2025-49599?

CVE-2025-49599 is a medium-severity vulnerability in Huawei EG8141A5, published on 6 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-49599?


## How do I fix CVE-2025-49599?

No fix has been published for CVE-2025-49599 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-49599 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49599 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-49599 and fix it if it is affected.

What it is: CVE-2025-49599 is a medium-severity vulnerability in Huawei EG8141A5, published on 6 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49599 exists.

Affected product: Huawei EG8141A5. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-49599/ (Markdown: https://insights.sbomify.com/CVE-2025-49599/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-49599
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-49599
- OSV: https://osv.dev/vulnerability/CVE-2025-49599

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-49599/
Summaries are generated and may contain mistakes; the official description above is the record.