Quick answers
- Is CVE-2026-96893 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96893 being exploited in the wild.
- How severe is CVE-2026-96893?
- High severity, with a CVSS score of 7.3, published 13 October 2026.
- Which products and versions are affected?
- GitLab Enterprise Edition 19.1 before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2.
- Is there a fix for CVE-2026-96893?
- Yes: fixed in GitLab EE 19.2.8, 19.3.5, 19.4.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-96893 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-96893?
- Check whether you run GitLab or GitLab Enterprise Edition 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.
How to fix
- Fixed in: GitLab EE 19.2.8, 19.3.5, 19.4.2
Technical details
An improper neutralization vulnerability in AI conversation context construction allows authenticated users to inject specially crafted input into AI agent instructions, leading to prompt injection. The vulnerability affects the Duo Agent Platform component and requires authentication and user interaction. A successful exploit could result in arbitrary command execution attributed to other users without proper authorization checks.
Affected products
- GitLab GitLab Enterprise Edition 19.1 before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2
Timeline
- 2026-10-13: disclosed
- 2026-10-12: patched