# CVE-2026-57225: Suricata datasets: NULL pointer dereference in JSON/NDJSON dataset loading

> A NULL pointer dereference in Suricata's dataset loading allows attackers to crash the service via malicious JSON or NDJSON feeds.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-57225, GHSA-vqqx-88xw-qqvc, UBUNTU-CVE-2026-57225

## What is CVE-2026-57225?

CVE-2026-57225 is a low-severity vulnerability in Oisf Suricata, published on 18 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Suricata is a network Intrusion Detection System, Intrusion Prevention System and Network Security Monitoring engine. From 8.0.0 until 8.0.6, src/datasets-context-json.c assumes that a configured JSON or NDJSON dataset value_key resolves to a string. A trusted or untrusted dataset or rule feed containing a non-string value for that key can cause a NULL pointer dereference during startup, configuration test mode, or rule reload, crashing Suricata before traffic processing. This issue is fixed in version 8.0.6.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Oisf Suricata.

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

Upgrade to a fixed version.

## Is CVE-2026-57225 being exploited?

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

## 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-57225 and fix it if it is affected.

What it is: CVE-2026-57225 is a low-severity vulnerability in Oisf Suricata, published on 18 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-57225 in the wild and no public exploit code.

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

## Sources

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

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