# CVE-2024-56179: Path traversal in n/a

> Attackers can write files to unexpected directories on victims' machines by tricking them into opening malicious MindManager files.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Aug 2025
- **Updated:** 22 Aug 2025
- **Also known as:** GHSA-4c8x-fgj4-4fr4

## What is CVE-2024-56179?

CVE-2024-56179 is a high-severity path traversal vulnerability in n/a, published on 22 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In MindManager Windows versions prior to 24.1.150, attackers could potentially write to unexpected directories in victims' machines via directory traversal if victims opened file attachments located in malicious mmap files.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2024-56179?


## How do I fix CVE-2024-56179?

No fix has been published for CVE-2024-56179 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-56179 being exploited?

There is no known exploitation of CVE-2024-56179 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-56179 and fix it if it is affected.

What it is: CVE-2024-56179 is a high-severity path traversal vulnerability in n/a, published on 22 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-56179 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-56179/ (Markdown: https://insights.sbomify.com/CVE-2024-56179/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-56179
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-56179
- OSV: https://osv.dev/vulnerability/CVE-2024-56179

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-56179/
Summaries are generated and may contain mistakes; the official description above is the record.