Evidence used
- No CISA KEV confirmation is currently recorded.
- Exploitation requires an existing local or physical foothold with privileges.
- EPSS is 0.26% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2024
CVE-2024-9902High confidence
Ansible-core: ansible-core user may read/write unauthorized content
Unknown · Unknown
Official source article: Red Hat RHSA-2024:10762 ↗. Check the applicable product and release in the original source.
6.3MediumCVSS 3.1
Scheduled
Patch availableMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Low, lowered one band.downgradedsince 6 Nov 2025
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
10 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | ansible | Vendor fix publishedDebian records a fixed source-package version for this release. | 5.4.0-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian trixietrixie · source | ansible-core | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.18.0-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | ansible | Vendor fix publishedDebian records a fixed source-package version for this release. | 5.4.0-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | ansible-core | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.14.18-0+deb12u1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | ansible | Vendor fix publishedDebian records a fixed source-package version for this release. | 5.4.0-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | ansible-core | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.18.0-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | ansible | Vendor fix publishedDebian records a fixed source-package version for this release. | 5.4.0-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | ansible-core | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.18.0-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | ansible | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | ansible-core | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Open-source package ranges10 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| PyPIansible-core | ECOSYSTEM: introduced 0; fixed 2.14.18rc1 | 2.14.18rc1 | OSV record ↗aggregator derived · 10 Sep 2026 |
| PyPIansible-core | ECOSYSTEM: introduced 2.15.0b1; fixed 2.15.13rc1 | 2.15.13rc1 | OSV record ↗aggregator derived · 10 Sep 2026 |
| PyPIansible-core | ECOSYSTEM: introduced 2.16.0b1; fixed 2.16.13rc1 | 2.16.13rc1 | OSV record ↗aggregator derived · 10 Sep 2026 |
| PyPIansible-core | ECOSYSTEM: introduced 2.17.0b1; fixed 2.17.6rc1 | 2.17.6rc1 | OSV record ↗aggregator derived · 10 Sep 2026 |
| PyPIansible-core | ECOSYSTEM: introduced 2.18.0b1; fixed 2.18.0rc2 | 2.18.0rc2 | OSV record ↗aggregator derived · 10 Sep 2026 |
| pipansible-core | < 2.14.18rc1 | 2.14.18rc1 | GitHub advisory ↗github reviewed aggregator · 4 Nov 2025 |
| pipansible-core | >= 2.15.0b1, < 2.15.13rc1 | 2.15.13rc1 | GitHub advisory ↗github reviewed aggregator · 4 Nov 2025 |
| pipansible-core | >= 2.16.0b1, < 2.16.13rc1 | 2.16.13rc1 | GitHub advisory ↗github reviewed aggregator · 4 Nov 2025 |
| pipansible-core | >= 2.17.0b1, < 2.17.6rc1 | 2.17.6rc1 | GitHub advisory ↗github reviewed aggregator · 4 Nov 2025 |
| pipansible-core | >= 2.18.0b1, < 2.18.0rc2 | 2.18.0rc2 | GitHub advisory ↗github reviewed aggregator · 4 Nov 2025 |
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Patch available01
What, why and how
A flaw was found in Ansible. The ansible-core `user` module can allow an unprivileged user to silently create or replace the contents of any file on any system path and take ownership of it when a privileged user executes the `user` module against the unprivileged user's home directory. If the unprivileged user has traversal permissions on the directory containing the exploited target file, they retain full control over the contents of the file as its owner.
What
A flaw was found in Ansible. The ansible-core `user` module can allow an unprivileged user to silently create or replace the contents of any file on any system path and take ownership of it when a privileged user executes the `user` module against the unprivileged user's home directory. If the unprivileged user has traversal permissions on the directory containing the exploited target file, they retain full control over the contents of the file as its owner.
Why
The application performs an authorisation check, but it does not correctly enforce the required permission boundary.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
A flaw was found in Ansible. The ansible-core `user` module can allow an unprivileged user to silently create or replace the contents of any file on any system path and take ownership of it when a privileged user executes the `user` module against the unprivileged user's home directory. If the unprivileged user has traversal permissions on the directory containing the exploited target file, they retain full control over the contents of the file as its owner.
Why
The application performs an authorisation check, but it does not correctly enforce the required permission boundary.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Incorrect Authorization → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Local
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- Required interaction required
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-863 ↗
CWE-863: Incorrect Authorization. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:LCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.ALowAvailability impact: A successful attack can cause a limited loss.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Fixed
- Ansible Automation Platform Execution Environments: 3.0.1-96 < *, 3.0.1-95 < *, 2.9.27-32 < *, 2.14.13-21 < *, 2.17.6-2 < *
- Red Hat Ansible Automation Platform 2.4 for RHEL 8: 1:2.15.13-1.el8ap < *
- Red Hat Ansible Automation Platform 2.4 for RHEL 9: 1:2.15.13-1.el9ap < *
- Red Hat Ansible Automation Platform 2.5 for RHEL 8: 1:2.16.13-1.el8ap < *
- Red Hat Ansible Automation Platform 2.5 for RHEL 9: 1:2.16.13-1.el9ap < *
- Red Hat OpenStack Platform 17.1 for RHEL 9: 0:2.14.2-4.6.el9ost < *
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 6 Nov 2024 · Last source change 6 Nov 2025, 23:17 UTC · CWE-863 · Incorrect Authorization
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2024-3182
Product sourceUnavailable
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD not scheduled
Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.
Material change intelligence
View recent updates ↗What changed after publication
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
CVE published
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.