CVE-2026-0963VulnerabilityPublished 30 Jan 2026Updated 2 Feb 2026

CVE-2026-0963: Arcadia Technology Crafty Controller · Path Traversal

Affects Arcadia Technology Crafty ControllerSource CVE Database V5

Not known to be exploited · CVSS 9.9 Critical : upgrade to 4.8.0 as a priority.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

9.9Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.8.0

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: High
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Arcadia Technology Crafty Controller to 4.8.0.

Affected software

Product	Affected	Fixed in
Arcadia Technology, LLCCrafty Controller	Affected >=4.7.0 <4.8.0	Fixed in 4.8.0
GitHubcrafty-controller/crafty`pkg:github/crafty-controller/crafty`Other threats	Affected =4.7.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately restrict access to the File Operations API Endpoint to only trusted and necessary users, employing network segmentation and firewall rules. 2. Enforce strong authentication and authorization controls, including multi-factor authentication, to reduce the risk of credential compromise. 3. Monitor and log all file operation requests and responses for unusual or unauthorized activity, enabling rapid detection of exploitation attempts. 4. Implement input validation and sanitization at the application layer to detect and block path traversal patterns if possible via WAF or custom rules. 5. Isolate the Crafty Controller environment to minimize lateral movement in case of compromise. 6. Engage with Arcadia Technology for patches or updates addressing this vulnerability and plan immediate deployment once available. 7. Conduct regular security audits and penetration testing focusing on API endpoints and file system access controls. 8. Educate users and administrators about the risks of credential theft and the importance of secure password practices. 9. Consider temporary compensating controls such as disabling the vulnerable API endpoint if feasible without disrupting critical operations.

Description

An input neutralization vulnerability in the File Operations API Endpoint component of Crafty Controller allows a remote, authenticated attacker to perform file tampering and remote code execution via path traversal.

Impact

For European organizations, the impact of CVE-2026-0963 is significant, especially for those relying on Crafty Controller 4.7.0 in industrial automation, IoT, or critical infrastructure environments. Successful exploitation can lead to unauthorized disclosure of sensitive data, manipulation of configuration or operational files, and execution of arbitrary code, potentially disrupting operations or causing safety hazards. This could result in operational downtime, financial losses, regulatory penalties under GDPR if personal data is compromised, and reputational damage. The requirement for authentication means insider threats or compromised credentials could be leveraged, increasing risk in environments with weak access controls. The partial availability impact could affect service continuity, critical in manufacturing or energy sectors prevalent in Europe. The absence of known exploits does not reduce urgency, as the vulnerability’s characteristics make it a likely target for attackers once exploit code becomes available.

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

gitlab.com/crafty-controller/crafty-4/-/issues/660 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Feb 2026, 08:40 UTC

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats