# CVE-2026-90780: SIPp through 3.7.7 Buffer Overflow via Oversized SIP Header Content

> Unauthenticated remote attackers can crash the SIPp testing tool by sending oversized SIP headers, causing a buffer overflow.

- **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-fg45-qcjm-jcjr

## What is CVE-2026-90780?

CVE-2026-90780 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 buffer overflow vulnerability in the get_header() function in src/sip_parser.cpp when processing SIP messages with header content exceeding 20,490 bytes. Unauthenticated remote attackers can send crafted SIP messages with oversized headers to overflow the static buffer and crash the process.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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


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

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

## Is CVE-2026-90780 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90780 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-90780 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-90780/ (Markdown: https://insights.sbomify.com/CVE-2026-90780/index.md)
```

## Sources

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

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