Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 17 Apr 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:ufrisk:memprocfs:*:*:*:*:*:*:*:* |
Thu, 09 Apr 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 09 Apr 2026 08:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ufrisk
Ufrisk memprocfs |
|
| Vendors & Products |
Ufrisk
Ufrisk memprocfs |
Wed, 08 Apr 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | MemProcFS < 5.17 DLL/Shared Library Hijacking | |
| Weaknesses | CWE-427 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-05-08T14:07:22.373Z
Reserved: 2026-04-08T13:36:52.082Z
Link: CVE-2026-40031
Updated: 2026-04-09T14:49:56.291Z
Status : Analyzed
Published: 2026-04-08T22:16:23.650
Modified: 2026-04-17T16:15:37.513
Link: CVE-2026-40031
No data.
OpenCVE Enrichment
Updated: 2026-04-09T08:25:51Z