Bug 2427094 (CVE-2026-0598)

Summary:	CVE-2026-0598 ansible-lightspeed: Broken Object Level Authorization Leading to Cross-User AI Conversation Context Injection in Ansible Lightspeed API
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security DevOps Team <prodsec-dev>
Status:	NEW ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	carogers, dschmidt, erezende, haoli, hkataria, jajackso, jcammara, jmitchel, jneedle, kegrant, koliveir, kshier, mabashia, mattdavi, pbohmill, pbraun, security-response-team, shvarugh, simaishi, smcdonal, stcannon, teagle, tfister, thavo, yguenane
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A security flaw was identified in the Ansible Lightspeed API conversation endpoints that handle AI chat interactions. The APIs do not properly verify whether a conversation identifier belongs to the authenticated user making the request. As a result, an attacker with valid credentials could access or influence conversations owned by other users. This exposes sensitive conversation data and allows unauthorized manipulation of AI-generated outputs.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Deadline:	2026-02-06

Description OSIDB Bzimport 2026-01-05 07:48:13 UTC

Broken Object Level Authorization (BOLA) vulnerability in the Ansible Lightspeed AI conversation endpoints. The flaw occurs due to missing ownership validation of the conversation_id parameter in the /api/v0/ai/chat/, /api/v1/ai/chat/, and streaming chat APIs. Although UUIDs are used, the backend does not verify that the authenticated user owns the referenced conversation, and conversations are incorrectly mapped to a default null user ID. An authenticated attacker who obtains a valid conversation identifier can access prior conversation history and inject new prompts into another user’s AI session, potentially influencing generated Ansible playbooks. This can be exploited remotely without user interaction and leads to unauthorized information disclosure and integrity compromise.