CVE-2026-32733: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in squidowl halloy
Halloy is an IRC application written in Rust. Prior to commit 0f77b2cfc5f822517a256ea5a4b94bad8bfe38b6, the DCC receive flow did not sanitize filenames from incoming `DCC SEND` requests. A remote IRC user could send a filename with path traversal sequences like `../../.ssh/authorized_keys` and the file would be written outside the user's configured `save_directory`. With auto-accept enabled this required zero interaction from the victim. Starting with commit 0f77b2cfc5f822517a256ea5a4b94bad8bfe38b6, all identified code paths sanitize filenames through a shared `sanitize_filename` function.
AI Analysis
Technical Summary
CVE-2026-32733 is a path traversal vulnerability (CWE-22) identified in Halloy, an IRC client written in Rust and maintained by squidowl. The flaw exists in the DCC (Direct Client-to-Client) file receive flow, where filenames from incoming DCC SEND requests were not properly sanitized before being used to write files to disk. Specifically, attackers could include path traversal sequences such as '../../.ssh/authorized_keys' in the filename, causing the application to write files outside the user-configured save directory. This could lead to overwriting or creating arbitrary files on the victim's system. The vulnerability is particularly dangerous when the auto-accept feature for DCC SEND is enabled, as it requires no user interaction or authentication, allowing remote attackers to exploit it silently. The issue was fixed starting with commit 0f77b2cfc5f822517a256ea5a4b94bad8bfe38b6 by introducing a centralized filename sanitization function that cleans all relevant code paths. The CVSS 4.0 base score is 8.7, reflecting high severity due to network attack vector, no required privileges or user interaction, and high impact on integrity. No known exploits have been reported in the wild as of the publication date. The vulnerability affects all Halloy versions up to and including 2026.4.
Potential Impact
The primary impact of this vulnerability is the potential for remote attackers to write arbitrary files anywhere on the victim's filesystem, bypassing intended directory restrictions. This can lead to unauthorized modification or creation of sensitive files, such as SSH authorized_keys, configuration files, or scripts, potentially enabling further system compromise or persistent access. The lack of required authentication and user interaction, combined with network-based exploitation, increases the risk of widespread exploitation in environments where Halloy is used with auto-accept enabled. Organizations relying on Halloy for IRC communications, especially those in sensitive or high-security environments, face risks of data integrity loss, unauthorized access, and potential lateral movement within networks. Although no active exploits are currently known, the vulnerability's characteristics make it a critical concern for affected users.
Mitigation Recommendations
1. Upgrade Halloy to a version released after commit 0f77b2cfc5f822517a256ea5a4b94bad8bfe38b6 or any version later than 2026.4 that includes the filename sanitization fix. 2. Temporarily disable the auto-accept feature for DCC SEND requests to prevent automatic file writes without user validation. 3. Implement network-level controls to restrict IRC traffic to trusted sources, reducing exposure to malicious DCC SEND requests. 4. Monitor filesystem changes in directories commonly targeted by path traversal attacks, such as user home directories and SSH configuration folders. 5. Educate users about the risks of enabling auto-accept and encourage manual validation of incoming file transfers. 6. Consider deploying host-based intrusion detection systems (HIDS) to alert on suspicious file writes outside expected directories. 7. Review and harden file system permissions to limit the impact of unauthorized file writes by applications.
Affected Countries
United States, Germany, United Kingdom, France, Japan, South Korea, Canada, Australia, Netherlands, Sweden
CVE-2026-32733: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in squidowl halloy
Description
Halloy is an IRC application written in Rust. Prior to commit 0f77b2cfc5f822517a256ea5a4b94bad8bfe38b6, the DCC receive flow did not sanitize filenames from incoming `DCC SEND` requests. A remote IRC user could send a filename with path traversal sequences like `../../.ssh/authorized_keys` and the file would be written outside the user's configured `save_directory`. With auto-accept enabled this required zero interaction from the victim. Starting with commit 0f77b2cfc5f822517a256ea5a4b94bad8bfe38b6, all identified code paths sanitize filenames through a shared `sanitize_filename` function.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-32733 is a path traversal vulnerability (CWE-22) identified in Halloy, an IRC client written in Rust and maintained by squidowl. The flaw exists in the DCC (Direct Client-to-Client) file receive flow, where filenames from incoming DCC SEND requests were not properly sanitized before being used to write files to disk. Specifically, attackers could include path traversal sequences such as '../../.ssh/authorized_keys' in the filename, causing the application to write files outside the user-configured save directory. This could lead to overwriting or creating arbitrary files on the victim's system. The vulnerability is particularly dangerous when the auto-accept feature for DCC SEND is enabled, as it requires no user interaction or authentication, allowing remote attackers to exploit it silently. The issue was fixed starting with commit 0f77b2cfc5f822517a256ea5a4b94bad8bfe38b6 by introducing a centralized filename sanitization function that cleans all relevant code paths. The CVSS 4.0 base score is 8.7, reflecting high severity due to network attack vector, no required privileges or user interaction, and high impact on integrity. No known exploits have been reported in the wild as of the publication date. The vulnerability affects all Halloy versions up to and including 2026.4.
Potential Impact
The primary impact of this vulnerability is the potential for remote attackers to write arbitrary files anywhere on the victim's filesystem, bypassing intended directory restrictions. This can lead to unauthorized modification or creation of sensitive files, such as SSH authorized_keys, configuration files, or scripts, potentially enabling further system compromise or persistent access. The lack of required authentication and user interaction, combined with network-based exploitation, increases the risk of widespread exploitation in environments where Halloy is used with auto-accept enabled. Organizations relying on Halloy for IRC communications, especially those in sensitive or high-security environments, face risks of data integrity loss, unauthorized access, and potential lateral movement within networks. Although no active exploits are currently known, the vulnerability's characteristics make it a critical concern for affected users.
Mitigation Recommendations
1. Upgrade Halloy to a version released after commit 0f77b2cfc5f822517a256ea5a4b94bad8bfe38b6 or any version later than 2026.4 that includes the filename sanitization fix. 2. Temporarily disable the auto-accept feature for DCC SEND requests to prevent automatic file writes without user validation. 3. Implement network-level controls to restrict IRC traffic to trusted sources, reducing exposure to malicious DCC SEND requests. 4. Monitor filesystem changes in directories commonly targeted by path traversal attacks, such as user home directories and SSH configuration folders. 5. Educate users about the risks of enabling auto-accept and encourage manual validation of incoming file transfers. 6. Consider deploying host-based intrusion detection systems (HIDS) to alert on suspicious file writes outside expected directories. 7. Review and harden file system permissions to limit the impact of unauthorized file writes by applications.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-13T15:02:00.627Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69bdda57b462d409683a8c69
Added to database: 3/20/2026, 11:37:59 PM
Last enriched: 3/28/2026, 9:26:14 PM
Last updated: 5/2/2026, 2:27:57 PM
Views: 47
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.