Description
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."
Published: 2026-07-04
Score: 2.3 Low
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability resides in the get_conversation_history function of smart_customer_service.py in ForceInjection AI‑fundermentals. It employs a weak or broken hash algorithm, classified under CWE-327 and CWE-328, which allows an attacker to manipulate session data used during conversation history retrieval. This weakness can lead to modification or forging of conversation identifiers and potentially unauthorized data access. The description explicitly notes that remote exploitation is feasible, although it requires a high degree of complexity and is considered difficult to achieve.

Affected Systems

ForceInjection AI‑fundermentals versions 2.0 and 3.0 are impacted. Vulnerability occurs within the Memory Recall Handler component of the smart_customer_service module. The patch identified by commit f57277fdd9ba373ace72d83c272023ec67f720d6 introduces session ownership verification in methods such as username and sessionowner.

Risk and Exploitability

The CVSS score of 2.3 indicates low overall severity, and the EPSS score of <1% suggests exploitation is unlikely. The vulnerability is not listed in the CISA KEV catalog. While the attack is possible, the combination of low severity, high attack complexity, and low exploitation probability makes active attacks uncommon. Nonetheless, applying the patch removes the weak hash and mitigates any potential exploitation risk.

Generated by OpenCVE AI on July 24, 2026 at 09:59 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the patch at commit f57277fdd9ba373ace72d83c272023ec67f720 to implement session‑related methods such as username and sessionowner, following the developer’s guidance.
  • Switch to a strong, collision‑resistant hash function (e.g., SHA‑256 or higher) when generating or validating conversation identifiers.
  • Audit the application for other instances of weak hash usage and ensure that all session handling functions enforce ownership verification and proper authentication controls.

Generated by OpenCVE AI on July 24, 2026 at 09:59 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 06 Jul 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Sat, 04 Jul 2026 14:30:00 +0000

Type Values Removed Values Added
Description 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."
Title ForceInjection AI-fundermentals Memory Recall smart_customer_service.py get_conversation_history weak hash
First Time appeared Forceinjection
Forceinjection ai-fundermentals
Weaknesses CWE-327
CWE-328
CPEs cpe:2.3:a:forceinjection:ai-fundermentals:*:*:*:*:*:*:*:*
Vendors & Products Forceinjection
Forceinjection ai-fundermentals
References
Metrics cvssV2_0

{'score': 2.1, 'vector': 'AV:N/AC:H/Au:S/C:P/I:N/A:N/E:POC/RL:OF/RC:C'}

cvssV3_0

{'score': 3.1, 'vector': 'CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C'}

cvssV3_1

{'score': 3.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C'}

cvssV4_0

{'score': 2.3, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P'}


Subscriptions

Forceinjection Ai-fundermentals
cve-icon MITRE

Status: PUBLISHED

Assigner: VulDB

Published:

Updated: 2026-07-06T19:05:32.208Z

Reserved: 2026-07-03T17:14:51.596Z

Link: CVE-2026-14630

cve-icon Vulnrichment

Updated: 2026-07-06T19:05:08.668Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-24T10:00:04Z

Weaknesses
  • CWE-327

    Use of a Broken or Risky Cryptographic Algorithm

  • CWE-328

    Use of Weak Hash