CVE-2026-44220: Jo-Jo98 ciguard · Link Following
Affects Jo-Jo98 ciguardSource CVE Database V5
Not known to be exploited · CVSS 3.2 Low : upgrade to 0.8.2 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.8.2
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade Jo-Jo98 ciguard to 0.8.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Jo-Jo98ciguard | Affected
| Fixed in
|
AI-suggested
This vulnerability is fixed in ciguard version 0.8.2. Users should upgrade to version 0.8.2 or later to remediate this issue. No other official remediation level or temporary fix is provided. Patch status is confirmed by the vendor's versioning information. Until upgraded, users should avoid scanning directories where untrusted users can create symlinks.
Description
ciguard is a static security auditor for CI/CD pipelines. From 0.8.0 to 0.8.1 , the discover_pipeline_files() function in src/ciguard/discovery.py walks a directory tree following symlinks, with cycle protection via tracking visited resolved paths. An attacker who can plant a symlink in a directory the user (or AI agent) scans can cause discovery to walk into the symlink target and return paths to pipeline-shaped files outside the requested root. This vulnerability is fixed in 0.8.2.