# CVE-2026-36365: Command injection in n/a

> A local attacker can execute arbitrary code via command injection in the shutdown and sleep functions of the caesium-image-compressor library.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** No
- **Published:** 4 May 2026
- **Updated:** 5 May 2026
- **Also known as:** GHSA-2rrx-2h24-9hm6

## What is CVE-2026-36365?

CVE-2026-36365 is a high-severity command injection vulnerability in n/a, published on 4 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in Lymphatus caesium-image-compressor All versions up to and including commit 02da2c6 allows a local attacker to execute arbitrary code via the shutdownMachine and putMachineToSleep functions in PostCompressionActions.cpp

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2026-36365 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-36365 is a high-severity command injection vulnerability in n/a, published on 4 May 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-36365 in the wild and no public exploit code.

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

## Sources

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

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