# CVE-2026-111696: data-platform-open through commit efeacd3 Hardcoded AES Key for Datasource Passwords

> Authenticated attackers can decrypt stored datasource passwords using a hardcoded AES key, exposing plaintext database credentials.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-jhvf-5wf6-hcgg

## What is CVE-2026-111696?

CVE-2026-111696 is a high-severity vulnerability in shaiwz data-platform-open, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

data-platform-open through commit efeacd3 uses a hardcoded, publicly known default AES key in AesPasswordEncAndDecServiceImpl, allowing authenticated attackers to decrypt stored datasource passwords. Attackers can obtain ciphertext passwords from the datasource detail API, for example via cross-workspace IDOR, and decrypt them offline to recover plaintext database credentials.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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


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

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

## Is CVE-2026-111696 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111696 is a high-severity vulnerability in shaiwz data-platform-open, published on 16 Oct 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-111696 in the wild and no public exploit code.

Affected product: shaiwz data-platform-open. 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-111696/ (Markdown: https://insights.sbomify.com/CVE-2026-111696/index.md)
```

## Sources

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

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