Quick answers
- Is CVE-2026-56076 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56076 being exploited in the wild.
- How severe is CVE-2026-56076?
- High severity, with a CVSS score of 8.1, published 18 June 2026.
- Which products and versions are affected?
- PraisonAI praisonaiagents < 1.5.128.
- Is there a fix for CVE-2026-56076?
- 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-56076 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-56076?
- Check whether anything you run is named in the advisory. 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 exists in the `POST /agui` endpoint of the PraisonAI AGUI component. It stems from three combined issues: a lack of authentication on the endpoint, hardcoded `Access-Control-Allow-Origin: *` headers, and reliance on Starlette/FastAPI's JSON parsing which does not strictly enforce the `application/json` Content-Type. An attacker can craft a malicious website that sends a 'simple request' (using `text/plain`) to a victim's locally running AGUI server. Because the request is classified as a simple request, it bypasses CORS preflight checks; the server then executes the agent's instructions (which may include tool use like filesystem access) and returns the results. Due to the wildcard CORS header, the attacker's JavaScript can read the response and exfiltrate sensitive data. The issue is patched in version 1.5.128.
Affected products
- PraisonAI praisonaiagents < 1.5.128
Timeline
- 2026-04-09: advisory: Vendor security advisory published on GitHub
- 2026-06-18: disclosed: CVE published to NVD