Medium · CVSS 6.3CVE-2024-9902

Ansible-core: ansible-core user may read/write unauthorized contentCVE-2024-9902

Answer in brief

CVE-2024-9902 records a Medium severity (CVSS 6.3) vulnerability in Ansible-core: ansible-core user may read/write unauthorized content. The current sources do not mark it as known exploited. The current feed maps ansible-core (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Nov 6, 2024Updated Nov 5, 2026Source checked Nov 5, 2026First seen by HOL Nov 5, 2026Material review Nov 5, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.3
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 6.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps ansible-core (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
ansible-coregeneric	>=0 <2.14.18rc1 \|\| >=2.15.0b1 <2.15.13rc1 \|\| >=2.16.0b1 <2.16.13rc1 \|\| >=2.17.0b1 <2.17.6rc1 \|\| >=2.18.0b1 <2.18.0rc2	2.14.18rc1, 2.15.13rc1, 2.16.13rc1, 2.17.6rc1, 2.18.0rc2

Recommended response

Check inventory. Check lockfiles and deployed manifests for ansible-core.
Review the reported fix. Source-reported workaround: In the play that uses the user module with the key generation option, have a prior task ensuring the public key does not exist for example: - name: avoid user exploit (change name depending on other options used in user task) file: path=/home/{{username}}/.ssh/id_rsa.pub state=absent

Evidence timeline and material changes

Published upstream
Nov 6, 2024
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Nov 5, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.

Affected scope and exposure questions

The current feed maps ansible-core (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
ansible-coregeneric	>=0 <2.14.18rc1 \|\| >=2.15.0b1 <2.15.13rc1 \|\| >=2.16.0b1 <2.16.13rc1 \|\| >=2.17.0b1 <2.17.6rc1 \|\| >=2.18.0b1 <2.18.0rc2	2.14.18rc1, 2.15.13rc1, 2.16.13rc1, 2.17.6rc1, 2.18.0rc2

Recommended response

Check inventory. Check lockfiles and deployed manifests for ansible-core.

Review the reported fix. Source-reported workaround: In the play that uses the user module with the key generation option, have a prior task ensuring the public key does not exist for example: - name: avoid user exploit (change name depending on other options used in user task) file: path=/home/{{username}}/.ssh/id_rsa.pub state=absent

Sources and claim methodology

Upstream source description

Quoted source text, attributed separately from HOL analysis.