# CVE-2024-39888: A vulnerability has been identified in Mendix Encryption (All versions >= V10.0.0 < V10.0.2).


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Jul 2024
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-xq6h-7hww-f48m

## What is CVE-2024-39888?

CVE-2024-39888 is a high-severity vulnerability in Siemens Mendix Encryption, published on 9 Jul 2024. 

### Official description

A vulnerability has been identified in Mendix Encryption (All versions >= V10.0.0 < V10.0.2). Affected versions of the module define a specific hard-coded default value for the EncryptionKey constant, which is used in projects where no individual EncryptionKey was specified.

This could allow to an attacker to decrypt any encrypted project data, as the default encryption key can be considered compromised.

Weakness: CWE-547 (Use of Hard-coded, Security-relevant Constants)

## Which versions are affected by CVE-2024-39888?


## How do I fix CVE-2024-39888?

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

## Is CVE-2024-39888 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-39888 and fix it if it is affected.

What it is: CVE-2024-39888 is a high-severity vulnerability in Siemens Mendix Encryption, published on 9 Jul 2024. 
Exploitation: There is no known exploitation of CVE-2024-39888 in the wild and no public exploit code.

Affected product: Siemens Mendix Encryption. 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-2024-39888/ (Markdown: https://insights.sbomify.com/CVE-2024-39888/index.md)
```

## Sources

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

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