# CVE-2026-90779: SIPp through 3.7.7 Stack Buffer Overflow via createAuthHeader Algorithm Parameter

> A malicious SIP server can crash the SIPp client via a stack buffer overflow in the authentication header processing logic.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-h494-p5hw-ph93

## What is CVE-2026-90779?

CVE-2026-90779 is a high-severity memory corruption vulnerability in sipp, published on 13 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SIPp through 3.7.7 contains a stack buffer overflow vulnerability in createAuthHeader() 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.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-90779?


## How do I fix CVE-2026-90779?

No fix has been published for CVE-2026-90779 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-90779 being exploited?

There is no known exploitation of CVE-2026-90779 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90779 and fix it if it is affected.

What it is: CVE-2026-90779 is a high-severity memory corruption vulnerability in sipp, published on 13 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90779 in the wild and no public exploit code.

Affected product: sipp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90779/ (Markdown: https://insights.sbomify.com/CVE-2026-90779/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90779
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90779
- OSV: https://osv.dev/vulnerability/CVE-2026-90779

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90779/
Summaries are generated and may contain mistakes; the official description above is the record.