# CVE-2026-45769: ikev2: unbounded client transform storage can lead to resource exhaustion

> Attackers can cause Suricata to consume excessive memory via crafted IKEv2 traffic, leading to denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-45769, GHSA-hg2g-r464-5593, UBUNTU-CVE-2026-45769

## What is CVE-2026-45769?

CVE-2026-45769 is a high-severity denial of service vulnerability in Oisf Suricata, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. Prior to versions 7.0.16 and 8.0.5,IKEv2 parser state could grow without bounds while storing client transforms. Repeated crafted UDP traffic may cause Suricata to consume excessive memory, potentially resulting in denial of service. Versions 7.0.16 and 8.0.5 fix the issue. Some workarounds are available. Disable IKE application-layer parsing if it is not needed. Alternatively, use a rule to bypass ike flows after the first packets like `alert ike any any -> any any (sid: 2; flow.pkts_toserver: > 256; bypass; noalert;)`.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Oisf Suricata.

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

Upgrade to a fixed version.

## Is CVE-2026-45769 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45769 exists.

## Other vulnerabilities in Oisf Suricata

- [CVE-2023-35853](https://insights.sbomify.com/CVE-2023-35853/): Code injection in n/a (critical 9.8)
- [CVE-2021-37592](https://insights.sbomify.com/CVE-2021-37592/): Other in n/a (critical 9.8)
- [CVE-2018-10244](https://insights.sbomify.com/CVE-2018-10244/): Integer overflow in n/a (critical 9.8)
- [CVE-2026-94083](https://insights.sbomify.com/CVE-2026-94083/): Memory corruption in Suricata (critical 9.4)
- [CVE-2026-94084](https://insights.sbomify.com/CVE-2026-94084/): Use after free in Suricata (critical 9.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45769 is a high-severity denial of service vulnerability in Oisf Suricata, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45769 exists.

Affected product: Oisf Suricata. 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-45769/ (Markdown: https://insights.sbomify.com/CVE-2026-45769/index.md)
```

## Sources

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

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