dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-8217

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A security flaw has been discovered in Industrial Application Software IAS Canias ERP 8.03. Impacted is the function Runtime.getRuntime.exec of the component RMI Interface. Performing a manipulation of the argument troiaCode results in os command injection. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

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 · high confidence

OS command injection vulnerability in IAS Canias ERP 8.03 RMI Interface. The troiaCode parameter passed to Runtime.getRuntime.exec is not properly sanitized, allowing remote attackers to execute arbitrary operating system commands. The exploit is publicly available and the vendor did not respond to disclosure.

MitigationImplement strict input validation on the troiaCode parameter before passing to Runtime.getRuntime.exec; preferably refactor to use ProcessBuilder with argument array instead of shell execution to eliminate shell injection vectors. Network segmentation and RMI authentication should be applied as compensating controls until the fix is deployed.

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Canias ERP is installed
    Check for running processes or installed services named 'canias', 'ias', or look for the installation directory typically under C:\IAS or /opt/ias on Linux systems
    Affected if Canias ERP software is present and running
  2. Verify the installed version
    Check the version information in the application or installation directory - look for version files, about dialogs, or check the IAS executable version property
    Affected if Version is 8.03 or falls within the 8.03 release line
  3. Confirm RMI interface is enabled and exposed
    Check network listening ports - RMI typically uses ports 1098-1099 or custom ports. Use 'netstat -an' or 'ss -tlnp' to identify open ports associated with the IAS process
    Affected if RMI service port is listening and accessible from network
  4. Identify RMI service exposure
    Review firewall rules and network configuration to determine if RMI ports are exposed to untrusted networks. Check if the server is directly accessible from the internet or DMZ
    Affected if RMI interface is reachable from untrusted networks or the internet
  5. Inspect application logs for troiaCode parameter usage
    Search application logs for 'troiaCode' parameter entries, particularly any unusual or suspicious command patterns. Check logs in the IAS logs directory for failed command injection attempts or errors
    Affected if Logs contain suspicious troiaCode parameter values or evidence of injection attempts
  6. Check for signs of compromise
    Review system logs and IAS audit logs for unexpected command execution, new user accounts, or unauthorized file modifications. Check for reverse shells or unexpected network connections
    Affected if Evidence of unauthorized command execution or unexpected system changes exists

The environment is affected if Canias ERP version 8.03 is installed and the RMI interface is network-accessible, allowing remote attackers to inject commands via the troiaCode parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation on the troiaCode parameter before passing to Runtime.getRuntime.exec; preferably refactor to use ProcessBuilder with argument array instead of shell execution to eliminate shell injection vectors. Network segmentation and RMI authentication should be applied as compensating controls until the fix is deployed.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8217 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8217 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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