Skip to content

Conversation

@red-hat-konflux
Copy link
Contributor

This PR contains the following updates:

File rpms.in.yaml:

Package Change
gcc-toolset-14-gcc 14.2.1-10.el8_10 -> 14.2.1-11.el8_10
gcc-toolset-14-gcc-c++ 14.2.1-10.el8_10 -> 14.2.1-11.el8_10
gcc-toolset-14-libstdc++-devel 14.2.1-10.el8_10 -> 14.2.1-11.el8_10
python3.12 3.12.12-1.el8_10 -> 3.12.12-2.el8_10
python3.12-libs 3.12.12-1.el8_10 -> 3.12.12-2.el8_10
brotli 1.0.6-3.el8 -> 1.0.6-4.el8_10
libselinux 2.9-10.el8_10 -> 2.9-11.el8_10
libselinux-devel 2.9-10.el8_10 -> 2.9-11.el8_10
libselinux-utils 2.9-10.el8_10 -> 2.9-11.el8_10
python3-libselinux 2.9-10.el8_10 -> 2.9-11.el8_10

cpython: python: Python zipfile End of Central Directory (EOCD) Locator record offset not checked

CVE-2025-8291

More information

Details

The 'zipfile' module would not check the validity of the ZIP64 End of
Central Directory (EOCD) Locator record offset value would not be used to
locate the ZIP64 EOCD record, instead the ZIP64 EOCD record would be
assumed to be the previous record in the ZIP archive. This could be abused
to create ZIP archives that are handled differently by the 'zipfile' module
compared to other ZIP implementations.

Remediation maintains this behavior, but checks that the offset specified
in the ZIP64 EOCD Locator record matches the expected value.

Severity

Moderate

References


Scrapy: python-scrapy: brotli: Python brotli decompression bomb DoS

CVE-2025-6176

More information

Details

Scrapy are vulnerable to a denial of service (DoS) attack due to a flaw in its brotli decompression implementation. The protection mechanism against decompression bombs fails to mitigate the brotli variant, allowing remote servers to crash clients with less than 80GB of available memory. This occurs because brotli can achieve extremely high compression ratios for zero-filled data, leading to excessive memory consumption during decompression.

Severity

Important

References

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: Branch creation - "" in timezone Etc/UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux bot requested review from a team and rhacs-bot as code owners February 10, 2026 13:07
@red-hat-konflux red-hat-konflux bot enabled auto-merge (squash) February 10, 2026 13:07
Copy link

@rhacs-bot rhacs-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approved by automation.

@red-hat-konflux red-hat-konflux bot merged commit ef3497d into release-0.2 Feb 10, 2026
40 of 41 checks passed
@red-hat-konflux red-hat-konflux bot deleted the konflux/mintmaker/release-0.2/lock-file-maintenance-vulnerability branch February 10, 2026 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant