# CVE-2026-82786: Information disclosure in Remote I/O Coupler Unit (Server Type) CPSN-MCB271-*

> Attackers can restore sensitive credentials from backup files in Contec Remote I/O Coupler Units, exposing system secrets.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/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 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-622w-5wv2-xm5f

## What is CVE-2026-82786?

CVE-2026-82786 is a high-severity vulnerability in Contec Co., Ltd. Remote I/O Coupler Unit (Server Type) CPSN-MCB271-*, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insufficiently protected credentials issue exists in Remote I/O Coupler Unit (Server Type) CPSN-MCB271-*. If this vulnerability is exploited, sensitive information may be restored from a backup file.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2026-82786 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82786 is a high-severity vulnerability in Contec Co., Ltd. Remote I/O Coupler Unit (Server Type) CPSN-MCB271-*, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82786 in the wild and no public exploit code.

Affected product: Contec Co., Ltd. Remote I/O Coupler Unit (Server Type) CPSN-MCB271-*. 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-82786/ (Markdown: https://insights.sbomify.com/CVE-2026-82786/index.md)
```

## Sources

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

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