# CVE-2026-44105: Cleartext password in logs

> A local attacker with log access can read cleartext credentials to authenticate as a limited user, potentially interrupting charging operations.

- **Severity:** Medium 5.8 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA: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:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-hc4q-m2pq-frr6

## What is CVE-2026-44105?

CVE-2026-44105 is a medium-severity vulnerability in Phoenix Contact CHARX SEC-3000, published on 30 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The credentials for the local user "user-app" may be exposed in log files, potentially enabling a low-privileged local attacker with access to the logs to authenticate via SSH as the limited user "user-app". Charging could be interrupted.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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


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

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

## Is CVE-2026-44105 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44105 is a medium-severity vulnerability in Phoenix Contact CHARX SEC-3000, published on 30 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44105 in the wild and no public exploit code.

Affected product: Phoenix Contact CHARX SEC-3000. 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-44105/ (Markdown: https://insights.sbomify.com/CVE-2026-44105/index.md)
```

## Sources

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

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