CVE-2026-58449

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-01. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation1.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.4%
EPSS %ILE
71st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 30, 2026

Last Modified

July 14, 2026

Advisory Details (4)

Auto-updated Oct 10, 2026
Patch available. Sources: github_commit.
Web page

txtai - Unauthenticated Remote Code Execution via Unsafe Reflection in API /reindex function Parameter | Advisories | VulnCheck

https://www.vulncheck.com/advisories/txtai-unauthenticated-remote-code-execution-via-unsafe-reflection-in-api-reindex-function-parameter
Web page

[Security] RCE via __import__() in /reindex function parameter · Issue #1122 · neuml/txtai · GitHub

https://github.com/neuml/txtai/issues/1122
Web page

Add `reindex` parameter for API · Issue #1111 · neuml/txtai · GitHub

https://github.com/neuml/txtai/issues/1111
GitHub commit Patch Available

commit 11b32da720f0 (neuml/txtai)

Patch available: neuml/txtai v9.11.0 (contains commit 11b32da720f0)

https://github.com/neuml/txtai/commit/11b32da720f03276199ebc5583c15fc5d1ccafd3

Vendor Advisories for CVE-2026-58449(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 456 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 356 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-17 06:38 UTCEG score recompute
  2. 2026-10-17 06:38 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-16 16:43 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  4. 2026-10-16 07:20 UTCEG score recompute
  5. 2026-10-16 07:19 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  7. 2026-10-15 06:14 UTCEG score recompute
  8. 2026-10-15 06:14 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-14 16:33 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  10. 2026-10-14 01:52 UTCEG score recompute
  11. 2026-10-14 01:52 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  13. 2026-10-12 22:07 UTCEG score recompute
  14. 2026-10-12 22:06 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  16. 2026-10-12 15:53 UTCEG score recompute
  17. 2026-10-12 06:40 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-11 19:36 UTCEG score recompute
  19. 2026-10-11 16:52 UTCEG score recompute
  20. 2026-10-11 14:14 UTCEG score recompute
  21. 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  22. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  23. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  24. 2026-10-08 17:13 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  25. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.4% · 70th percentile
Show 75 more
  1. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  2. 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  3. 2026-10-03 14:26 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  4. 2026-10-02 17:56 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  5. 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  6. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  7. 2026-09-29 15:22 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  8. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  9. 2026-09-27 13:48 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  10. 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  11. 2026-09-24 14:04 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  12. 2026-09-23 17:54 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  13. 2026-09-23 11:16 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-09-23 07:15 UTCEG score recompute
  15. 2026-09-23 07:15 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-09-18 19:28 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  17. 2026-09-18 10:52 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-09-18 06:47 UTCEG score recompute
  19. 2026-09-18 06:47 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-09-17 19:31 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  21. 2026-09-16 14:08 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  22. 2026-09-16 05:15 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  23. 2026-09-15 03:11 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  24. 2026-09-14 08:21 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-09-14 04:33 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-09-14 00:46 UTCEG score recompute
  27. 2026-09-14 00:46 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-09-13 16:47 UTCEPSS rescoreEPSS 1.4% · 70th percentile
  29. 2026-09-13 13:07 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  30. 2026-09-13 09:14 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-09-12 15:07 UTCEG score recompute
  32. 2026-09-12 15:07 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-09-11 14:53 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  34. 2026-09-10 09:35 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  35. 2026-09-08 22:01 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  36. 2026-09-07 16:01 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  37. 2026-09-06 14:34 UTCEG score recompute
  38. 2026-09-06 14:34 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-09-06 13:47 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  40. 2026-09-04 05:07 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  41. 2026-09-02 14:12 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  42. 2026-09-01 13:54 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  43. 2026-09-01 04:40 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  44. 2026-08-31 02:11 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-08-30 22:22 UTCEG score recompute
  46. 2026-08-30 22:22 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-08-30 19:17 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  48. 2026-08-30 17:54 UTCEG score recompute
  49. 2026-08-30 17:54 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-08-30 01:22 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  51. 2026-08-28 21:42 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  52. 2026-08-28 02:50 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-08-27 22:38 UTCEG score recompute
  54. 2026-08-27 22:38 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-08-27 14:25 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  56. 2026-08-26 14:46 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  57. 2026-08-25 13:49 UTCEPSS rescoreEPSS 1.4% · 69th percentile
  58. 2026-08-25 04:40 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-08-25 00:53 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-08-24 21:05 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-08-24 15:22 UTCEG score recompute
  62. 2026-08-24 15:22 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-08-24 11:31 UTCEG score recompute
  64. 2026-08-24 11:31 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-08-24 04:21 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-08-23 23:39 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-08-23 19:51 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  68. 2026-08-23 16:03 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-08-23 12:15 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-08-23 08:26 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-08-23 04:34 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-08-23 00:46 UTCEG score recompute
  73. 2026-08-23 00:46 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  75. 2026-08-22 20:26 UTCGHSA enrichmentGHSA-m8p4-rrq5-qvmf · GitHub severity CRITICAL · GitHub CVSS 9.8

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58449?
CVE-2026-58449 is a critical-severity vulnerability; its CVE record was published on June 30, 2026. 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…
When was CVE-2026-58449 made public?
CVE-2026-58449 was made public on June 9, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on June 30, 2026. EchelonGraph's copy of the record carries a last-modified date of July 14, 2026; the record at its source may have been updated since.
Is CVE-2026-58449 actively exploited?
CVE-2026-58449 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (71st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58449?
CVE-2026-58449 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-58449?
A fix for CVE-2026-58449 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-58449 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-58449

Explore →

Is Your Infrastructure Affected by CVE-2026-58449?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs