{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66908 exists.","fix":"No fix has been published for CVE-2025-66908 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-66908 is a medium-severity vulnerability in n/a, published on 19 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-66908 and fix it if it is affected.\n\nWhat it is: CVE-2025-66908 is a medium-severity vulnerability in n/a, published on 19 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66908 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-66908/ (Markdown: https://insights.sbomify.com/CVE-2025-66908/index.md)","id":"CVE-2025-66908","markdown":"https://insights.sbomify.com/CVE-2025-66908/index.md","name":"CVE-2025-66908","record":{"aliases":["GHSA-rxfw-3x38-vmhv"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Turms AI-Serving module","requires_auth":"none","summary":"Attackers can upload malicious files by bypassing image validation, potentially leading to server-side code execution or information disclosure.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"turms","vendor":"turms-im"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"Turms AI-Serving module v0.10.0-SNAPSHOT and earlier contains an improper file type validation vulnerability in the OCR image upload functionality. The OcrController in turms-ai-serving/src/main/java/im/turms/ai/domain/ocr/controller/OcrController.java uses the @FormData(contentType = MediaTypeConst.IMAGE) annotation to restrict uploads to image files, but this constraint is not properly enforced. The system relies solely on client-provided Content-Type headers and file extensions without validating actual file content using magic bytes (file signatures). An attacker can upload arbitrary file types including executables, scripts, HTML, or web shells by setting the Content-Type header to \"image/*\" or using an image file extension. This bypass enables potential server-side code execution, stored XSS, or information disclosure depending on how uploaded files are processed and served.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"File upload in n/a","id":"CVE-2025-66908","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Denial of service in n/a","id":"CVE-2025-66909"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2025-66906"},"products":["n/a"],"published":"2025-12-19","related":[{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2025-66909","kev_date_added":null,"published":"2025-12-19"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2025-66911","kev_date_added":null,"published":"2025-12-19"},{"cvss_score":6.1,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-66906","kev_date_added":null,"published":"2025-12-19"},{"cvss_score":6,"headline":"Information disclosure in n/a","id":"CVE-2025-66910","kev_date_added":null,"published":"2025-12-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-19","vendors":["n/a"]},"summary":"Attackers can upload malicious files by bypassing image validation, potentially leading to server-side code execution or information disclosure.","url":"https://insights.sbomify.com/CVE-2025-66908/"}