Tinyllava Factory
Monthly
Code injection in TinyLLaVA Factory (TinyLLaVA_Factory) allows a remote attacker to execute arbitrary code with the privileges of the process that loads a model configuration, by supplying a crafted llm_model_name_or_path value that is handled by TinyLlavaConfig._load_text_config in tinyllava/model/configuration_tinyllava.py. Exploitation is not fully autonomous: user interaction is required (CVSS 4.0 UI:P / assessed CVSS 3.1 UI:R) because an operator must point the loader at the hostile path or model reference - an untouched default deployment is not affected - while authentication is not required per the vector (PR:N). Publicly available exploit code exists (the CVE reference set includes a public upstream issue/exploit at GitHub issue #212 and is flagged as 'exploit'), but there is no confirmation of active exploitation via CISA KEV, and because the project uses a rolling release with no response to the report, no vendor-patched version can be identified; the independent assessment (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) rates confidentiality, integrity and availability impact as High, well above the 2.1 score published by the reporting source.
Code injection in TinyLLaVA Factory (TinyLLaVA_Factory) allows a remote attacker to execute arbitrary code with the privileges of the process that loads a model configuration, by supplying a crafted llm_model_name_or_path value that is handled by TinyLlavaConfig._load_text_config in tinyllava/model/configuration_tinyllava.py. Exploitation is not fully autonomous: user interaction is required (CVSS 4.0 UI:P / assessed CVSS 3.1 UI:R) because an operator must point the loader at the hostile path or model reference - an untouched default deployment is not affected - while authentication is not required per the vector (PR:N). Publicly available exploit code exists (the CVE reference set includes a public upstream issue/exploit at GitHub issue #212 and is flagged as 'exploit'), but there is no confirmation of active exploitation via CISA KEV, and because the project uses a rolling release with no response to the report, no vendor-patched version can be identified; the independent assessment (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) rates confidentiality, integrity and availability impact as High, well above the 2.1 score published by the reporting source.