{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-23738 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-23738 is a low-severity cross-site scripting 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-23738 and fix it if it is affected.\n\nWhat it is: CVE-2026-23738 is a low-severity cross-site scripting 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-23738 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-23738/ (Markdown: https://insights.sbomify.com/CVE-2026-23738/index.md)","id":"CVE-2026-23738","markdown":"https://insights.sbomify.com/CVE-2026-23738/index.md","name":"CVE-2026-23738","record":{"aliases":["DEBIAN-CVE-2026-23738","GHSA-v6hp-wh3r-cwxh","UBUNTU-CVE-2026-23738"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Asterisk PBX","requires_auth":"none","summary":"Attackers can inject malicious scripts into the Asterisk web server status page via unsanitized cookies or query parameters, potentially compromising user sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"asterisk","vendor":"sangoma"},{"product":"certified_asterisk","vendor":"sangoma"}],"cvss":{"score":3.5,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"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, user supplied/control values for Cookies and any GET variable query Parameter are directly interpolated into the HTML of the page using ast_str_append. The endpoint at GET /httpstatus is the potential vulnerable endpoint relating to asterisk/main /http.c. 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":"Cross-site scripting in asterisk","id":"CVE-2026-23738","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Asterisk xml.c uses unsafe XML_PARSE_NOENT leading to potential XXE Injection","id":"CVE-2026-23739"},"packages":[],"prev":{"headline":"seroval Affected by Remote Code Execution via JSON Deserialization","id":"CVE-2026-23737"},"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":"Attackers can inject malicious scripts into the Asterisk web server status page via unsanitized cookies or query parameters, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2026-23738/"}