dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-7212

HIGH · 7.3 CVSS v3.1 Published 2026-04-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A security vulnerability has been detected in edvardlindelof notes-mcp up to 0.1.4. This affects an unknown function of the file notes_mcp.py. The manipulation of the argument root_dir/path leads to path traversal. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Path traversal vulnerability in notes-mcp (versions up to 0.1.4) allows attackers to access files outside the intended directory through manipulation of the root_dir/path arguments in notes_mcp.py. The vulnerability is remotely exploitable and a public exploit exists, indicating active risk.

MitigationImplement strict input validation and sanitization for path arguments, ensuring paths are normalized and constrained within allowed directories. Use allowlisting or chroot-style containment to prevent directory escape.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if notes-mcp is installed
    Run 'pip show notes-mcp' or check your package manager for the notes-mcp package
    Affected if The package is not installed or not present in your environment
  2. Identify the installed version
    Run 'pip show notes-mcp' and look for the Version field, or check your lock file/package.json for the version number
    Affected if The installed version is 0.1.4 or any version lower (e.g., 0.1.3, 0.1.2, etc.)
  3. Locate the vulnerable notes_mcp.py file
    Find the notes_mcp.py file in your installation (typically in site-packages or your project dependencies)
    Affected if The file exists and contains code that handles root_dir or path arguments for file operations
  4. Verify the path traversal vulnerability is exploitable
    Examine the notes_mcp.py code to see if it processes user-supplied paths without proper validation using os.path.realpath() or equivalent path sanitization
    Affected if The code accepts path arguments and lacks validation to prevent ../ sequences from escaping the intended directory
  5. Confirm the application is using the vulnerable file handling
    Check your application logs or code that calls notes-mcp to see if it passes root_dir or path parameters to the MCP server
    Affected if Your implementation passes directory paths to notes-mcp without your own validation layer

You are affected if notes-mcp version 0.1.4 or lower is installed AND your environment passes unsanitized path arguments to the application.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization for path arguments, ensuring paths are normalized and constrained within allowed directories. Use allowlisting or chroot-style containment to prevent directory escape.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7212 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7212 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data