Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.5amended

Ansible may expose private key

CVE-2023-4237GHSA-ww3m-ffrm-qvqv

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 ansible-core

    Affected
    >= 2.8.0, <= 2.15.2
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
EPSS
  • CVE-2023-4237: 0.25% estimated exploitation activity in the next 30 days; percentile 16.70 (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 flaw was found in the Ansible Automation Platform. When creating a new keypair, the ec2key module prints out the private key directly to the standard output. This flaw allows an attacker to fetch those keys from the log files, compromising the system's confidentiality, integrity, and availability.

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

    Amended from ghsa record GHSA-ww3m-ffrm-qvqv

  2. Revision 1 · created ·

    Published from osv record GHSA-ww3m-ffrm-qvqv

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-2023-4237

Advisory: Ansible may expose private key
IDs: CVE-2023-4237, GHSA-ww3m-ffrm-qvqv
Record: https://patchnext.com/advisories/cve-2023-4237 (revision 2, source checked 26 Oct 2026, 13:12 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
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 ansible-core: affected >= 2.8.0, <= 2.15.2

## Suggested inspection (read-only)
- `python -m pip show ansible-core`: 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 ansible-core.
- 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-ww3m-ffrm-qvqv (OSV record GHSA-ww3m-ffrm-qvqv lists affected ranges: PyPI ansible-core >=2.8.0 <=2.15.2)
- Verified: https://github.com/advisories/GHSA-ww3m-ffrm-qvqv (GitHub-reviewed advisory GHSA-ww3m-ffrm-qvqv lists affected ranges: PyPI ansible-core >=2.8.0 <=2.15.2)

Commands are suggestions: review each one before running it.

Loading voting…