LiveActive security incident?Get immediate response
CVE Record

CVE-2026-0598: Ansible-lightspeed: broken object level authorization leading to cross-user ai conversation context injection in ansible lightspeed api

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.

MediumCVSS 4.2Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-0598 is an authorization flaw in Red Hat Ansible Lightspeed AI chat APIs. A logged-in user could access or influence another user’s AI conversation if they can reference that conversation. Business impact is limited but relevant where chat content may contain sensitive automation details or where AI output integrity matters.

Executive priority

Treat as a medium-priority fix for environments using Ansible Lightspeed. It is not an unauthenticated takeover issue, but it can expose or alter AI conversation context across users, which may affect confidentiality and trust in automation recommendations.

Technical view

The issue is broken object-level authorization in Ansible Lightspeed conversation endpoints. The API does not properly verify that a conversation identifier belongs to the authenticated requester. Red Hat rates it Medium, CVSS 4.2, with network access, low privileges, high attack complexity, and low confidentiality and integrity impact.

Likely exposure

Exposure appears limited to Red Hat Ansible Automation Platform 2.6 deployments using package ansible-automation-platform-26/lightspeed-rhel9. Multiple listed AAP 2.4 and 2.5 packages are marked unaffected in the source bundle.

Exploitation context

An attacker needs valid credentials. Sources do not indicate public exploitation, and the CVE is not listed as KEV in the provided data. The practical risk depends on whether conversation identifiers can be obtained or guessed and whether chat content includes sensitive operational context.

Researcher notes

The source data identifies CWE-283 and broken object-level authorization. No exploit details, proof of concept, or active exploitation evidence are provided. Red Hat Bugzilla and RHSA links are the primary sources for implementation-specific remediation details.

Mitigation direction

  • Review Red Hat advisory RHSA-2026:13545 for applicable updates or required actions.
  • Prioritize affected Ansible Lightspeed components in AAP 2.6 on RHEL 9.
  • Restrict access to Ansible Lightspeed to users with a business need.
  • Avoid placing secrets or sensitive infrastructure details in AI chat prompts.
  • Monitor vendor guidance for corrected package details and deployment instructions.

Validation and detection

  • Inventory Ansible Automation Platform versions and Lightspeed container packages.
  • Confirm whether ansible-automation-platform-26/lightspeed-rhel9 is deployed.
  • Check Red Hat CVE and errata pages for fixed package status.
  • Review application logs for unusual cross-user conversation access patterns.
  • Validate authorization controls after applying vendor updates.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-283: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-0598 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.2CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N1.62.5redhat

Vulnerability scoring details

Base CVSS 3.1 score

4.2Medium
CVSS 3.1 vector shape for CVE-2026-0598Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineredhat

    Reported to Red Hat.

  2. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  3. Source timelineredhat

    Made public.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Red HatRed Hat Ansible Automation Platform 2.6ansible-automation-platform-26/lightspeed-rhel9, 1777387242affected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-24/de-minimal-rhel8unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-24/de-minimal-rhel9unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-24/de-supported-rhel8unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-24/de-supported-rhel9unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-24/ee-minimal-rhel8unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-24/ee-minimal-rhel9unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-24/ee-supported-rhel8unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-24/ee-supported-rhel9unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-24/lightspeed-rhel8unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-24/platform-resource-runner-rhel8unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-25/aap-cloud-metrics-collector-rhel8unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-25/ansible-dev-tools-rhel8unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-25/de-minimal-rhel8unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-25/de-minimal-rhel9unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-25/de-supported-rhel8unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-25/de-supported-rhel9unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-25/ee-cloud-services-rhel9unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-25/ee-minimal-rhel8unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-25/ee-minimal-rhel9unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-25/ee-supported-rhel8unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-25/ee-supported-rhel9unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-25/lightspeed-rhel8unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-25/platform-resource-runner-rhel8unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-26/ansible-dev-tools-rhel9unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-26/de-minimal-rhel9unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-26/de-supported-rhel9unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-26/ee-minimal-rhel9unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-26/ee-supported-rhel9unaffected
Red HatRed Hat Ansible Automation Platform 2ansible-automation-platform-26/mcp-tools-rhel9unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-283 · source CWE mapping

Unverified Ownership

Unverified Ownership represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.