Advisory record · GHSA-q3m2-crgq-5p3q

OpenStack Ironic before 29.0.1 can write unintended files to a target node disk during image handling (if a deployment was performed via the API). A malicious project assigned as a node owner can p...

CVSS 2.8 LowEPSS 0.0019 · 8th percentile

Published by the GitHub Advisory Database at 8 May 2025, 17:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
ironicPyPI<24.1.3 || >=25.0.0, <26.1.1 || >=27.0.0, <29.0.124.1.3, 26.1.1, 29.0.1
Identifiers
GHSA-q3m2-crgq-5p3q · CVE-2025-44021 · PYSEC-2025-38
Weakness (CWE)
CWE-22
Published
8 May 2025
Updated
10 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

OpenStack Ironic versions before 24.1.3, from 25.0.0 before 26.1.1, from 27.0.0 before 29.0.1 are vulnerable. An attacker who is a project assigned as a node owner, and who can trigger a deployment through the API, can cause files readable by ironic-conductor to be written to the target node's disk. Exploitation is difficult in practice, and the risk is mainly for environments with insecure settings such as disabled automated cleaning. Upgrade to 24.1.3, 26.1.1, or 29.0.1, depending on your release line.

Written 10 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
2.8 Low 3.1 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N CNA (mitre)
  • CISA KEV Not listed.
  • EPSS 0.0019, the 8th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 8 May 2025. New records show when each source confirmed them.

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.