CVE-2026-43505: Medium severity Prosody prosody vulnerability
An issue was discovered in Prosody before 0.12.6 and 1.0.0 through 13.0.0 before 13.0.5, when modproxy65 is enabled. Because modproxy65 mishandles access control in the activation scenario, relaying of unauthenticated traffic can occur.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
alpine/prosodyto a version that resolves this vulnerability.Fixed in 13.0.5-r0 - Upgrade
Upgrade
debian/prosodyto a version that resolves this vulnerability.Fixed in 0.12.3-1+deb12u1 - Upgrade
Upgrade
debian/prosodyto a version that resolves this vulnerability.Fixed in 13.0.1-1+deb131u - Upgrade
Upgrade
debian/prosodyto a version that resolves this vulnerability.Fixed in 13.0.5-1 - Upgrade
Upgrade
debian/prosodyto a version that resolves this vulnerability.Fixed in 0.12.3-1+deb12u1Fixed in 13.0.1-1+deb131uFixed in 13.0.7-1 - Upgrade
Upgrade
Prosodyto a version that resolves this vulnerability.Fixed in 0.12.6 - Upgrade
Upgrade
Prosodyto a version that resolves this vulnerability.Fixed in 13.0.5
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43505?
CVE-2026-43505 is considered a medium severity vulnerability as it allows relaying of unauthenticated traffic due to access control mishandling.
How do I fix CVE-2026-43505?
To fix CVE-2026-43505, update Prosody to version 0.12.6 or 13.0.5 or later.
What versions of Prosody are affected by CVE-2026-43505?
CVE-2026-43505 affects Prosody versions prior to 0.12.6 and 1.0.0 through 13.0.0 before 13.0.5.
What does mod_proxy65 do that makes CVE-2026-43505 a concern?
Mod_proxy65 mishandles access control, which can lead to unauthorized access and relaying of unauthenticated traffic.
Is CVE-2026-43505 related to any specific module in Prosody?
Yes, CVE-2026-43505 is specifically related to the mod_proxy65 module in Prosody.