Approved changes feed: RSS · Atom
cpe:2.3:a:neuml:txtai:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Neuml (8cf9a422-fff9-5be3-846b-1291e9db1a14) |
|---|---|
| Product | Txtai (c3365fd4-d0a6-5b94-8ec2-203c2e4aa06e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-58449 |
vulnerable | 2026-07-29 01:03:16.813210 |
txtai - Unauthenticated Remote Code Execution via Unsafe Reflection in API /reindex function Parameter
CRITICAL (9.8)
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.
Published: 2026-06-30T21:06:47.254Z
Updated: 2026-07-14T22:03:04.255Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.