# CVE-2026-24694: Other in Roland Cloud Manager

> Insecure DLL loading in Roland Cloud Manager allows attackers to execute arbitrary code with application privileges.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 3 Feb 2026
- **Updated:** 3 Feb 2026
- **Also known as:** GHSA-8w3q-29h2-426f

## What is CVE-2026-24694?

CVE-2026-24694 is a high-severity vulnerability in Roland Cloud Manager, published on 3 Feb 2026. 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

The installer for Roland Cloud Manager ver.3.1.19 and prior insecurely loads Dynamic Link Libraries (DLLs), which could allow an attacker to execute arbitrary code with the privileges of the application.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2026-24694?


## How do I fix CVE-2026-24694?

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

## Is CVE-2026-24694 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24694 and fix it if it is affected.

What it is: CVE-2026-24694 is a high-severity vulnerability in Roland Cloud Manager, published on 3 Feb 2026. 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-2026-24694 in the wild and no public exploit code.

Affected product: Roland Cloud Manager. 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-2026-24694/ (Markdown: https://insights.sbomify.com/CVE-2026-24694/index.md)
```

## Sources

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

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