# CVE-2026-38945: Command injection in n/a

> Attackers can execute arbitrary code via crafted paths in Raynet rvia due to improper handling of search criteria in the Java find command.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-6j46-7pm3-f2jp

## What is CVE-2026-38945?

CVE-2026-38945 is a high-severity command injection vulnerability in n/a, published on 27 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Command injection in Raynet rvia version 12.6 Update 8 and previous versions allows adversaries to execute arbitrary code via a crafted path that matches the improperly terminated search criteria of rvia's Java search using the find command.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2026-38945 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-38945 exists.

Public exploit code:

- https://github.com/Wise-Security/CVE-2026-38945 (github_poc): https://github.com/Wise-Security/CVE-2026-38945

## Fix prompt for AI coding agents

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

What it is: CVE-2026-38945 is a high-severity command injection vulnerability in n/a, published on 27 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-38945 exists.

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-2026-38945/ (Markdown: https://insights.sbomify.com/CVE-2026-38945/index.md)
```

## Sources

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

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