CVE-2025-47273VulnerabilityPublished 26 Aug 2025Updated 19 Oct 2026

Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.5 Product Security and Bug Fix Update

Affects Red Hat pip-toolsSource GCVE Database

Mentioned vulnerabilities

CVE-2025-48432

Not known to be exploited · fixed in Red Hat package updates : update Red Hat pip-tools when convenient.

Data as of 26 Oct 2026, 17:16 UTC

Severity

Medium

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

EPSS: 1.5% chance of exploitation in 30 days – higher than 75% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.4.1_2, 1.11.0_7, 78.1.1

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, 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

Upgrade pip-tools to 7.4.1_2; osc-cli to 1.11.0_7; python-setuptools to 78.1.1.

Affected software

Product	Affected	Fixed in
Homebrewpip-tools`pkg:brew/pip-tools`Other threats	Affected >=7.3.0_1 <7.4.1_2	Fixed in 7.4.1_2
Homebrewosc-cli`pkg:brew/osc-cli`Other threats	Affected >=1.11.0_3 <1.11.0_7	Fixed in 1.11.0_7
Homebrewpython-setuptools`pkg:brew/python-setuptools`Other threats	Affected >=68.2.2 <78.1.1	Fixed in 78.1.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

Red Hat Ansible Automation Platform provides an enterprise framework for building, deploying and managing IT automation at scale. IT Managers can provide top-down guidelines on how automation is applied to individual teams, while automation developers retain the freedom to write tasks that leverage existing knowledge without the overhead. Ansible Automation Platform makes it possible for users across an organization to share, vet, and manage automation content by means of a simple, powerful, and agentless language. Security Fix(es): * automation-controller: Path Traversal Vulnerability in setuptools PackageIndex (CVE-2025-47273) * python3.11-django: Django Path Injection Vulnerability (CVE-2025-48432) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. Updates and fixes included: Automation platform * Enhanced Support for Streaming Chat Responses (AAP-51756) * Improved LDAP filter parsing/handling (AAP-51591) * Updated AAP to allow for HTTP headers to be passed through envoy when HTTPS is offloaded by another device in front of envoy (AAP-51347) * Updated the OpenAPI spec to now reflect all available query parameters (AAP-49824) * Added a new field on AzureAD authenticator called 'Field to use as username' which allows use of an arbitrary field from the assertion as the username (AAP-49481) * Fixed migration scenarios that left legacy users in a partly migrated state to now migrate properly to gateway (AAP-43251) * Removed the required label from the Organization field for Galaxy credentials in the controller Credential Create and Edit forms (AAP-51587) * Fixed the 'LOGIN_REDIRECT_OVERRIDE' to be respected (AAP-49726) * Fixed a breadcrumb in a launch template to no longer send users to the wrong URL (AAP-44194) * Fixed the subscription entitlement window to no longer display again after AAP has been entitled when running in a load-balanced environment with multiple controller web pods (AAP-43883) * Updated the AAP User Interface to allow all users to see the Notifiers tab (AAP-41342) * Added the limit field on the job details page (AAP-36118) * automation-gateway has been updated to 2.5.20250827 * python3.11-django-ansible-base has been updated to 2.5.20250827 Automation controller * Galaxy credentials can now be created and edited without the need to specify an organization (AAP-51614) * Fixed the subscription functionality to no longer attach before subscription credentials have been set, and to return a '400 Bad Request' error instead (AAP-50322) * automation-controller has been updated to 4.6.19 Event-Driven Ansible * Fixed project import state to no longer be stuck at pending or running (AAP-51643) * Fixed EDA to allow '%20' in the project git URL (AAP-51642) * Fixed 'MQ_TLS' to accept a boolean value (AAP-51012) * Fixed missing RPM dependency for PostgreSQL client which resulted in container images missing psql binaries (AAP-50941) * Fixed a bug to no longer prevent a user who belonged to a team with an EDA organization Project Admin role to be able see the organization (AAP-50921) * automation-eda-controller has been updated to 1.1.13 Container-based Ansible Automation Platform * Implemented PostgreSQL extra settings parameter on the installer (AAP-51533) * Fixed the Redis hostname to no longer fail to be set in a disconnected environment (AAP-51532) * Updated preflight checks to temporarily check PostgreSQL version to use a CA bundle from the VM server with the custom cert appended, if provided (AAP-50884) * Fixed PCP data permissions by migrating the data to a podman volume instead of a bind mount (AAP-50807) * Fixed a parameter to allow excluding subdirs during the Automation Hub backup process (AAP-50784) * Added an exclusion parameter for Containerized Backup, allowing users to specify snapshot paths to be excluded from the backup process (AAP-46767) * containerized installer setup has been updated to 2.5-18 RPM-based Ansible Automation Platform * Added 'postgres_extra_settings' for postgresql.conf customization for managed database installations (AAP-51462) * Fixed automation controller nodes so they are removed from the gateway registry when set to a deprovision state (AAP-51461) * Fixed the installer to no longer fail when disabling HTTPS for gateway and/or gateway proxy (envoy) (AAP-48606) * ansible-automation-platform-installer and installer setup have been updated to 2.5-17 Additional changes: * automation-hub has been updated to 4.10.7 * python3.11-django has been updated to 4.2.23 * python3.11-galaxy-ng has been updated to 4.10.7

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-117Improper Output Neutralization for Logs (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product constructs a log message from external input, but it does not neutralize or incorrectly neutralizes special elements when the message is written to a log file.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Output Encoding
Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8.
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Logging (opens in a new tab)
Content Security Policy (opens in a new tab)
Application Logging Vocabulary (opens in a new tab)
OWASP ASVS 4.0.3
V7.3.1 (opens in a new tab)
V14.4.6 (opens in a new tab)
V14.4.4 (opens in a new tab)
Attack patterns
Audit Log Manipulation (opens in a new tab)
Web Server Logs Tampering (opens in a new tab)
Log Injection-Tampering-Forging (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

WeaknessesCWE-22, CWE-117

Technical details

References

Community reviews

Related threats