# CVE-2026-69419: Azure Data Manager for Energy Remote Code Execution Vulnerability

> An integer overflow in Azure Data Manager for Energy allows authorized attackers to execute code remotely.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **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:** 20 Aug 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-5vp6-c73p-75c8

## What is CVE-2026-69419?

CVE-2026-69419 is a high-severity vulnerability in Microsoft Azure Data Manager for Energy, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Integer overflow or wraparound in Azure Data Manager for Energy allows an authorized attacker to execute code over a network.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Microsoft Azure Data Manager for Energy.

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

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

## Is CVE-2026-69419 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-69419 is a high-severity vulnerability in Microsoft Azure Data Manager for Energy, published on 20 Aug 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-69419 in the wild and no public exploit code.

Affected product: Microsoft Azure Data Manager for Energy. 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-69419/ (Markdown: https://insights.sbomify.com/CVE-2026-69419/index.md)
```

## Sources

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

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