# CVE-2026-79396: Hardcoded credentials in n/a

> Remote attackers can gain full administrative control over Xiongmai IP cameras by exploiting hardcoded default credentials stored in plaintext configuration files.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-9xx2-xxg3-9xpx

## What is CVE-2026-79396?

CVE-2026-79396 is a critical vulnerability in n/a, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use of hardcoded default credentials in Xiongmai IP Camera XM530 firmware HMT.CM2005-v220608.1837 and earlier stores static account credentials in unencrypted plaintext within bin/config.xml and compiled into the Sofia executable, allowing remote attackers to gain full administrative control over the camera.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2026-79396 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79396 is a critical vulnerability in n/a, published on 11 Sep 2026. 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-2026-79396 exists.

Affected product: n/a. 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-79396/ (Markdown: https://insights.sbomify.com/CVE-2026-79396/index.md)
```

## Sources

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

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