cve.bz

CVE-2026-103754 Path traversal

5.9 mediumEPSS 0.3%

Medium (5.9). EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw was found in ansible-runner. The unstream_dir() function, which receives and extracts a streamed zip archive on the worker side of the ansible-runner transmit/worker protocol, re-creates symbolic links from archive content without validating the link target and applies chmod() and utime() to an unsanitized filesystem path derived from the archive member name. A crafted archive processed by a worker that consumes attacker-influenced input can create files, create symbolic links, or change permissions outside the intended target directory, which can be leveraged toward code execution.

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 27th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-103754 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103754?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103754?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-103754 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14ansible-runnerno fix listedDEBIAN-CVE-2026-103754
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 1 moreansible-runnerno fix listedUBUNTU-CVE-2026-103754

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate severity flaw was found in ansible-runner, affecting the automation-controller component of Red Hat Ansible Automation Platform. The unstream_dir() function, used on the worker side of the ansible-runner transmit/worker protocol, extracts a streamed zip archive while re-creating symbolic links from the archive content without validating their targets, and applies chmod()/utime() to an unsanitized filesystem path derived from the archive member names. A crafted archive processed by a worker that consumes attacker-influenced input can therefore create files, create symbolic links, or change permissions outside the intended target directory, which can be leveraged toward code execution. In the standard Ansible Automation Platform deployment the transmit stream is produced by the trusted controller and the controller-to-executor path is authenticated, so there the issue is primarily a defense-in-depth hardening concern; deployments that feed untrusted input into ansible-runner's worker path are directly exposed. Red Hat and the upstream CVE record both rate this flaw as moderate impact (CVSS 3.1 score 5.9), so there is no difference from the upstream severity assessment. A fix is deferred for the affected Ansible Automation Platform streams because exploitation requires attacker-influenced input to reach the worker's extraction path, which the standard trusted controller-to-executor topology prevents; the residual risk is limited to deployments that pass untrusted input into ansible-runner's worker path until a fix is applied. The ansible_automation_platform-2.4 stream is out of support scope and will not receive an update for this issue.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. The upstream ansible-runner project has a fix available via the referenced pull request; upgrading to a release that includes the upstream fix is the recommended resolution. As an additional measure, ensuring that only the trusted automation-controller produces the transmit stream consumed by ansible-runner workers (the standard authenticated Ansible Automation Platform topology) limits exposure to this flaw.

ProductPackageStateAdvisory
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/controller-rhel9Fix deferred
Red Hat Ansible Automation Platform 2automation-controllerFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-103754.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON