{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14630 exists.","fix":"No fix has been published for CVE-2026-14630 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-14630 is a low-severity vulnerability in ForceInjection AI-fundermentals, published on 4 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-14630 and fix it if it is affected.\n\nWhat it is: CVE-2026-14630 is a low-severity vulnerability in ForceInjection AI-fundermentals, published on 4 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-14630 exists.\n\nAffected product: ForceInjection AI-fundermentals. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-14630/ (Markdown: https://insights.sbomify.com/CVE-2026-14630/index.md)","id":"CVE-2026-14630","markdown":"https://insights.sbomify.com/CVE-2026-14630/index.md","name":"CVE-2026-14630","record":{"aliases":["GHSA-g4xw-pv27-8m29"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"AI agent framework","requires_auth":"low_privilege","summary":"Attackers can bypass session ownership verification in the AI agent's memory recall handler due to weak hashing, potentially accessing unauthorized conversation history.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":2.3,"severity":"low","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-328","name":"Use of Weak Hash"},{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"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.\"","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"ForceInjection AI-fundermentals Memory Recall smart_customer_service.py get_conversation_history weak hash","id":"CVE-2026-14630","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"webpack-dev-server vulnerable to denial of service via a malformed Host or Origin header","id":"CVE-2026-14631"},"packages":[],"prev":{"headline":"RT-Thread Parameter lwp_syscall.c sys_ioctl divide by zero","id":"CVE-2026-14629"},"products":["AI-fundermentals"],"published":"2026-07-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-06","vendors":["ForceInjection"]},"summary":"Attackers can bypass session ownership verification in the AI agent's memory recall handler due to weak hashing, potentially accessing unauthorized conversation history.","url":"https://insights.sbomify.com/CVE-2026-14630/"}