Vulnerability Description
txtai through 9.10.0, fixed in commit 11b32da, exposes an API /reindex endpoint whose function body parameter is resolved through txtai.util.Resolver, which performs __import__ and getattr on the caller-supplied dotted path with no allowlist. When the API is exposed with no TOKEN configured (authentication is opt-in, so all endpoints are unauthenticated) and the index is configured writable, a remote attacker can set function to an arbitrary callable such as subprocess.getoutput, achieving remote code execution as the server process during reindexing. Exploitation requires those deployment conditions (API exposed, no TOKEN, writable index); it is not the default configuration. The fix gates the endpoint behind a new reindex configuration flag.
CVSS Score
CRITICAL
Related Weaknesses (CWE)
References
- https://github.com/neuml/txtai/commit/11b32da720f03276199ebc5583c15fc5d1ccafd3
- https://github.com/neuml/txtai/issues/1111
- https://github.com/neuml/txtai/issues/1122
- https://www.vulncheck.com/advisories/txtai-unauthenticated-remote-code-execution
FAQ
What is CVE-2026-58449?
CVE-2026-58449 is a vulnerability with a CVSS score of 9.8 (CRITICAL). txtai through 9.10.0, fixed in commit 11b32da, exposes an API /reindex endpoint whose function body parameter is resolved through txtai.util.Resolver, which performs __import__ and getattr on the call...
How severe is CVE-2026-58449?
CVE-2026-58449 has been rated CRITICAL with a CVSS base score of 9.8/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2026-58449?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.