# CVE-2026-69702: SnailJob 1.7.0 Denial of Service via FuryUtil.deserialize OOM

> Authenticated attackers can crash the SnailJob server by submitting crafted compressed payloads that trigger unbounded memory allocation.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-ppxj-mvph-j9w4

## What is CVE-2026-69702?

CVE-2026-69702 is a high-severity denial of service vulnerability in aizuda SnailJob (snail-job), published on 4 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SnailJob 1.7.0 contains a denial of service vulnerability in the FuryUtil.deserialize helper that allows authenticated attackers to crash the server by supplying a crafted Zstandard-compressed payload with an inflated frame_content_size field in the frame header. Attackers can store a base64-encoded Zstandard payload declaring an arbitrarily large decompressed size in a retry task argument, causing the JVM to attempt an unbounded array allocation and triggering an unrecoverable java.lang.OutOfMemoryError when the task is dispatched through the retry-task pipeline.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value)

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


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

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

## Is CVE-2026-69702 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-69702 is a high-severity denial of service vulnerability in aizuda SnailJob (snail-job), published on 4 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-69702 in the wild and no public exploit code.

Affected product: aizuda SnailJob (snail-job). 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-69702/ (Markdown: https://insights.sbomify.com/CVE-2026-69702/index.md)
```

## Sources

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

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