# CVE-2025-10080: running-elephant Datart API AESUtil.java getTokensecret hard-coded key

> Attackers can exploit a hard-coded cryptographic key in the Datart API to bypass security controls, requiring high complexity and permissions.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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:** 8 Sep 2025
- **Updated:** 8 Sep 2025
- **Also known as:** GHSA-6fx4-gj89-g98p

## What is CVE-2025-10080?

CVE-2025-10080 is a low-severity vulnerability in running-elephant Datart, published on 8 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in running-elephant Datart up to 1.0.0-rc3. Affected by this issue is the function getTokensecret of the file datart/security/src/main/java/datart/security/util/AESUtil.java of the component API. The manipulation leads to use of hard-coded cryptographic key
 . The attack is possible to be carried out remotely. The attack is considered to have high complexity. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used.

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

## Which versions are affected by CVE-2025-10080?


## How do I fix CVE-2025-10080?

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

## Is CVE-2025-10080 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10080 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10080 and fix it if it is affected.

What it is: CVE-2025-10080 is a low-severity vulnerability in running-elephant Datart, published on 8 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10080 exists.

Affected product: running-elephant Datart. 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-2025-10080/ (Markdown: https://insights.sbomify.com/CVE-2025-10080/index.md)
```

## Sources

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

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