The vulnerability in txtai (<=9.10.0) involves improper control of code generation through the /reindex API endpoint. The function parameter is resolved using txtai.util.Resolver, which performs __import__ and getattr on a caller-supplied dotted path without any allowlist, enabling arbitrary callable execution. When the API is exposed without authentication and the index is writable, a remote attacker can specify dangerous callables such as subprocess.getoutput, resulting in remote code execution as the server process. Exploitation requires specific deployment conditions that are not default. The fix introduces a configuration flag that restricts access to the /reindex endpoint.

Successful exploitation allows a remote attacker to achieve remote code execution on the server running txtai, with full privileges of the server process. This can lead to complete compromise of the affected system, including confidentiality, integrity, and availability impacts. The vulnerability requires the API to be exposed without authentication and the index to be writable, which are not default configurations.

A fix is available in the form of a commit after version 9.10.0 that gates the /reindex endpoint behind a new configuration flag. Users should upgrade to a version including this fix or apply the commit to restrict access to the endpoint. Additionally, enabling TOKEN-based authentication and ensuring the index is not writable unless necessary will mitigate the risk. Patch status is not explicitly confirmed in the advisory; users should consult the vendor repository or advisory for the exact fixed version and apply the fix accordingly.