CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-32274 remediation guide

psf black, Red Hat Ansible Automation Platform 2.5, Red Hat Ansible Automation Platform 2.6

Black is the uncompromising Python code formatter. Starting in version 24.3.0 and prior to version 26.3.1, Black writes a cache file, the name of which is computed from various formatting options. The value of the --python-cell-magics option was placed in the filename without sanitization, which allowed an attacker who controls the value of this argument to write cache files to arbitrary file system locations. Fixed in Black 26.3.1.

Open CVE record
Productpsf black, Red Hat Ansible Automation Platform 2.5, Red Hat Ansible Automation Platform 2.6
Affected versions>= >= 24.3.0, < 26.3.1
Fixed versions26.3.1
Priority basisReview · CVSS 8.7 · EPSS 0.62%
01

Identify the affected asset

Confirm whether psf black, Red Hat Ansible Automation Platform 2.5, Red Hat Ansible Automation Platform 2.6 is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= >= 24.3.0, < 26.3.1. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 26.3.1. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.