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

> An attacker can execute arbitrary code by placing a malicious executable in a directory path with spaces, bypassing intended execution paths.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Nov 2025
- **Updated:** 25 Nov 2025
- **Also known as:** GHSA-g6mh-6454-qm24

## What is CVE-2024-47856?

CVE-2024-47856 is a critical path traversal vulnerability in n/a, published on 24 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In RSA Authentication Agent before 7.4.7, service paths and shortcut paths may be vulnerable to path interception if the path has one or more spaces and is not surrounded by quotation marks. An adversary can place an executable in a higher-level directory of the path, and Windows will resolve that executable instead of the intended executable.

Weakness: CWE-23 (Relative Path Traversal)

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

It affects 1 product.


Products: Rsa Authentication Agent for Windows.

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

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

## Is CVE-2024-47856 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-0931](https://insights.sbomify.com/CVE-2013-0931/): Security feature bypass in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47856 is a critical path traversal vulnerability in n/a, published on 24 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47856 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-47856/ (Markdown: https://insights.sbomify.com/CVE-2024-47856/index.md)
```

## Sources

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

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