# CVE-2026-26049: Jinan USR IOT Technology Limited (PUSR) USR-W610 Insufficiently Protected Credentials

> The web interface displays administrator passwords in plaintext, allowing attackers to steal credentials via shoulder surfing or browser caching.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Feb 2026
- **Updated:** 20 Feb 2026
- **Also known as:** GHSA-rxjp-cgw5-jfcg

## What is CVE-2026-26049?

CVE-2026-26049 is a medium-severity vulnerability in Jinan USR IOT Technology Limited (PUSR) USR-W610, published on 20 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The web management interface of the device renders the passwords in a 
plaintext input field. The current password is directly visible to 
anyone with access to the UI, potentially exposing administrator 
credentials to unauthorized observation via shoulder surfing, 
screenshots, or browser form caching.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2026-26049 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-26049 is a medium-severity vulnerability in Jinan USR IOT Technology Limited (PUSR) USR-W610, published on 20 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-26049 in the wild and no public exploit code.

Affected product: Jinan USR IOT Technology Limited (PUSR) USR-W610. 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-26049/ (Markdown: https://insights.sbomify.com/CVE-2026-26049/index.md)
```

## Sources

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

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