CVE-2026-38945
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 · uneditedCommand 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.
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 confidenceCommand injection vulnerability in Raynet rvia version 12.6 Update 8 and prior allows remote attackers to execute arbitrary OS commands by supplying a crafted path that exploits improperly terminated search criteria when the application's Java search feature invokes the find command.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Raynet rvia versionLocate the rvia application and check its version information. This is typically available in the application's About dialog, an installer log, or a version file within the rvia installation directory.Affected if The installed version is 12.6 Update 8 or any version prior to it.
-
Confirm Java search feature is enabledLocate the application's configuration files or settings that control the Java search functionality. Look for options related to search indexing, file searching, or the find command integration.Affected if The Java search feature is enabled and accessible to users who can supply path inputs.
-
Verify search feature invokes find commandInspect application logs, configuration files, or runtime behavior to confirm that the search feature executes the OS find command when processing search requests.Affected if The application directly invokes the find command with user-supplied path parameters without proper sanitization.
-
Review access controls on search interfaceCheck whether the search functionality is exposed to unauthenticated or low-privilege users, or if it can be reached remotely without additional authentication layers.Affected if The search interface is accessible to remote or untrusted users without strict access restrictions.
A system is affected if it runs Raynet rvia version 12.6 Update 8 or prior AND has the Java search feature enabled and accessible, allowing user-supplied paths to reach the underlying find command.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of rvia beyond 12.6 Update 8; if no patch available, restrict access to the application interface and implement strict input validation/sanitization on all path parameters before they are passed to the find command.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38945 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-38945 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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