CVE-2026-43504 Details
Description
An issue was discovered in Prosody before 0.12.6 and 1.0.0 through 13.0.0 before 13.0.5, when mod_proxy65 is enabled. Because mod_proxy65 mishandles access control in a paused scenario, relaying of unauthenticated traffic can occur.
A vulnerability allowing unauthenticated use of the SOCKS5 proxy module (mod_proxy65) has been identified in Prosody versions prior to 0.12.6 and 13.0.0 prior to 13.0.5. The issue arises from improper access control management in paused connections, enabling the relay of unauthenticated traffic through the proxy. This vulnerability requires knowledge of the proxy's domain and port, which defaults to port 5000, and can be exploited by skipping the initial discoverability stage of the protocol.
Users can upgrade to Prosody versions 0.12.6 or 13.0.5. If mod_proxy65 is not needed, it can be disabled, although this may impact certain file transfer functionalities.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed May 1, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://prosody.im/security/advisory_735dd9d3/ | [email protected] | MitigationPatchVendor Advisory |
| https://www.openwall.com/lists/oss-security/2026/05/01/5 | [email protected] | Mailing ListPatchThird Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-863 | Incorrect Authorization | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| prosody prosody | < 0.12.6 >= 13.0.0, < 13.0.5 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| May 1, 2026 | Initial Analysis | [email protected] |
| May 1, 2026 | New CVE Received | [email protected] |