Service interruption via unterminated PJSIP sessions
Published Aug 28, 2025 · Updated Nov 3, 2025
Resource exhaustion in Asterisk 18.26.3 and earlier or 18.9-cert16 and earlier allows remote authenticated users to interrupt service via SIP. A malformed static Via branch prevents normal BYE-driven teardown after ACK, so PJSIP retains RTP UDP ports and module resources after the connection closes. Access to an accepting PJSIP endpoint is required, and repeated calls exhaust the RTP port range until the PBX becomes inoperable.
Summary
What happened
Resource exhaustion in Asterisk 18.26.3 and earlier or 18.9-cert16 and earlier allows remote authenticated users to interrupt service via SIP. A malformed static Via branch prevents normal BYE-driven teardown after ACK, so PJSIP retains RTP UDP ports and module resources after the connection closes. Access to an accepting PJSIP endpoint is required, and repeated calls exhaust the RTP port range until the PBX becomes inoperable.
The record
- CVE
- CVE-2025-54995
- Published
- Aug 28, 2025
- Updated
- Nov 3, 2025
- Vendor
- Asterisk
- Product
- Asterisk
- Classifications
- CWE-1286, CWE-400, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 28, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 18.26.4
- Affected versionversion=< 18.9-cert17
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- SIPp malformed-branch reproduction scenariofunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- Resource leak first encountered in the wildreported exploitation
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo