ForceInjection AI-fundermentals 2.0/3.0 Memory Recall smart_customer_service.py get_conversation_history weak hash

Summaryinfo

A vulnerability categorized as problematic has been discovered in ForceInjection AI-fundermentals 2.0/3.0. Affected by this issue 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 results in weak hash. This vulnerability is identified as CVE-2026-14630. The attack can be executed remotely. Additionally, an exploit exists. A patch should be applied to remediate 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."

Detailsinfo

A vulnerability classified as problematic has been found in ForceInjection AI-fundermentals 2.0/3.0. Affected 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 with an unknown input leads to a weak hash vulnerability. CWE is classifying the issue as CWE-328. The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack). This is going to have an impact on confidentiality.

The advisory is available at github.com. This vulnerability is traded as CVE-2026-14630. The exploitability is told to be difficult. It is possible to launch the attack remotely. Technical details and a public exploit are known. This vulnerability is assigned to T1600.001 by the MITRE ATT&CK project.

The exploit is shared for download at github.com. It is declared as proof-of-concept. 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."

Applying the patch f57277fdd9ba373ace72d83c272023ec67f720d6 is able to eliminate this problem. The bugfix is ready for download at github.com.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Artificial Intelligence Software

Vendor

• ForceInjection

Name

• AI-fundermentals

Version

• 2.0
• 3.0

License

• open-source

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Submitinfo

Accepted

• Submit #845672: ForceInjection AI-fundermentals 5bb92c73a5aa0560c753beeb56e7ad4314dc8a7a Insecure Direct Object Reference (IDOR) / Cross-Tenant Data Expo (by Dem00000)

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion