# CVE-2026-7018: Datavane Datavines JWT Token TokenManager.java hard-coded key

> Hard-coded JWT secret in Datavines allows attackers to forge tokens and bypass authentication, requiring a patch to secure the system.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Apr 2026
- **Updated:** 27 Apr 2026
- **Also known as:** GHSA-cv5p-9wv2-xphq

## What is CVE-2026-7018?

CVE-2026-7018 is a medium-severity vulnerability in Datavane Datavines, published on 26 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was determined in Datavane Datavines up to 13607645e14a4982468cfdbcf75c85cde63bae71. The affected element is an unknown function of the file datavines-core/src/main/java/io/datavines/core/utils/TokenManager.java of the component JWT Token Handler. Executing a manipulation of the argument tokenSecret can lead to use of hard-coded cryptographic key
 . The attack can be executed remotely. The attack requires a high level of complexity. The exploitability is described as difficult. The exploit has been publicly disclosed and may be utilized. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. This patch is called e540d6dc04e2e6ad11907fb655f3728a13e7b939. It is advisable to implement a patch to correct this issue. The project was informed of the problem early through a pull request but has not reacted yet.

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

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


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

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

## Is CVE-2026-7018 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7018 is a medium-severity vulnerability in Datavane Datavines, published on 26 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7018 exists.

Affected product: Datavane Datavines. 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-7018/ (Markdown: https://insights.sbomify.com/CVE-2026-7018/index.md)
```

## Sources

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

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