{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-40031 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-40031 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-40031 is a high-severity vulnerability in ufrisk MemProcFS, published on 8 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-40031 and fix it if it is affected.\n\nWhat it is: CVE-2026-40031 is a high-severity vulnerability in ufrisk MemProcFS, published on 8 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-40031 in the wild and no public exploit code.\n\nAffected product: ufrisk MemProcFS. 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-40031/ (Markdown: https://insights.sbomify.com/CVE-2026-40031/index.md)","id":"CVE-2026-40031","markdown":"https://insights.sbomify.com/CVE-2026-40031/index.md","name":"CVE-2026-40031","record":{"aliases":["GHSA-wxrw-fvc7-2xmx"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Memory forensics tool","requires_auth":"none","summary":"Attackers can achieve arbitrary code execution by placing malicious libraries in the working directory or manipulating environment variables.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"memprocfs","vendor":"ufrisk"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"MemProcFS before 5.17 contains multiple unsafe library-loading patterns that enable DLL and shared-library hijacking across six attack surfaces, including bare-name LoadLibraryU and dlopen calls without path qualification for vmmpyc, libMSCompression, and plugin DLLs. An attacker who places a malicious DLL or shared library in the working directory or manipulates LD_LIBRARY_PATH can achieve arbitrary code execution when MemProcFS loads.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"MemProcFS \u003c 5.17 DLL/Shared Library Hijacking","id":"CVE-2026-40031","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"UAC \u003c 3.3.0-rc1 Command Injection via Placeholder Substitution","id":"CVE-2026-40032"},"packages":[],"prev":{"headline":"parseusbs \u003c 1.9 Command Injection via Volume Path Argument","id":"CVE-2026-40030"},"products":["MemProcFS"],"published":"2026-04-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["ufrisk"]},"summary":"Attackers can achieve arbitrary code execution by placing malicious libraries in the working directory or manipulating environment variables.","url":"https://insights.sbomify.com/CVE-2026-40031/"}