Skip to main content
CVE-2025-2099VulnerabilityPublished Updated

Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.5 Container Release Update

Affects Red HatSource GCVE Database

0
Compare

Not known to be exploited.

Data as of 31 Oct 2026, 20:20 UTC

Severity
Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

What to do

AI-suggested

Red Hat has released updated container images and collection versions that fix this vulnerability. Users of Red Hat Ansible Automation Platform 2.5 should apply the official updates as provided in Red Hat Security Advisory RHSA-2025:12791. The advisory lists updated versions of ansible.controller (4.6.18), ansible.eda (2.8.2), ansible.windows (2.8.0), and redhat.rhel_system_roles (1.95.7). Applying these updates mitigates the ReDoS vulnerability. No additional mitigation actions are required beyond applying the official fixes.

Description

A Regular Expression Denial of Service (ReDoS) vulnerability (CVE-2025-2099) was identified in the ansible-lightspeed-chatbot-container component of Red Hat Ansible Automation Platform 2.5. This vulnerability is related to the huggingface/transformers library. Red Hat has released an update for Ansible Automation Platform 2.5 that addresses this issue along with updates to several Ansible collections.

References

Community reviews

Loading reviews…