# CVE-2026-55985: Tycon Systems TPDIN-Monitor-WEB2 Cleartext Storage of Sensitive Information

> Authenticated users can view system credentials in cleartext on the web management interface, potentially allowing attackers to compromise other local network systems.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jul 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-gg6g-q7xj-hhwf

## What is CVE-2026-55985?

CVE-2026-55985 is a medium-severity vulnerability in Tycon Systems TPDIN-Monitor-WEB2, published on 24 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The web management interface in Tycon Systems TPDIN-Monitor-WEB2

stores and displays system credentials in cleartext on a certain configuration page accessible to authenticated users. Any party with access to the administrative dashboard can immediately read these credentials, which may be used to compromise other systems on the local network.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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


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

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

## Is CVE-2026-55985 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55985 is a medium-severity vulnerability in Tycon Systems TPDIN-Monitor-WEB2, published on 24 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-55985 in the wild and no public exploit code.

Affected product: Tycon Systems TPDIN-Monitor-WEB2. 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-55985/ (Markdown: https://insights.sbomify.com/CVE-2026-55985/index.md)
```

## Sources

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

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