# CVE-2026-8072: Insecure generation of SAT access credentials in Ingecon EMS Board

> Weak credential generation in Ingecon EMS Board allows attackers to escalate privileges via insecure hashing.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/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:** 12 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-4h3h-6vxm-m4vr

## What is CVE-2026-8072?

CVE-2026-8072 is a critical vulnerability in Ingeteam Ingecon Sun EMS Board, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insecure generation of credentials in the local SAT (Technical Support) access functionality of the Ingecon Sun EMS Board. The vulnerability arose because the secret access credentials were not based on a secure cryptographic scheme, but rather on a weak hashing algorithm, which could allow an attacker to carry out a privilege escalation.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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


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

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

## Is CVE-2026-8072 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-8072 is a critical vulnerability in Ingeteam Ingecon Sun EMS Board, published on 12 May 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-8072 in the wild and no public exploit code.

Affected product: Ingeteam Ingecon Sun EMS Board. 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-8072/ (Markdown: https://insights.sbomify.com/CVE-2026-8072/index.md)
```

## Sources

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

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