VulnerabilityPublished 27 Dec 2025Updated 29 Dec 2025

CVE-2025-15108: PandaXGO PandaX · Use of Hard-coded Cryptographic Key

Affects PandaXGO PandaXSource CVE Database V5

Public exploit available · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Base metrics

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Immediately audit all PandaXGO PandaX deployments to identify versions affected by the hard-coded key vulnerability.
Replace the hard-coded cryptographic key with a securely generated, environment-specific secret managed through a dedicated secrets management system or hardware security module (HSM).
Implement strict access controls and monitoring on JWT issuance and validation processes to detect anomalous token usage or forgery attempts.
Employ runtime application self-protection (RASP) or Web Application Firewalls (WAF) with custom rules to detect and block suspicious JWT-related activities.
Enforce short token lifetimes and implement token revocation mechanisms to limit the window of exploitation.
Monitor threat intelligence feeds for any emerging exploits targeting this vulnerability and prepare incident response plans accordingly.
Engage with PandaXGO vendor or community channels to track patch releases and apply updates promptly once available.
Conduct regular security reviews of cryptographic implementations to prevent similar issues in the future.

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.

Impact

For European organizations, the use of a hard-coded cryptographic key in PandaXGO PandaX poses a significant risk to the confidentiality and integrity of authentication tokens. Exploitation could allow attackers to impersonate legitimate users or escalate privileges, leading to unauthorized access to sensitive systems and data. This is particularly critical for sectors such as finance, healthcare, and government, where JWT tokens often protect sensitive transactions and personal data. The medium severity and high complexity of exploitation suggest that while widespread attacks may be limited, targeted attacks against high-value assets are plausible. The lack of vendor response and patch availability increases exposure time, raising the risk of eventual exploitation. Additionally, the rolling release model complicates patch management and vulnerability tracking, potentially delaying remediation efforts. European organizations using PandaXGO PandaX must assess their exposure and implement compensating controls to mitigate risk until a patch is available.

Summary

CVE-2025-15108 identifies a cryptographic vulnerability in the PandaXGO PandaX software, specifically within the JWT Secret Handler component configured via the config.yml file. The vulnerability arises from the use of a hard-coded cryptographic key, which is embedded directly in the software rather than being dynamically generated or securely stored. This static key can be discovered and exploited by attackers to forge or manipulate JSON Web Tokens (JWTs), potentially bypassing authentication or authorization mechanisms. The vulnerability affects versions up to commit fb8ff40f7ce5dfebdf66306c6d85625061faf7e5, but due to the product’s rolling release system, exact versioning is difficult to ascertain. The attack vector is remote with no need for authentication or user interaction, but the complexity to exploit is high, indicating that a skilled attacker is required. The CVSS 4.0 score of 6.3 reflects medium severity, with network attack vector, high attack complexity, and no privileges or user interaction needed. The vulnerability does not impact integrity or availability directly but compromises confidentiality by exposing cryptographic secrets. No patches or vendor responses have been published, and while no known exploits are currently active in the wild, the public disclosure increases risk. Organizations relying on PandaXGO PandaX for JWT-based authentication are at risk of token forgery or unauthorized access if this vulnerability is exploited.

References

Community reviews

Loading reviews…