Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-0963: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in Arcadia Technology, LLC Crafty Controller

0
Critical
VulnerabilityCVE-2026-0963cvecve-2026-0963cwe-22
Published: Fri Jan 30 2026 (01/30/2026, 06:04:05 UTC)
Source: CVE Database V5
Vendor/Project: Arcadia Technology, LLC
Product: Crafty Controller

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.

AI-Powered Analysis

AILast updated: 02/06/2026, 08:40:27 UTC

Technical Analysis

CVE-2026-0963 is a critical security vulnerability classified under CWE-22 (Improper Limitation of a Pathname to a Restricted Directory, commonly known as path traversal) affecting Arcadia Technology, LLC's Crafty Controller product, specifically version 4.7.0. The vulnerability resides in the File Operations API Endpoint, where insufficient input validation allows an authenticated remote attacker to manipulate file path parameters. By exploiting this flaw, the attacker can traverse directories outside the intended restricted directory, enabling unauthorized file access, modification, or deletion. This can escalate to remote code execution (RCE) if the attacker replaces or tampers with executable files or scripts used by the system. The CVSS v3.1 score of 9.9 reflects the critical nature of this vulnerability, with an attack vector of network (AV:N), low attack complexity (AC:L), requiring privileges (PR:L) but no user interaction (UI:N). The scope is changed (S:C), indicating that exploitation affects resources beyond the initially vulnerable component. The impact on confidentiality and integrity is high, as sensitive files can be accessed or altered, and availability impact is low but present. No public exploits are known yet, but the severity and ease of exploitation make this a high-priority threat. The lack of available patches at the time of publication increases risk for affected users.

Potential 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.

Mitigation Recommendations

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.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitLab
Date Reserved
2026-01-14T20:14:16.821Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 697c4f63ac0632022232629b

Added to database: 1/30/2026, 6:27:47 AM

Last enriched: 2/6/2026, 8:40:27 AM

Last updated: 2/7/2026, 1:52:50 PM

Views: 32

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats