# CVE-2026-12819: DVP-12SE Missing Authentication and Unauthorized Write access Vulnerability

> Unauthenticated attackers can access and modify security-sensitive PLC functions via the exposed Modbus TCP service on Delta DVP-12SE devices.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 30 Jun 2026
- **Updated:** 30 Jun 2026
- **Also known as:** GHSA-xpw2-pg2w-j67h

## What is CVE-2026-12819?

CVE-2026-12819 is a critical missing authorization vulnerability in deltaww DVP-12SE, published on 30 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Delta Electronics DVP12SE PLC exposes a Modbus TCP service over a specified port without authentication or access control, permitting unauthenticated interaction with security-sensitive PLC functions.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-12819 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12819 is a critical missing authorization vulnerability in deltaww DVP-12SE, published on 30 Jun 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-12819 in the wild and no public exploit code.

Affected product: deltaww DVP-12SE. 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-12819/ (Markdown: https://insights.sbomify.com/CVE-2026-12819/index.md)
```

## Sources

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

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