PatchSiren cyber security CVE debrief
CVE-2026-57193 asterisk CVE debrief
Asterisk, a widely-used open-source private branch exchange and telephony toolkit, is vulnerable to LDAP filter injection through a SIP username. This vulnerability allows an unauthenticated attacker to make arbitrary LDAP queries and potentially disclose sensitive information. The res_config_ldap module must be loaded and configured to access an LDAP server, which is not the default configuration. This issue affects Asterisk versions prior to 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk versions prior to 20.7-cert11, 22.8-cert3. The vulnerability stems from the LDAP realtime driver res_config_ldap's improper handling of SIP usernames, which can be crafted to inject mal
- Vendor
- asterisk
- Product
- Unknown
- CVSS
- MEDIUM 6.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-26
- Original CVE updated
- 2026-10-27
- Advisory published
- 2026-10-26
- Advisory updated
- 2026-10-27
Who should care
Defenders responsible for Asterisk installations, particularly those using the res_config_ldap module, should assess exposure and apply patches or mitigations as needed. This includes verifying if the module is loaded and configured, reviewing system logs for suspicious activity, and ensuring that appropriate compensating controls are in place. Additionally, security teams and vulnerability management teams should prioritize verifying the vulnerability's
Why it matters
Defenders should prioritize verifying if the res_config_ldap module is loaded and configured, and apply patches or mitigations as needed to prevent potential LDAP filter injection attacks.
- Potential information disclosure through LDAP queries
- Possible unauthorized access to sensitive information
Technical summary
The LDAP realtime driver res_config_ldap in Asterisk may permit LDAP filter injection through a SIP username, allowing an unauthenticated attacker to make arbitrary LDAP queries and disclose information. The vulnerability arises from the module's improper handling of user input, specifically SIP usernames, which can be manipulated to inject malicious LDAP filters. This issue affects Asterisk versions prior to 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk versions prior to 20.7-cert11, 22.8-cert3. The res_config_ldap module must be loaded and configured to access an LDAP server
Defensive priority
Defenders should prioritize verifying if the res_config_ldap module is loaded and configured, and apply patches or mitigations as needed.
Recommended defensive actions
- Verify if the res_config_ldap module is loaded and configured
- Apply patches or mitigations as needed
- Monitor for suspicious LDAP queries
- Review compensating controls for exposed systems
- Check relevant monitoring, detection, and logs for exposed assets
- Track exceptions and retest remediated assets
- Confirm whether affected product deployments exist in managed environments
Evidence notes
The CVE record and NVD vulnerability detail page provide information on the vulnerability, but do not provide evidence of exploitation or specific affected versions beyond Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 20.7-cert11, 22.8-cert3. The res_config_ldap module's configuration and loading status should be verified by defenders. There is no indication of in-the-wild exploitation, but defenders should assess exposure and apply patches or mitigations as needed. The vulnerability's impact is potentially severe,
Sources and references
Verified primary and authoritative sources
-
CVE-2026-57193 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-57193
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-57193 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-57193
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/asterisk/asterisk/commit/04aa482212e43b292817444eb4de35499f4b1568
-
Source reference
Unverified legacy reference
URL: https://github.com/asterisk/asterisk/commit/14968f2f440ea0dd983caa4f477237a5224904dd
-
Source reference
Unverified legacy reference
URL: https://github.com/asterisk/asterisk/commit/23c01b6d359c5d85da725beea89e394a6c031c5d
-
Source reference
Unverified legacy reference
URL: https://github.com/asterisk/asterisk/commit/7e1ae09594a101950398cc6aff2dd2e5ab314884
-
Source reference
Unverified legacy reference
URL: https://github.com/asterisk/asterisk/commit/8170a6bfa75994e7617a8b9d7fe7a7140b70cbe2
-
Source reference
Unverified legacy reference
URL: https://github.com/asterisk/asterisk/commit/dd0c768d9e9678e4cb1ed95689a254a61452239b
-
Source reference
Unverified legacy reference
URL: https://github.com/asterisk/asterisk/commit/ef280572a034cac3994075298facb1999778ee0d
-
Source reference
Unverified legacy reference
URL: https://github.com/asterisk/asterisk/releases/tag/20.20.1
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.