Bug 2408694 - CVE-2025-61725 buildah: Excessive CPU consumption in ParseAddress in net/mail [fedora-43]
Summary: CVE-2025-61725 buildah: Excessive CPU consumption in ParseAddress in net/mail...
Keywords:
Status: ON_QA
Alias: None
Product: Fedora
Classification: Fedora
Component: buildah
Version: 43
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Lokesh Mandvekar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["28009fd4-f2e2-490d-a5a3-7...
Depends On:
Blocks: CVE-2025-61725
TreeView+ depends on / blocked
 
Reported: 2025-10-30 23:11 UTC by Jon Moroney
Modified: 2025-11-04 04:20 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jon Moroney 2025-10-30 23:11:53 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

The following link provides references to all essential vulnerability management information. If something is wrong or missing, please contact a member of PSIRT.
https://spaces.redhat.com/display/PRODSEC/Vulnerability+Management+-+Essential+Documents+for+Engineering+Teams

Comment 1 Fedora Update System 2025-11-03 21:15:40 UTC
FEDORA-2025-8f97b687c8 (buildah-1.42.0-4.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-8f97b687c8

Comment 2 Fedora Update System 2025-11-04 04:20:38 UTC
FEDORA-2025-8f97b687c8 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-8f97b687c8`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-8f97b687c8

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.


Note You need to log in before you can comment on or make changes to this bug.