Skip to content

NO-ISSUE: Refresh RPM lockfiles [SECURITY]#1466

Open
red-hat-konflux[bot] wants to merge 1 commit into
release-ocm-2.13from
konflux/mintmaker/release-ocm-2.13/rpm-lockfile-refresh-vulnerability
Open

NO-ISSUE: Refresh RPM lockfiles [SECURITY]#1466
red-hat-konflux[bot] wants to merge 1 commit into
release-ocm-2.13from
konflux/mintmaker/release-ocm-2.13/rpm-lockfile-refresh-vulnerability

Conversation

@red-hat-konflux

@red-hat-konflux red-hat-konflux Bot commented May 20, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

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


Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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.

@red-hat-konflux red-hat-konflux Bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. rpm-lockfile labels May 20, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 20, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@red-hat-konflux[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

This PR contains the following updates:

File rpm-prefetching/rpms.in.yaml:

Package Change
aardvark-dns 2:1.16.0-1.el9 -> 2:1.17.0-1.el9
conmon 3:2.1.13-1.el9 -> 3:2.2.1-1.el9
containers-common 4:1-135.el9_7 -> 5:5.8-1.el9
crun 1.27-1.el9_7 -> 1.27-1.el9_8
netavark 2:1.16.0-1.el9 -> 2:1.17.2-1.el9
nmap 3:7.92-3.el9 -> 3:7.92-5.el9
nmap-ncat 3:7.92-3.el9 -> 3:7.92-5.el9
passt 0^20250512.g8ec1341-4.el9_7 -> 0^20251210.gd04c480-4.el9_8
podman 6:5.6.0-14.el9_7 -> 6:5.8.2-1.el9_8
chrony 4.6.1-2.el9 -> 4.8-1.el9
device-mapper 9:1.02.206-2.el9_7.2 -> 9:1.02.207-4.el9
device-mapper-libs 9:1.02.206-2.el9_7.2 -> 9:1.02.207-4.el9
dhcp-client 12:4.4.2-19.b1.el9 -> 12:4.4.2-20.b1.el9
dhcp-common 12:4.4.2-19.b1.el9 -> 12:4.4.2-20.b1.el9
file 5.39-16.el9 -> 5.39-17.el9
hwdata 0.348-9.20.el9 -> 0.348-9.22.el9
libatomic 11.5.0-11.el9 -> 11.5.0-14.el9
libedit 3.1-38.20210216cvs.el9 -> 3.1-39.20210216cvs.el9
libibverbs 57.0-2.el9 -> 61.0-2.el9
librdmacm 57.0-2.el9 -> 61.0-2.el9
openssh 8.7p1-49.el9_7 -> 9.9p1-7.el9_8
openssh-clients 8.7p1-49.el9_7 -> 9.9p1-7.el9_8
shadow-utils-subid 2:4.9-15.el9 -> 2:4.9-16.el9
daxctl-libs 78-2.el9 -> 82-1.el9
ndctl-libs 78-2.el9 -> 82-1.el9

crun: crun: Privilege escalation due to incorrect parsing of the --user option

CVE-2026-30892

More information

Details

A flaw was found in crun, an open-source OCI Container Runtime. A local user can exploit this vulnerability due to incorrect parsing of the --user option when using crun exec. The value 1 is misinterpreted as root privileges (User ID 0 and Group ID 0) instead of the intended User ID 1 and Group ID 0. This allows a process to run with higher privileges than expected, leading to privilege escalation.

Severity

Moderate

References


OpenSSH: OpenSSH: Arbitrary command execution via shell metacharacters in username

CVE-2026-35386

More information

Details

A flaw was found in OpenSSH. This vulnerability allows a remote attacker to achieve arbitrary command execution by injecting shell metacharacters into a username provided on the command line. Exploitation requires an untrusted username and a non-default configuration of the '%' character in ssh_config.

Severity

Important

References


OpenSSH: OpenSSH: Information disclosure due to unintended cryptographic algorithm usage

CVE-2026-35387

More information

Details

A flaw was found in OpenSSH. This vulnerability allows the system to use unintended Elliptic Curve Digital Signature Algorithm (ECDSA) algorithms. This occurs because the configuration for accepted public key algorithms is misinterpreted, leading to the use of weaker cryptographic methods than intended. This could potentially allow an attacker to compromise the confidentiality of data.

Severity

Important

References


OpenSSH: OpenSSH: Privilege escalation via scp legacy protocol when not preserving file mode

CVE-2026-35385

More information

Details

A flaw was found in OpenSSH. When the scp command is used by a root user to download a file with the legacy protocol option (-O) and without preserving original file permissions (-p), the downloaded file can be installed with elevated privileges (setuid or setgid). This unexpected behavior could allow a malicious file to execute with higher permissions than intended, posing a security risk through potential privilege escalation.

Severity

Important

References


OpenSSH: OpenSSH: Low integrity impact from unconfirmed proxy-mode multiplexing sessions

CVE-2026-35388

More information

Details

A flaw was found in OpenSSH. This vulnerability allows for a low integrity impact due to the omission of connection multiplexing confirmation for proxy-mode multiplexing sessions. A local user, under specific and complex conditions requiring user interaction, could potentially establish a multiplexed session without explicit confirmation, leading to unintended data handling.

Severity

Important

References


OpenSSH: OpenSSH: Security bypass via mishandling of authorized_keys principals option

CVE-2026-35414

More information

Details

A flaw was found in OpenSSH. This vulnerability arises from the incorrect handling of the authorized_keys principals option in uncommon scenarios. Specifically, when a principals list is used with a Certificate Authority that includes comma characters, OpenSSH may misinterpret the input. This could lead to security bypasses, potentially allowing unintended access or information disclosure in specific authentication contexts.

Severity

Important

References

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


Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@coderabbitai

coderabbitai Bot commented May 20, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 0fbfea87-e15f-4fae-b541-4cfb4cd2f841

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch konflux/mintmaker/release-ocm-2.13/rpm-lockfile-refresh-vulnerability

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label May 20, 2026
@openshift-ci openshift-ci Bot requested review from gamli75 and romfreiman May 20, 2026 09:19
@codecov

codecov Bot commented May 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.81%. Comparing base (aaf2e36) to head (a0d7117).
⚠️ Report is 4 commits behind head on release-ocm-2.13.

Additional details and impacted files

Impacted file tree graph

@@                Coverage Diff                @@
##           release-ocm-2.13    #1466   +/-   ##
=================================================
  Coverage             56.81%   56.81%           
=================================================
  Files                    88       88           
  Lines                  4272     4272           
=================================================
  Hits                   2427     2427           
  Misses                 1674     1674           
  Partials                171      171           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux Bot force-pushed the konflux/mintmaker/release-ocm-2.13/rpm-lockfile-refresh-vulnerability branch from f5267a0 to a0d7117 Compare May 20, 2026 15:00
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label May 20, 2026
@openshift-ci

openshift-ci Bot commented May 20, 2026

Copy link
Copy Markdown

New changes are detected. LGTM label has been removed.

@openshift-ci

openshift-ci Bot commented May 20, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: red-hat-konflux[bot]

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci

openshift-ci Bot commented May 20, 2026

Copy link
Copy Markdown

@red-hat-konflux[bot]: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-ci openshift-ci Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 20, 2026
@openshift-ci

openshift-ci Bot commented Jun 20, 2026

Copy link
Copy Markdown

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. rpm-lockfile size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant