CVE-2026-25879

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Langroid is a framework for building large-language-model-powered applications. Prior to version 0.63.0, SQLChatAgent executes SQL produced by an LLM, which is influenceable by prompt injection. When configured with a database role that has privileges enabling code execution or filesystem access (e.g., PostgreSQL pg_execute_server_program, MySQL FILE, MSSQL xp_cmdshell), an attacker who can shape the agent's input — including indirectly via data returned to the LLM — can coerce execution of dialect-specific primitives such as COPY ... FROM PROGRAM, achieving RCE on the database host. Fixed in v0.63.0 by defaulting SQLChatAgent to a SELECT-only sqlglot-parsed statement allowlist with a dialect-aware dangerous-pattern blocklist; allow_dangerous_operations=True restores the previous unrestricted behavior for trusted deployments.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
33.1%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 2, 2026

Advisory Details (1)

Auto-updated Jun 20, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Security Vulnerability Report: Prompt to SQL Injection leading to RCE in latest Langroid · Advisory · langroid/langroid · GitHub

https://github.com/langroid/langroid/security/advisories/GHSA-mxfr-6hcw-j9rq

Vendor Advisories for CVE-2026-25879(1)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
langroid0.1.100 ... 0.9.5 (530 versions)0.63.0

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 87× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 207 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-25879?
CVE-2026-25879 is a critical vulnerability published on May 27, 2026. Langroid is a framework for building large-language-model-powered applications. Prior to version 0.63.0, SQLChatAgent executes SQL produced by an LLM, which is influenceable by prompt injection. When configured with a database role that has privileges enabling code execution or filesystem access…
When was CVE-2026-25879 disclosed?
CVE-2026-25879 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-25879 actively exploited?
CVE-2026-25879 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-25879?
CVE-2026-25879 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-25879?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25879, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-25879

Explore →

Is Your Infrastructure Affected by CVE-2026-25879?

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