Quick answers
- Is CVE-2026-72776 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72776 being exploited in the wild.
- How severe is CVE-2026-72776?
- Critical severity, with a CVSS score of 9.8, published 13 August 2026.
- Which products and versions are affected?
- Fosowl Agenticseek commit fc242c7 and earlier.
- Is there a fix for CVE-2026-72776?
- 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-72776 attacked?
- It is attacked over the network or from the adjacent network, in a web application.
- Am I affected by CVE-2026-72776?
- Check whether you run Fosowl Agenticseek 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
The vulnerability is an unauthenticated remote code execution (RCE) flaw in the POST /query API endpoint. The root cause is that user-supplied queries are passed directly to an autonomous agent (BashInterpreter) that executes shell commands via subprocess.Popen with shell=True and safety=False, while relying on an incomplete command blocklist for protection. The attack vector is network-adjacent; attackers can send unauthenticated HTTP requests from any machine able to reach the API listening on 0.0.0.0:7777, which has wildcard CORS enabled, allowing browser-based exploitation. The vulnerable code fails to properly validate or sanitize queries before passing them to the shell executor, allowing bypass of the incomplete blocklist. An attacker achieves full host-level code execution with the privileges of the user running AgenticSeek.
Affected products
- Fosowl AgenticSeek commit fc242c7 and earlier
Timeline
- 2026-08-13: disclosed: CVE-2026-72776 published
- 2026-06-13: other: Security issue reported on GitHub (#520)