# CVE-2025-15107: actiontech sqle JWT Secret jwt.go hard-coded key

> Attackers can exploit a hard-coded JWT secret in actiontech sqle to bypass authentication and potentially take over accounts.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/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:** Yes
- **Published:** 27 Dec 2025
- **Updated:** 29 Dec 2025
- **Also known as:** GHSA-43h9-hc38-qph5, GO-2025-4269

## What is CVE-2025-15107?

CVE-2025-15107 is a medium-severity vulnerability in actiontech sqle, published on 27 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security vulnerability has been detected in actiontech sqle up to 4.2511.0. The impacted element is an unknown function of the file sqle/utils/jwt.go of the component JWT Secret Handler. The manipulation of the argument JWTSecretKey leads to use of hard-coded cryptographic key
 . The attack is possible to be carried out remotely. The attack's complexity is rated as high. The exploitability is regarded as difficult. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report and is planning to fix this flaw in an upcoming release.

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

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

3 open source packages ship an affected version, including github.com/actiontech/sqle. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/actiontech/sqle` | Go | All versions | None |
| `github.com/actiontech/sqle` | Go | All versions to 4.2511.0 | None |
| `github.com/actiontech/sqle` | Go | All versions to 4.2511.0 | None |

Products: Actionsky Sqle.

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

Upgrade to a fixed version.

## Is CVE-2025-15107 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15107 is a medium-severity vulnerability in actiontech sqle, published on 27 Dec 2025. 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-2025-15107 exists.

Affected packages and fixed versions:
- github.com/actiontech/sqle (Go): affected all versions; no fix listed
- github.com/actiontech/sqle (Go): affected all versions up to 4.2511.0; no fix listed
- github.com/actiontech/sqle (Go): affected all versions up to 4.2511.0; no fix listed

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-15107/ (Markdown: https://insights.sbomify.com/CVE-2025-15107/index.md)
```

## Sources

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

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