CVE-2026-14630

LOWPre-NVD 3.13.1
EchelonGraph scoreMEDIUM confidence

Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-07-04. a secondary CVSS source baseline 3.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
3.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.1Exploit: Elevated riskExposed: 0

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

A vulnerability has been found in ForceInjection AI-fundermentals 2.0/3.0. Affected by this vulnerability is the function get_conversation_history of the file 08_agentic_system/memory/langchain/code/smart_customer_service.py of the component Memory Recall Handler. The manipulation leads to use of weak hash. Remote exploitation of the attack is possible. A high degree of complexity is needed for the attack. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The identifier of the patch is f57277fdd9ba373ace72d83c272023ec67f720d6. It is suggested to install a patch to address this issue. The project confirms (translated from Chinese): "We now require session ownership verification in methods such as username, sessionowner, etc., and we've chat()changed the generation of sessionowner to include verified user identity and security context metadata."

CVSS v3
3.1
EG Score
3.1(medium)
EG Risk
30(Track)
EG Risk 30/100SSVC: Track

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
Severity31% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

July 4, 2026

Last Modified

July 6, 2026

Vendor Advisories for CVE-2026-14630(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 44× 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.

  1. 2026-08-25 13:48 UTCEPSS rescore
  2. 2026-08-25 04:07 UTCEG score recompute
  3. 2026-08-25 04:07 UTCGHSA enrichment
  4. 2026-08-22 05:12 UTCEG score recompute
  5. 2026-08-22 05:12 UTCGHSA enrichment
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-19 17:03 UTCEPSS rescore
  9. 2026-08-19 05:29 UTCEG score recompute
  10. 2026-08-19 05:29 UTCGHSA enrichment
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 06:30 UTCEG score recompute
  14. 2026-08-16 06:30 UTCGHSA enrichment
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 07:34 UTCEG score recompute
  19. 2026-08-13 07:34 UTCGHSA enrichment
  20. 2026-08-12 13:50 UTCEPSS rescore
  21. 2026-08-10 23:59 UTCEPSS rescore
  22. 2026-08-10 08:06 UTCEG score recompute
  23. 2026-08-10 08:06 UTCGHSA enrichment
  24. 2026-08-09 13:46 UTCEPSS rescore
  25. 2026-08-08 16:37 UTCEPSS rescore
Show 54 more
  1. 2026-08-07 09:10 UTCEG score recompute
  2. 2026-08-07 09:10 UTCGHSA enrichment
  3. 2026-08-06 13:46 UTCEPSS rescore
  4. 2026-08-05 19:17 UTCEPSS rescore
  5. 2026-08-04 15:09 UTCEPSS rescore
  6. 2026-08-04 10:38 UTCEPSS rescore
  7. 2026-08-04 10:15 UTCEG score recompute
  8. 2026-08-04 10:15 UTCGHSA enrichment
  9. 2026-08-03 10:35 UTCEPSS rescore
  10. 2026-08-02 02:26 UTCEPSS rescore
  11. 2026-08-01 10:44 UTCEG score recompute
  12. 2026-08-01 10:44 UTCGHSA enrichment
  13. 2026-08-01 04:15 UTCEPSS rescore
  14. 2026-07-30 16:27 UTCEPSS rescore
  15. 2026-07-30 01:30 UTCEPSS rescore
  16. 2026-07-29 11:49 UTCEG score recompute
  17. 2026-07-29 11:49 UTCGHSA enrichment
  18. 2026-07-28 15:36 UTCEPSS rescore
  19. 2026-07-27 14:13 UTCEPSS rescore
  20. 2026-07-26 14:54 UTCEPSS rescore
  21. 2026-07-26 14:54 UTCEPSS rescore
  22. 2026-07-26 12:53 UTCEG score recompute
  23. 2026-07-26 12:53 UTCGHSA enrichment
  24. 2026-07-25 14:17 UTCEPSS rescore
  25. 2026-07-24 14:17 UTCEPSS rescore
  26. 2026-07-23 14:18 UTCEPSS rescore
  27. 2026-07-23 03:05 UTCEG score recompute
  28. 2026-07-22 14:08 UTCEPSS rescore
  29. 2026-07-21 15:24 UTCEPSS rescore
  30. 2026-07-20 17:08 UTCEPSS rescore
  31. 2026-07-19 14:30 UTCEPSS rescore
  32. 2026-07-19 02:28 UTCEPSS rescore
  33. 2026-07-18 10:04 UTCEPSS rescore
  34. 2026-07-16 17:02 UTCEPSS rescore
  35. 2026-07-16 10:04 UTCGHSA enrichment
  36. 2026-07-15 16:57 UTCEPSS rescore
  37. 2026-07-15 02:00 UTCEPSS rescore
  38. 2026-07-13 22:30 UTCEPSS rescore
  39. 2026-07-13 11:09 UTCGHSA enrichment
  40. 2026-07-13 06:12 UTCEPSS rescore
  41. 2026-07-12 05:46 UTCEPSS rescore
  42. 2026-07-11 08:27 UTCEPSS rescore
  43. 2026-07-10 12:13 UTCGHSA enrichment
  44. 2026-07-09 19:10 UTCEPSS rescore
  45. 2026-07-08 15:15 UTCEPSS rescore
  46. 2026-07-08 15:15 UTCEPSS rescore
  47. 2026-07-07 13:18 UTCGHSA enrichment
  48. 2026-07-06 21:35 UTCNVD updateCVSS v4 → 1.3
  49. 2026-07-06 19:44 UTCMITRE cvelistV5CVSS v4 → 2.3
  50. 2026-07-06 16:27 UTCEPSS rescore
  51. 2026-07-06 02:23 UTCEPSS rescore
  52. 2026-07-04 16:28 UTCNVD updateCVSS v4 → 1.3
  53. 2026-07-04 14:22 UTCEG score recompute
  54. 2026-07-04 14:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-14630?
CVE-2026-14630 is a low vulnerability published on July 4, 2026. A vulnerability has been found in ForceInjection AI-fundermentals 2.0/3.0. Affected by this vulnerability is the function getconversationhistory of the file 08agenticsystem/memory/langchain/code/smartcustomerservice.py of the component Memory Recall Handler. The manipulation leads to use of weak…
When was CVE-2026-14630 disclosed?
CVE-2026-14630 was first published in the National Vulnerability Database on July 4, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14630 actively exploited?
CVE-2026-14630 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 86.1% of all scored CVEs.
What is the CVSS score of CVE-2026-14630?
CVE-2026-14630 has a CVSS v3 base score of 3.1 (NVD).
How do I remediate CVE-2026-14630?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14630, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-14630?

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