# ciguard: Container image runs as root (no USER directive)

Advisory record · `GHSA-jrm4-4pcf-4763`

- **Identifiers:** `GHSA-jrm4-4pcf-4763` · `CVE-2026-44218` · `PYSEC-2026-2409`
- **State:** Confirmed
- **Severity:** CVSS 3.0 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-269](https://cwe.mitre.org/data/definitions/269.html)
- **Tags:** [Privilege escalation](https://agentprime.io/advisories/tag/privilege-escalation.md)
- **Published:** 5 May 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 May 2026, 22:18 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `ciguard` (PyPI): affected `>=0.1.0, <0.8.2`; fixed in `0.8.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The ciguard package, versions from 0.1.0 before 0.8.2, has a container image that runs as root because its Dockerfile has no USER directive. The source describes this as a defence-in-depth gap and says it is not directly exploitable on its own; it would only matter if a separate container-runtime escape were available, where a root container would give more access on the host. To fix it, upgrade ciguard to 0.8.2 or later.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 3.0 Low, CVSS 3.1: `CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0012, the 1st percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:02 UTC: First seen by agentprime
- 31 Oct 2026, 15:02 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jrm4-4pcf-4763)

## Sources

- [GitHub Advisory Database: GHSA-jrm4-4pcf-4763](https://github.com/advisories/GHSA-jrm4-4pcf-4763)
- [OSV: GHSA-jrm4-4pcf-4763](https://osv.dev/vulnerability/GHSA-jrm4-4pcf-4763)
- <https://github.com/Jo-Jo98/ciguard/security/advisories/GHSA-jrm4-4pcf-4763>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-44218>
- <https://github.com/Jo-Jo98/ciguard>
- <https://github.com/Jo-Jo98/ciguard/releases/tag/v0.8.2>
- <https://github.com/Jo-Jo98/ciguard/releases/tag/v0.8.3>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jrm4-4pcf-4763>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jrm4-4pcf-4763/>. Everything for agents: <https://agentprime.io/llms.txt>.
