CVE-2026-44218 json
ciguard: Container image runs as root (no USER directive)
published 2026-05-05 6 mo ago modified 2026-10-26 13 d ago also GHSA-jrm4-4pcf-4763 , PYSEC-2026-2409 , EUVD-2026-29795
- cvss
- 3.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 1%
- public exploits
- 0
- none known
Summary
ciguard is a static security auditor for CI/CD pipelines. From 0.1.0 to 0.8.1, the published ghcr.io/jo-jo98/ciguard container image inherits the default root user because the Dockerfile lacks a USER directive. This vulnerability is fixed in 0.8.2.
Patch / fix
- pypi ciguard 0.8.2
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.12% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.0 | CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N |
| GitHub | 3.1 | 3.0 | CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N |
| OSV | 3.1 | 3.0 | CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | ciguard | >=0.1.0, <0.8.2 |
0.8.2 |
Affected products
- Jo-Jo98 ciguard
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
github.com
/Jo-Jo98/ciguard/security/advisories/GHSA-jrm4-4pcf-4763
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-44218
advisory
-
github.com
/Jo-Jo98/ciguard
package
-
github.com
/Jo-Jo98/ciguard/releases/tag/v0.8.2
web
-
github.com
/Jo-Jo98/ciguard/releases/tag/v0.8.3
web
-
pypi.org
/project/ciguard
package
-
github.com
/advisories/GHSA-jrm4-4pcf-4763
advisory
Sources
- CVE List CVE-2026-44218
- GitHub Advisory GHSA-jrm4-4pcf-4763
- NVD CVE-2026-44218
- OSV PYSEC-2026-2409
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.