{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-23741 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-23741 is a vulnerability in asterisk, published on 6 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-23741 and fix it if it is affected.\n\nWhat it is: CVE-2026-23741 is a vulnerability in asterisk, published on 6 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-23741 in the wild and no public exploit code.\n\nAffected product: asterisk. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-23741/ (Markdown: https://insights.sbomify.com/CVE-2026-23741/index.md)","id":"CVE-2026-23741","markdown":"https://insights.sbomify.com/CVE-2026-23741/index.md","name":"CVE-2026-23741","record":{"aliases":["DEBIAN-CVE-2026-23741","GHSA-rvch-3jmx-3jf3","UBUNTU-CVE-2026-23741"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Asterisk PBX","requires_auth":"none","summary":"A local attacker with write access to Asterisk config can execute arbitrary code as root via the ast_coredumper script.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"asterisk","vendor":"sangoma"},{"product":"certified_asterisk","vendor":"sangoma"}],"cvss":{"score":0,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"Asterisk is an open source private branch exchange and telephony toolkit. Prior to versions 20.7-cert9, 20.18.2, 21.12.1, 22.8.2, and 23.2.2, the asterisk/contrib/scripts/ast_coredumper runs as root, as noted by the NOTES tag on line 689 of the ast_coredumper file. The script will source the contents of /etc/asterisk/ast_debug_tools.conf, which resides in a folder that is writeable by the asterisk user:group. Due to the /etc/asterisk/ast_debug_tools.conf file following bash semantics and it being loaded; an attacker with write permissions may add or modify the file such that when the root ast_coredumper is run; it would source and thereby execute arbitrary bash code found in the /etc/asterisk/ast_debug_tools.conf. This issue has been patched in versions 20.7-cert9, 20.18.2, 21.12.1, 22.8.2, and 23.2.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Privilege escalation in asterisk","id":"CVE-2026-23741","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Skipper arbitrary code execution through lua filters","id":"CVE-2026-23742"},"packages":[],"prev":{"headline":"Asterisk vulnerable to potential privilege escalation","id":"CVE-2026-23740"},"products":["asterisk"],"published":"2026-02-06","related":[{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2024-57520","kev_date_added":null,"published":"2025-02-05"},{"cvss_score":7.7,"headline":"Using malformed From header can forge identity with \";\" or NULL in name portion","id":"CVE-2025-47779","kev_date_added":null,"published":"2025-05-22"},{"cvss_score":7.5,"headline":"Asterisk can crash from a specifically malformed Authorization header in an incoming SIP request","id":"CVE-2025-57767","kev_date_added":null,"published":"2025-08-28"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2022-37325","kev_date_added":null,"published":"2022-12-05"},{"cvss_score":7,"headline":"Asterisk Unsafe Shell Sourcing in safe_asterisk Leads to Local Privilege Escalation","id":"CVE-2025-1131","kev_date_added":null,"published":"2025-09-23"},{"cvss_score":6.5,"headline":"Asterisk remotely exploitable leak of RTP UDP ports and internal resources","id":"CVE-2025-54995","kev_date_added":null,"published":"2025-08-28"},{"cvss_score":6.5,"headline":"Asterisk is Vulnerable to Remote DoS and possible RCE Attacks During Memory Allocation","id":"CVE-2025-49832","kev_date_added":null,"published":"2025-08-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-06","vendors":["asterisk"]},"summary":"A local attacker with write access to Asterisk config can execute arbitrary code as root via the ast_coredumper script.","url":"https://insights.sbomify.com/CVE-2026-23741/"}