# CVE-2026-58449: txtai - Unauthenticated Remote Code Execution via Unsafe Reflection in API /reindex function Parameter

> Remote attackers can execute arbitrary code via unsafe reflection in the /reindex endpoint when authentication is disabled and the index is writable.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-m8p4-rrq5-qvmf

## What is CVE-2026-58449?

CVE-2026-58449 is a critical code injection vulnerability in neuml txtai, published on 30 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-58449?


## How do I fix CVE-2026-58449?

No fix has been published for CVE-2026-58449 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-58449 being exploited?

There is no known exploitation of CVE-2026-58449 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-58449 and fix it if it is affected.

What it is: CVE-2026-58449 is a critical code injection vulnerability in neuml txtai, published on 30 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-58449 in the wild and no public exploit code.

Affected product: neuml txtai. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-58449/ (Markdown: https://insights.sbomify.com/CVE-2026-58449/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-58449
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-58449
- OSV: https://osv.dev/vulnerability/CVE-2026-58449

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-58449/
Summaries are generated and may contain mistakes; the official description above is the record.