{"answers":{"affected":"3 open source packages ship an affected version, including ciguard.","exploited":"There is no known exploitation of CVE-2026-44218 in the wild and no public exploit code.","fix":"Upgrade ciguard to 0.8.2 or later.","what":"CVE-2026-44218 is a low-severity vulnerability in Jo-Jo98 ciguard, published on 12 May 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-44218 and fix it if it is affected.\n\nWhat it is: CVE-2026-44218 is a low-severity vulnerability in Jo-Jo98 ciguard, published on 12 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-44218 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ciguard (PyPI): affected from 0.1.0; fixed in 0.8.2\n- ciguard (PyPI): affected from 0.1.0; fixed in 0.8.2\n- ciguard (PyPI): affected from 0.1.0; fixed in 0.8.2\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-44218/ (Markdown: https://insights.sbomify.com/CVE-2026-44218/index.md)","id":"CVE-2026-44218","markdown":"https://insights.sbomify.com/CVE-2026-44218/index.md","name":"CVE-2026-44218","record":{"aliases":["GHSA-jrm4-4pcf-4763","PYSEC-2026-2409"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"CI/CD security auditor","requires_auth":"high_privilege","summary":"The container image runs as root by default, allowing attackers to escalate privileges if they compromise the container.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ciguard: Container image runs as root (no USER directive)","id":"CVE-2026-44218","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"ciguard: SCA HTTP client reads response body without size cap","id":"CVE-2026-44219"},"packages":[{"ecosystem":"PyPI","fixed":["0.8.2"],"introduced":["0.1.0"],"last_affected":[],"package":"ciguard","purl":null,"source":"GHSA-jrm4-4pcf-4763"},{"ecosystem":"PyPI","fixed":["0.8.2"],"introduced":["0.1.0"],"last_affected":[],"package":"ciguard","purl":"pkg:pypi/ciguard","source":"GHSA-jrm4-4pcf-4763"},{"ecosystem":"PyPI","fixed":["0.8.2"],"introduced":["0.1.0"],"last_affected":[],"package":"ciguard","purl":"pkg:pypi/ciguard","source":"PYSEC-2026-2409"}],"prev":{"headline":"sse-channel: SSE Injection via unsanitized event fields","id":"CVE-2026-44217"},"products":["ciguard"],"published":"2026-05-12","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-14","vendors":["Jo-Jo98"]},"summary":"The container image runs as root by default, allowing attackers to escalate privileges if they compromise the container.","url":"https://insights.sbomify.com/CVE-2026-44218/"}