# CVE-2026-81943: PLANET IGS-5225-8P2T4S V1/V2 Debug Mode RCE

> Privileged attackers can enable debug mode to execute arbitrary code and gain root access on PLANET industrial switches.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-g7v4-27pr-jwj2

## What is CVE-2026-81943?

CVE-2026-81943 is a high-severity vulnerability in PLANET IGS-5225-8P2T4S V1, published on 18 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PLANET IGS-5225-8P2T4S industrial managed switch V1 and V2 firmware versions before 1.2412b260707 and 2.2412b260519 contain active debug functionality in the embedded software. An attacker with privileged access to the device can enable this debug mode to execute arbitrary code on the underlying operating system and gain root-level access.

Weakness: CWE-489 (Active Debug Code)

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


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

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

## Is CVE-2026-81943 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81943 is a high-severity vulnerability in PLANET IGS-5225-8P2T4S V1, published on 18 Sep 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-81943 in the wild and no public exploit code.

Affected product: PLANET IGS-5225-8P2T4S V1. 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-81943/ (Markdown: https://insights.sbomify.com/CVE-2026-81943/index.md)
```

## Sources

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

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