# CVE-2016-15056: Ubee EVW3226 Unauthenticated Backup File Disclosure

> Remote attackers can download unencrypted configuration backups from the web root to obtain plaintext admin credentials and compromise the device.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Nov 2025
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-8v9v-gw67-q3r5

## What is CVE-2016-15056?

CVE-2016-15056 is a high-severity vulnerability in Ubee EVW3226, published on 14 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ubee EVW3226 cable modem/routers firmware versions up to and including 1.0.20 store configuration backup files in the web root after they are generated for download. These backup files remain accessible without authentication until the next reboot. A remote attacker on the local network can request 'Configuration_file.cfg' directly to obtain the backup archive. Because backup files are not encrypted, they expose sensitive information including the plaintext admin password, allowing full compromise of the device.

Weakness: CWE-538 (Insertion of Sensitive Information into Externally-Accessible File or Directory)

## Which versions are affected by CVE-2016-15056?


## How do I fix CVE-2016-15056?

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

## Is CVE-2016-15056 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-15056 and fix it if it is affected.

What it is: CVE-2016-15056 is a high-severity vulnerability in Ubee EVW3226, published on 14 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-15056 exists.

Affected product: Ubee EVW3226. 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-2016-15056/ (Markdown: https://insights.sbomify.com/CVE-2016-15056/index.md)
```

## Sources

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

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