# CVE-2026-49000: Cryptography Implementation Flaw vulnerability in ZTE ZXUniPOS NDS-LTE product

> Weak cryptography in ZTE ZXUniPOS NDS-LTE allows attackers to potentially leak or tamper with data due to insecure password schemes.

- **Severity:** High 7.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-grx5-r275-m4vr

## What is CVE-2026-49000?

CVE-2026-49000 is a high-severity vulnerability in ZTE ZXUniPOS NDS-LTE, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An insecure password scheme refers to vulnerabilities arising from improper selection of encryption algorithms, inadequate key management, or flawed code implementation, which may lead to data leakage or tampering, such as hard-coded keys or the use of weak encryption algorithms.

Weakness: CWE-310

## Which versions are affected by CVE-2026-49000?


## How do I fix CVE-2026-49000?

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

## Is CVE-2026-49000 being exploited?

There is no known exploitation of CVE-2026-49000 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49000 and fix it if it is affected.

What it is: CVE-2026-49000 is a high-severity vulnerability in ZTE ZXUniPOS NDS-LTE, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49000 in the wild and no public exploit code.

Affected product: ZTE ZXUniPOS NDS-LTE. 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-2026-49000/ (Markdown: https://insights.sbomify.com/CVE-2026-49000/index.md)
```

## Sources

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

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