VulnerabilityPublished 19 Nov 2025

CVE-2025-13316: Lynxtechnology Twonky Server · Use of Hard-coded Cryptographic Key

Affects Lynxtechnology Twonky ServerSource CVE Database V5

Public exploit available (Metasploit) · CVSS 8.2 High.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 4.0 base score

8.2High

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

EPSS: 2.7% chance of exploitation in 30 days – higher than 86% 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:H/VI:N/VA:N/SC:N/SI:N/SA:N

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

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: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
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.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
1 Metasploit module
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), 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

Affected software

Product	Affected	Fixed in
Lynxtechnology Twonky Server	Affected =8.5.2	Fixed in–

AI-suggested

Immediately restrict network access to Twonky Server management interfaces using firewalls or network segmentation to limit exposure to trusted administrators only.
Monitor logs and network traffic for unusual access patterns or attempts to retrieve encrypted password data.
If possible, disable Twonky Server services temporarily until a patch or update is released by Lynxtechnology.
Implement compensating controls such as multi-factor authentication (MFA) on administrative access points external to Twonky Server to reduce risk from credential compromise.
Regularly audit and rotate any credentials related to Twonky Server to limit the window of exposure.
Engage with Lynxtechnology support or vendor channels to obtain timelines for patches or workarounds.
Educate administrators about the risks of hard-coded keys and encourage secure password management practices.
Consider alternative media server solutions if Twonky Server is critical and no timely patch is forthcoming.

Description

CVE-2025-13316 is a high-severity vulnerability in Lynxtechnology Twonky Server 8.5.2 affecting both Linux and Windows platforms. The flaw involves the use of hard-coded cryptographic keys to encrypt administrator passwords. An attacker who obtains the encrypted admin password can decrypt it using the static keys, thereby revealing the plaintext password and gaining administrator-level access to the server. This vulnerability requires no authentication or user interaction but has a high attack complexity. Exploitation could lead to full control over the affected Twonky Server instance, compromising confidentiality and integrity. No known exploits are currently reported in the wild. European organizations using Twonky Server for media streaming or device management should prioritize patching or mitigating this issue. Countries with higher adoption of this product and strategic media infrastructure are at greater risk.

Impact

For European organizations, exploitation of this vulnerability could lead to unauthorized administrative access to Twonky Server instances, resulting in the compromise of sensitive media content, configuration settings, and potentially connected network devices. This could disrupt media services, violate data confidentiality, and enable lateral movement within corporate networks. Organizations relying on Twonky Server for internal or customer-facing media streaming services may face service outages or data breaches. The breach of administrator credentials could also facilitate further attacks, including malware deployment or espionage. Given the high CVSS score and the nature of the vulnerability, the impact on confidentiality and integrity is severe, though availability impact is limited unless the attacker intentionally disrupts services. The lack of known exploits reduces immediate risk but does not diminish the urgency for mitigation, especially in sectors with high media infrastructure reliance such as broadcasting, telecommunications, and hospitality.

CWE-321Use of Hard-coded Cryptographic Key (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses a hard-coded, unchangeable cryptographic key.
Architecture and Design
Prevention schemes mirror that of hard-coded password storage.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
HSTS (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.8.5 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

rapid7.com/blog/post/cve-2025-13315-cve-2025-13316-critical-twonky-server-authentication-bypass-not-fixed/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Nov 2025, 19:01 UTC

Public exploits and detection1 Metasploit module

WeaknessesCWE-321

Technical details

References

Community reviews

Related threats