# CVE-2025-15108: PandaXGO PandaX JWT Secret config.yml hard-coded key

> Attackers can exploit a hard-coded JWT secret in PandaX 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:** No
- **Published:** 27 Dec 2025
- **Updated:** 29 Dec 2025
- **Also known as:** GHSA-hj3q-q387-m5hr

## What is CVE-2025-15108?

CVE-2025-15108 is a medium-severity vulnerability in PandaXGO PandaX, 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 vulnerability was detected in PandaXGO PandaX up to fb8ff40f7ce5dfebdf66306c6d85625061faf7e5. This affects an unknown function of the file config.yml of the component JWT Secret Handler. The manipulation of the argument key results in use of hard-coded cryptographic key
 . The attack may be performed from remote. This attack is characterized by high complexity. The exploitability is reported as difficult. The exploit is now public and may be used. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. The project was informed of the problem early through an issue report but has not responded yet.

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

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


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

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

## Is CVE-2025-15108 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15108 is a medium-severity vulnerability in PandaXGO PandaX, 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-15108 exists.

Affected product: PandaXGO PandaX. 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-15108/ (Markdown: https://insights.sbomify.com/CVE-2025-15108/index.md)
```

## Sources

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

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