VulnerabilityPublished 24 Sep 2026Updated 3 Nov 2026

CVE-2026-90959: Red Hat Ansible Automation Platform 2.6 for RHEL 9 · Improper Limitation of a Pathname to a Restricted Directory

Affects Red Hat Ansible Automation Platform 2.6 for RHEL 9Source CVE Database V5

Compare

Not known to be exploited · CVSS 8.1 High.

Data as of 8 Nov 2026, 11:36 UTC

CVSS 3.1 base score

8.1High

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.1	8.1

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 8 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red Hat Ansible Automation Platform 2.6 for RHEL 9python3.12-pulpcore	Affected–	Fixed in–
Red Hat Ansible Automation Platform 2.6ansible-automation-platform-26/hub-rhel9	Affected–	Fixed in–
Red Hat Ansible Automation Platform 2.7ansible-automation-platform-27/hub-rhel9	Affected–	Fixed in–
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/hub-rhel8	Affected–	Fixed in–
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/hub-rhel8	Affected–	Fixed in–
Red Hat Ansible Automation Platform 2pulpcore-selinux	Affected–	Fixed in–

AI-suggested

Currently, no mitigation is available that meets Red Hat Product Security's standards for usability, deployment, applicability, or stability. Users should monitor Red Hat advisories for updates and patches addressing this vulnerability.

Description

CVE-2026-90959 is a path traversal vulnerability in pulpcore's content upload API of Red Hat Ansible Automation Platform 2.6 for RHEL 9. It arises from improper validation of the 'file_url' parameter, allowing authenticated users with low repository privileges to read arbitrary files accessible to the Pulp server process. In deployments with Pulp Container, exploitation can lead to theft of the container registry token signing private key, enabling attackers to forge bearer tokens and gain unauthorized access to private container repositories.

Impact

An attacker with low-privilege authenticated access can read any file accessible to the Pulp server process, which may include sensitive data. In deployments including Pulp Container, the attacker can steal the registry JWT signing private key and forge bearer tokens, granting unauthorized read and write access to all private container repositories in the affected registry. This results in high confidentiality and integrity impact but no availability impact.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 12:48 UTC

Technical details

References

Community reviews

Related threats