CVE-2025-66908VulnerabilityPublished 19 Dec 2025

CVE-2025-66908: turms-ai-serving · n/a

Affects turms-ai-servingSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

5.3Medium

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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 impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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 2026-10-26.

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 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
GitHubturms-im/turms-ai-serving`pkg:github/turms-im/turms-ai-serving`Other threats	Affected =0.10.0-SNAPSHOT	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-66908, European organizations should implement strict server-side validation of uploaded files beyond relying on Content-Type headers and file extensions. Specifically, validate the actual file content using magic bytes or file signature verification libraries to ensure only legitimate image files are accepted. Employ allowlists for acceptable MIME types and file extensions combined with content inspection. Implement sandboxing or isolation mechanisms for processing uploaded files to limit potential damage from malicious payloads. Regularly update the Turms AI-Serving module to the latest versions once patches are released. Monitor file upload logs for suspicious activity such as unexpected file types or repeated upload attempts. Employ web application firewalls (WAFs) with rules to detect and block malicious file uploads. Conduct security testing including fuzzing and penetration testing focused on file upload functionalities. Educate developers on secure file handling practices and the risks of trusting client-supplied metadata. Finally, restrict permissions on directories handling uploads to prevent execution of uploaded files and enforce least privilege principles on the server environment.

Description

CVE-2025-66908 is a medium severity vulnerability in the Turms AI-Serving module (v0.10.0-SNAPSHOT and earlier) related to improper file type validation in the OCR image upload functionality. The system relies solely on client-supplied Content-Type headers and file extensions without verifying actual file content using magic bytes, allowing attackers to upload arbitrary file types including executables or web shells. This can lead to server-side code execution, stored cross-site scripting (XSS), or information disclosure depending on file processing and serving. The vulnerability stems from CWE-434 (Unrestricted Upload of File with Dangerous Type). No known exploits are currently reported in the wild. The CVSS score is 5.3 (medium), reflecting network attack vector, low complexity, no privileges or user interaction required, and limited confidentiality impact. European organizations using affected Turms AI-Serving versions should prioritize validation improvements and restrict file handling to mitigate risks.

Impact

For European organizations using the Turms AI-Serving module, this vulnerability poses a moderate risk. If exploited, attackers could upload malicious files leading to server-side code execution, which may compromise the affected system's integrity and availability. Stored XSS attacks could impact users interacting with the system, potentially leading to session hijacking or phishing. Information disclosure risks arise if sensitive data is exposed through improperly handled uploaded files. The impact is particularly significant for organizations relying on OCR services for document processing, automated workflows, or AI-driven data extraction, as compromise could disrupt critical business operations or leak confidential information. Given the network attack vector and no requirement for authentication or user interaction, attackers can exploit this vulnerability remotely and anonymously, increasing the threat surface. However, the absence of known exploits and the medium CVSS score suggest the threat is moderate but should not be underestimated. Organizations in sectors such as finance, healthcare, legal, and government, which often process sensitive documents with OCR, face higher risks. The vulnerability could also be leveraged as a foothold for further lateral movement or data exfiltration within corporate networks.

CWE-434Unrestricted Upload of File with Dangerous Type (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #12OWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
Architecture and Design
Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Architecture and Design
Consider storing the uploaded files outside of the web document root entirely. Then, use other mechanisms to deliver the files dynamically.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Web Service Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
File Upload (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V12.5.2 (opens in a new tab)
V13.1.5 (opens in a new tab)
V12.2.1 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Dec 2025, 15:22 UTC

WeaknessesCWE-434

Technical details

References

Community reviews

Related threats