Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.7amended

awxkit has a path traversal vulnerability

CVE-2026-52902GHSA-g29c-rgq6-gxgj

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI awxkit

    Affected
    <= 24.6.1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.7 · CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-52902: 0.13% estimated exploitation activity in the next 30 days; percentile 2.50 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

A path traversal vulnerability was found in awxkit, the CLI tool for AWX. The YAML !include directive does not sanitize file paths, allowing an attacker to craft a malicious YAML file that reads arbitrary YAML-formatted files from the local filesystem when a user imports it using "awx --conf.format yaml import". This is a client-side vulnerability requiring user interaction.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-g29c-rgq6-gxgj

  2. Revision 1 · created ·

    Published from osv record GHSA-g29c-rgq6-gxgj

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-52902

Advisory: awxkit has a path traversal vulnerability
IDs: CVE-2026-52902, GHSA-g29c-rgq6-gxgj
Record: https://patchnext.com/advisories/cve-2026-52902 (revision 2, source checked 26 Oct 2026, 13:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI awxkit: affected <= 24.6.1

## Suggested inspection (read-only)
- `python -m pip show awxkit`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on awxkit.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-g29c-rgq6-gxgj (OSV record GHSA-g29c-rgq6-gxgj lists affected ranges: PyPI awxkit >=0 <=24.6.1)
- Verified: https://github.com/advisories/GHSA-g29c-rgq6-gxgj (GitHub-reviewed advisory GHSA-g29c-rgq6-gxgj lists affected ranges: PyPI awxkit >=0 <=24.6.1)

Commands are suggestions: review each one before running it.

Loading voting…