Skip to main content
VulnerabilityPublished

CVE-2026-114497: DeusData codebase-memory-mcp · Missing Authorization

Affects DeusData codebase-memory-mcpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.5 Medium : upgrade to 0.9.1-rc.1 when convenient.

Data as of 20 Nov 2026, 20:14 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.5
Patch
Available – fixed in 0.9.1-rc.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade DeusData codebase-memory-mcp to 0.9.1-rc.1.

Affected software

ProductAffectedFixed in
DeusDatacodebase-memory-mcpAffected
  • <0.9.1-rc.1
Fixed in
  • 0.9.1-rc.1

AI-suggested

Upgrade to version 0.9.1-rc.1 or later, where the missing authorization check on Windows has been implemented to prevent unauthorized process termination. No additional mitigation is required once the update is applied.

Description

A missing authorization vulnerability in codebase-memory-mcp prior to version 0.9.1-rc.1 allows an attacker with local access on Windows to terminate arbitrary processes that the server user can terminate. This flaw exists in the optional graph UI's POST /api/process-kill route, which lacks an ownership check on Windows, potentially causing denial of service without data disclosure or modification. The issue is fixed in version 0.9.1-rc.1.

References

Community reviews

Loading reviews…