PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-90779 SIPp CVE debrief

A stack buffer overflow vulnerability exists in SIPp through version 3.7.7 in the createAuthHeader() function when processing SIP authentication challenges with oversized algorithm parameters. A malicious SIP server can send a crafted 401 or 407 challenge to corrupt the stack and crash the client process. This vulnerability can lead to service disruptions in SIPp installations. SIPp users and administrators need to verify their exposure, assess the potential impact, and prioritize updates to prevent client process crashes.

Vendor
SIPp
Product
Unknown
CVSS
HIGH 8.7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-13
Original CVE updated
2026-09-23
Advisory published
2026-09-13
Advisory updated
2026-09-23

Who should care

SIPp users and administrators should assess their exposure and prioritize verification and updates to prevent potential service disruptions. Defenders should care about CVE-2026-90779 because it can lead to service disruptions in SIPp installations. SIPp users and administrators need to verify their exposure, assess the potential impact, and prioritize updates to prevent client process crashes. This includes reviewing compensating controls, monitoring for

Why it matters

Defenders should care about CVE-2026-90779 because it can lead to service disruptions in SIPp installations. SIPp users and administrators need to verify their exposure, assess the potential impact, and prioritize updates to prevent client process crashes.

  • Potential service disruption due to client process crashes
  • Need for verification of affected versions and scope
  • Priority for updating to a fixed version of SIPp

Technical summary

The createAuthHeader() function in SIPp through 3.7.7 is vulnerable to a stack buffer overflow when processing SIP authentication challenges with oversized algorithm parameters. This can be exploited by a malicious SIP server to crash the client process. The vulnerability is confirmed in SIPp version 3.7.7. The CVE record and NVD entry provide details on the vulnerability, but further verification is needed to determine the full scope of affected versions and potential impact. Defenders should prioritize verifying and updating SIPp installations to prevent potential crashes and ensure availability of SIP services.

Defensive priority

Defenders should prioritize verifying and updating SIPp installations to prevent potential crashes and ensure availability of SIP services.

Recommended defensive actions

  • Verify and update SIPp installations to the latest version
  • Implement network monitoring to detect potential malicious SIP traffic
  • Restrict SIP server access to trusted sources
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is confirmed in SIPp version 3.7.7. The CVE record and NVD entry provide details on the vulnerability, but further verification is needed to determine the full scope of affected versions and potential impact.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-90779 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-90779

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-90779 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-90779

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.