Quick answers
- Is CVE-2026-44777 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44777 being exploited in the wild.
- How severe is CVE-2026-44777?
- Medium severity, with a CVSS score of 5.5, published 11 May 2026.
- Which products and versions are affected?
- Jqlang Jq 1.8.2rc1 and earlier.
- Is there a fix for CVE-2026-44777?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-44777 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-44777?
- Check whether you run Jqlang Jq at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An uncontrolled recursion vulnerability (CWE-674) exists in jq's module loader. The issue occurs because the loader lacks cycle detection when resolving dependencies via the 'include' directive. If two modules mutually include each other, the loader repeatedly re-enters the resolution path (specifically through jq_realpath, find_lib, and load_library), leading to stack exhaustion and a process crash. An attacker can trigger this by influencing the module search path or providing malicious jq programs. As of the advisory date, no official patch is listed, though a fix involving tracking active resolutions in a stack is proposed.
Affected products
- jqlang jq 1.8.2rc1 and earlier
Timeline
- 2026-05-11: disclosed
- 2026-05-11: advisory