Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 6.5

How to Fix CVE-2026-43505: Prosody (Bundle Sibling)

By Sai Kiran Pandrala

Last verified: 2026-05-25

CVE-2026-43505 is a sibling vulnerability in the same vendor advisory as CVE-2026-43504. Applying the patched build named in the primary write-up closes this CVE as well.

⚡ At a glance
SeverityCVSS 6.5 - Medium
Actively exploited?Not currently in CISA KEV
AffectedSame as the bundle - see CVE-2026-43504
Fixed inSame patched build as CVE-2026-43504 (See vendor advisory)
Type (CWE)CWE-420: CWE-420 Unprotected Alternate Channel

What's different about CVE-2026-43505?

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 the activation scenario, relaying of unauthenticated traffic can occur.

The technical impact and remediation are identical to the primary CVE in the bundle. The same vendor patch closes both.

How to fix CVE-2026-43505

Apply the patched build per the primary write-up: How to Fix CVE-2026-43504.

The patch installation procedure, verification commands, and interim mitigations are documented there. Reusing one runbook keeps the rollout consistent across the bundle.

Frequently asked questions

Is CVE-2026-43505 fixed by the same patch as CVE-2026-43504?

Yes. CVE-2026-43505 ships in the same vendor advisory as CVE-2026-43504. Applying the patched build named in the primary write-up closes both.

What is the CVSS score for CVE-2026-43505?

The CVSS base score is 6.5 (Medium).

Is it being exploited?

It is not currently listed in CISA KEV.

References


*Part of the Prosody bundle. Full procedure at CVE-2026-43504.*