CVE-2026-57193 json
Asterisk: LDAP Filter Injection in res_config_ldap via SIP Username (Unauthenticated Information Disclosure)
published 4mo ago modified 12d ago also EUVD-2026-110081 , GHSA-r6c2-hwc2-j4mp
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository asterisk/asterisk. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 6.9
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
Asterisk is an open source private branch exchange and telephony toolkit. Prior to Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 20.7-cert11, 22.8-cert3, the LDAP realtime driver `res_config_ldap` may permit `LDAP filter injection` through a `SIP username`, allowing an unauthenticated attacker to make arbitrary LDAP queries using carefully crafted SIP packets and disclose information. The `res_config_ldap` module must be loaded and configured to access an LDAP server, which is not the default. This issue is fixed in Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 20.7-cert11, 22.8-cert3.
Patch / fix
- asterisk open_source 20.20.1, 21.12.3, 22.10.1, 23.4.1
- digium certified_asterisk 20.7-cert11, 20.20.1, 21.12.3, 22.8-cert3, 22.10.1, 23.4.1
- sangoma certified_asterisk 20.7-cert11, 20.20.1, 21.12.3, 22.8-cert3, 22.10.1, 23.4.1
- asterisk certified_asterisk 20.7-cert11, 20.20.1, 21.12.3, 22.8-cert3, 22.10.1, 23.4.1
- digium asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1
- asterisk Debian 14 1:22.10.1+dfsg+~cs6.17.60671434-1
debian advisories DEBIAN-CVE-2026-57193
- github.com/asterisk/asterisk@04aa482 commit
- github.com/asterisk/asterisk@14968f2 commit
- github.com/asterisk/asterisk@23c01b6 commit
- github.com/asterisk/asterisk@7e1ae09 commit
- github.com/asterisk/asterisk@8170a6b commit
- github.com/asterisk/asterisk@dd0c768 commit
- github.com/asterisk/asterisk@ef28057 commit
- github.com/asterisk/asterisk/releases/tag/20.20.1 release
- github.com/asterisk/asterisk/releases/tag/21.12.3 release
- github.com/asterisk/asterisk/releases/tag/22.10.1 release
Is CVE-2026-57193 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-57193 updated cvss 5.3
asterisk: asterisk: Information disclosure via LDAP filter injection in res_config_ldap
-
Red Hat Fuse 7 camel-asterisk 2.23.2.fuse-7_13_0-00013-redhat-00001, camel-asterisk-starter 2.23.2.fuse-7_13_0-00013-redhat-00001not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 12d ago
Exploit prediction
1.96% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N |
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- asterisk asterisk
- asterisk certified-asterisk
Classification
- Weakness
-
- CWE-943 Improper Neutralization of Special Elements in Data Query Logic
References
- github.com /asterisk/asterisk/commit/04aa482212e43b292817444eb4de35499f4b1568
- github.com /asterisk/asterisk/commit/14968f2f440ea0dd983caa4f477237a5224904dd
- github.com /asterisk/asterisk/commit/23c01b6d359c5d85da725beea89e394a6c031c5d
- github.com /asterisk/asterisk/commit/7e1ae09594a101950398cc6aff2dd2e5ab314884
- github.com /asterisk/asterisk/commit/8170a6bfa75994e7617a8b9d7fe7a7140b70cbe2
- github.com /asterisk/asterisk/commit/dd0c768d9e9678e4cb1ed95689a254a61452239b
- github.com /asterisk/asterisk/commit/ef280572a034cac3994075298facb1999778ee0d
-
github.com
/asterisk/asterisk/security/advisories/GHSA-r6c2-hwc2-j4mp
advisory
- github.com /asterisk/asterisk/releases/tag/20.20.1
- github.com /asterisk/asterisk/releases/tag/21.12.3
- github.com /asterisk/asterisk/releases/tag/22.10.1
- github.com /asterisk/asterisk/releases/tag/23.4.1
- github.com /asterisk/asterisk/releases/tag/certified-20.7-cert11
- github.com /asterisk/asterisk/releases/tag/certified-22.8-cert3
- github.com /asterisk/asterisk/tree/24.0.0-pre1
Sources
- CVE List CVE-2026-57193
- NVD CVE-2026-57193
- Maintainer advisory GHSA-r6c2-hwc2-j4mp
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of asterisk/asterisk published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.