CVE-2026-14630

LOWPre-NVD 3.13.1—
EchelonGraph scoreHIGH 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
Elevated
3.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.1Exploit: NoneExposed: 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(high)
EG Risk
—
EPSS
5.6%
KEV
Not listed

Published

July 4, 2026

Last Modified

July 6, 2026

References (8)

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 8× in last 7d / 27× 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-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:30 UTCEPSS rescore
  5. 2026-07-19 02:28 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-16 17:02 UTCEPSS rescore
  8. 2026-07-16 10:04 UTCGHSA enrichment
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 02:00 UTCEPSS rescore
  11. 2026-07-13 22:30 UTCEPSS rescore
  12. 2026-07-13 11:09 UTCGHSA enrichment
  13. 2026-07-13 06:12 UTCEPSS rescore
  14. 2026-07-12 05:46 UTCEPSS rescore
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-10 12:13 UTCGHSA enrichment
  17. 2026-07-09 19:10 UTCEPSS rescore
  18. 2026-07-08 15:15 UTCEPSS rescore
  19. 2026-07-08 15:15 UTCEPSS rescore
  20. 2026-07-07 13:18 UTCGHSA enrichment
  21. 2026-07-06 21:35 UTCNVD updateCVSS v4 → 1.3
  22. 2026-07-06 19:44 UTCMITRE cvelistV5CVSS v4 → 2.3
  23. 2026-07-06 16:27 UTCEPSS rescore
  24. 2026-07-06 02:23 UTCEPSS rescore
  25. 2026-07-04 16:28 UTCNVD updateCVSS v4 → 1.3
Show 2 more
  1. 2026-07-04 14:22 UTCEG score recompute
  2. 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 5.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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.

Start Free Scan →Browse All CVEs