Skip to main content
VulnerabilityPublished Updated

CVE-2024-1394: Red Hat Ansible Automation Platform 2.4 for RHEL 8 · Memory Leak

Affects Red Hat Ansible Automation Platform 2.4 for RHEL 8Source GCVE Database

0
Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 29 Oct 2026, 10:09 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.17.5
EPSS
1.5% chance of exploitation in 30 days – higher than 74% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Mar 2024

  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 29 Oct 2026.

What to do

AI-suggested

Red Hat has released an official security update for the golang package that fixes this memory leak vulnerability. Users should apply the update as per Red Hat's advisory RHSA-2024:1462. Before applying this update, ensure all previously released errata relevant to your system are applied. No additional mitigations are required beyond applying the official patch.

Description

CVE-2024-1394 is a high-severity memory leak vulnerability in the Golang RSA encrypting/decrypting code used by Red Hat Ansible Automation Platform 2.4 for RHEL 8. The flaw occurs due to improper release of memory objects during error handling, potentially leading to resource exhaustion. Red Hat has issued a security advisory with an update to the golang package that addresses this issue.

References

Community reviews

Loading reviews…