Quick answers
- Is CVE-2026-111321 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111321 being exploited in the wild.
- How severe is CVE-2026-111321?
- Medium severity, with a CVSS score of 5.4, published 15 October 2026.
- Which products and versions are affected?
- TaskingAI through 0.3.0.
- Is there a fix for CVE-2026-111321?
- 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-111321 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111321?
- Check whether you run TaskingAI 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
TaskingAI fails to validate the OpenAPI servers[0].url parameter when users define custom actions, allowing attackers to inject arbitrary URLs. An authenticated attacker with project API key or console admin credentials can create an action pointing to loopback (127.0.0.1), internal networks, or cloud metadata services, then execute it via POST /actions/{action_id}/run to retrieve up to 64 KiB of response data. The vulnerability stems from missing URL validation in the openapi_call.py service handler.
Affected products
- TaskingAI TaskingAI through 0.3.0
Timeline
- 2026-10-15: disclosed