CVE-2026-23738
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAsterisk 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a reflected Cross-Site Scripting (XSS) vulnerability in Asterisk's built-in HTTP server. User-supplied values from HTTP Cookies and GET query parameters are directly interpolated into HTML responses at the /httpstatus endpoint (asterisk/main/http.c) without proper sanitization or encoding, allowing injection of malicious HTML/JavaScript.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 20.18.2>= 21.0.0, <= 21.12.1>= 22.0.0, <= 22.8.2>= 23.0.0, < 23.2.2<= 18.9= 20.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Asterisk versionRun `asterisk -V` or `asterisk -x "core show version"` to retrieve the exact version numberAffected if The version falls within these ranges: <= 20.18.2, 21.0.0-21.12.1, 22.0.0-22.8.2, or 23.0.0-23.2.1 (or Certified versions <= 18.9 or = 20.7)
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped23.2.2
Upgrade to patched versions 20.7-cert9, 20.18.2, 21.12.1, 22.8.2, or 23.2.2. If immediate upgrade is not feasible, restrict or disable the HTTP server and ensure the /httpstatus endpoint is not exposed to untrusted networks.
Asterisk 20.18.2, 21.12.1, 22.8.2, or 23.2.2 (or Certified Asterisk 20.7-cert9)
- 1. Identify the currently running Asterisk version by running 'asterisk -V' or 'asterisk -rx "core show version"'
- 2. Determine which Asterisk branch (20.x, 21.x, 22.x, or 23.x) is currently in production
- 3. Download the appropriate fixed version from the official Asterisk downloads page (downloads.asterisk.org) or your distribution's package repository
- 4. For Asterisk 20.x: upgrade to version 20.18.2
- 5. For Asterisk 21.x: upgrade to version 21.12.1
- 6. For Asterisk 22.x: upgrade to version 22.8.2
- 7. For Asterisk 23.x: upgrade to version 23.2.2
- 8. For Certified Asterisk 18.x: upgrade to version 18.9-cert10 or later (if available)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23738 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-23738 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data