CVE-2026-58449
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedtxtai 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencetxtai through 9.10.0 exposes an unauthenticated /reindex API endpoint where the function body parameter is resolved through txtai.util.Resolver, which performs __import__ and getattr on caller-supplied dotted paths without any allowlist. When the API is exposed without a TOKEN configured (authentication is opt-in) and the index is writable, attackers can specify arbitrary callables like subprocess.getoutput to achieve remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if TOKEN authentication is configuredInspect environment variables for TOKEN or check configuration files for auth settingsAffected if No TOKEN is set, meaning the API accepts unauthenticated requests
-
Verify if API is network-exposedCheck startup configuration or running service to see if txtai binds to a non-localhost interface (0.0.0.0 or external IP)Affected if API is accessible from the network without authentication
-
Determine if index is writableCheck index path permissions or configuration setting for write access on the index directoryAffected if Index directory or storage is writable by the API process
-
Check if /reindex endpoint is accessibleVerify the API is running and the /reindex endpoint is reachable without credentialsAffected if /reindex endpoint responds to requests without authentication
Environment is affected if the txtai API is network-exposed without TOKEN authentication configured AND the index is writable, allowing arbitrary code execution via the /reindex endpoint.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedEnable authentication by setting a TOKEN, ensure the API is not publicly exposed, or upgrade to the fixed version and configure the new reindex configuration flag to control endpoint access.
txtai 9.10.1 or later
- Upgrade txtai to a version that includes the fix from commit 11b32da (version 9.10.1 or later)
- If immediate upgrade is not possible, ensure the API is not exposed publicly and a TOKEN is configured for authentication
- If writable index is not required in deployment, configure it as read-only to reduce attack surface
- After upgrading, configure the new reindex configuration flag appropriately to control access to the /reindex endpoint
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58449 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-58449 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data