Skip to content

Update registry.redhat.io/openshift4/ose-operator-sdk-rhel9 Docker digest to 1657337 [SECURITY] - #121

Open
red-hat-konflux[bot] wants to merge 1 commit into
tech-previewfrom
konflux/mintmaker/tech-preview/docker-registry.redhat.io-openshift4-ose-operator-sdk-rhel9-vulnerability
Open

red-hat-konflux[bot] wants to merge 1 commit into
tech-previewfrom
konflux/mintmaker/tech-preview/docker-registry.redhat.io-openshift4-ose-operator-sdk-rhel9-vulnerability

Conversation

@red-hat-konflux

@red-hat-konflux red-hat-konflux Bot commented Oct 16, 2026 •

Copy link
Copy Markdown

This PR contains the following updates:

Package Type Update Change
registry.redhat.io/openshift4/ose-operator-sdk-rhel9 final digest 8ff0cb8 → 1657337

Kubelet: CRI-O: kube-apiserver: Kubelet, CRI-O, kube-apiserver: Denial of Service via SPDY streaming code

CVE-2026-35469

More information

Details

A flaw was found in the SPDY streaming code used by Kubelet, CRI-O, and kube-apiserver. An attacker with specific cluster roles, such as those allowing access to pod port forwarding, execution, or attachment, or node proxying, could exploit this vulnerability. This could lead to a Denial of Service (DoS) by causing the affected components to become unresponsive.

Severity

Important

References


net/http/internal/http2: golang: golang.org/x/net: Go HTTP/2: Denial of Service via malformed SETTINGS_MAX_FRAME_SIZE frame

CVE-2026-33814

More information

Details

A flaw was found in the HTTP/2 protocol implementation within the Go standard library (golang.org/x/net and net/http/internal/http2). A remote attacker can exploit this vulnerability by sending a specially crafted HTTP/2 SETTINGS frame with the SETTINGS_MAX_FRAME_SIZE parameter set to zero. This malicious frame causes the transport layer to enter an infinite loop of writing CONTINUATION frames, leading to resource exhaustion and a Denial of Service (DoS) condition.

Severity

Important

References


golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing

CVE-2026-39821

More information

Details

A flaw was found in golang.org/x/net/idna. ToASCII and ToUnicode incorrectly accept Punycode-encoded labels that decode to an ASCII-only hostname (for example, xn--example-.com returns example.com instead of an error). Applications that validate the ASCII form then convert to Unicode may grant access to a restricted hostname the ASCII check would have rejected.

Severity

Important

References


js-yaml: js-yaml: Denial of Service via exponential parsing in flow collections

CVE-2026-73643

More information

Details

A flaw was found in js-yaml, a JavaScript YAML parser. A remote attacker could exploit this vulnerability by providing specially crafted YAML input containing nested flow collections. This can lead to exponential parsing time when the application processes untrusted input, consuming excessive CPU resources. This resource exhaustion can block the Node.js event loop and cause a Denial of Service (DoS) for the affected process.

Severity

Important

References


golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Denial of Service via crafted AES-GCM packet decoder inputs

CVE-2026-46597

More information

Details

A flaw was found in golang.org/x/crypto/ssh. A remote attacker could send specially crafted inputs to the AES-GCM packet decoder. This could lead to an incorrectly placed cast from bytes to an integer, causing a server-side panic and resulting in a Denial of Service (DoS) for the affected system.

Severity

Important

References


js-yaml: js-yaml: Denial of Service via crafted YAML documents

CVE-2026-59869

More information

Details

A flaw was found in js-yaml, a JavaScript YAML parser and dumper. A remote attacker could exploit this vulnerability by providing a specially crafted YAML document containing a chain of mappings with merge keys. This could cause the parser to consume excessive CPU resources, leading to a Denial of Service (DoS) for the affected system.

Severity

Important

References


fast-uri: fast-uri: Authority Injection via Unvalidated Port Serialization

CVE-2026-84292

More information

Details

A flaw was found in fast-uri. This component improperly serializes the port component of a Uniform Resource Identifier (URI) without validating its content. A remote attacker can exploit this by crafting a malicious port value that injects authority delimiters. This manipulation can demote the intended host to user information and redirect the authority to an attacker-controlled host, leading to information disclosure as applications interpret the attacker's host as legitimate.

Severity

Important

References


js-yaml: js-yaml: Denial of Service vulnerability in YAML parsing

CVE-2026-84375

More information

Details

A flaw was found in js-yaml, a JavaScript YAML parser. An attacker can exploit this by providing a specially crafted YAML document that causes the parser to perform excessive processing when handling merge keys with empty sources. This can lead to prolonged CPU consumption, effectively causing a denial of service (DoS) for applications that process untrusted YAML input.

Severity

Important

References


fast-uri: fast-uri: Host confusion via unbalanced URI brackets can bypass security policies

CVE-2026-84394

More information

Details

A flaw was found in fast-uri. The library incorrectly processes Uniform Resource Identifier (URI) hosts containing unbalanced brackets, leading to a discrepancy in how the host is parsed by fast-uri compared to other HTTP clients. This host confusion can allow an attacker to bypass security policies, such as Server-Side Request Forgery (SSRF) denylists or redirect allowlists, by causing an application to evaluate its policy against an incorrect host string. This could result in unintended network requests or access to unauthorized resources.

Severity

Important

References


brace-expansion: Brace-expansion: Denial of Service via memory exhaustion in expand() function

CVE-2026-14257

More information

Details

A flaw was found in brace-expansion. A remote attacker can exploit this vulnerability by providing specially crafted input to the expand() function, which can lead to excessive memory consumption. This can cause a denial of service (DoS) by crashing the application due to an out-of-memory error.

Severity

Important

References


brace-expansion: DoS via unbounded intermediate arrays, bypassing the CVE-2026-14257 mitigation

CVE-2026-69152

More information

Details

A flaw was found in the brace-expansion library. The expand() function does not apply maxLength when constructing comma-alternative intermediate arrays or padded sequences, allowing attacker-controlled input to exhaust memory or block the event loop, resulting in a denial of service. This issue is due to an incomplete mitigation of CVE-2026-14257.

Severity

Important

References


crypto/tls: crypto/tls: Incorrect certificate validation during TLS session resumption

CVE-2025-68121

More information

Details

A flaw was found in the crypto/tls component. This vulnerability occurs during Transport Layer Security (TLS) session resumption when certificate authority (CA) settings are modified between the initial and resumed handshakes. An attacker could exploit this to bypass certificate validation, allowing a client or server to establish a connection that should have been rejected. This could lead to an authentication bypass under specific conditions.

Severity

Important

References


crypto/x509: crypto/tls: golang: Go: Denial of Service vulnerability in certificate chain building

CVE-2026-32280

More information

Details

A flaw was found in the Go standard library packages crypto/x509 and crypto/tls. During the process of building a certificate chain, an attacker can provide a large number of intermediate certificates. This excessive input is not properly limited, leading to an uncontrolled amount of work being performed. This can result in a denial of service (DoS) condition, making the affected system or application unavailable to legitimate users.

Severity

Important

References


net: golang: Go net package: Denial of Service via long CNAME response in LookupCNAME

CVE-2026-33811

More information

Details

A flaw was found in the net package of Go (golang), specifically when using the LookupCNAME function with the cgo DNS resolver. A remote attacker could exploit this by providing a very long Canonical Name (CNAME) response. This can trigger a double-free of C memory, leading to a crash and a Denial of Service (DoS) for the affected application.

Severity

Important

References


brace-expansion: Brace-expansion: Denial of Service due to exponential-time complexity

CVE-2026-13149

More information

Details

A flaw was found in brace-expansion. An attacker can exploit a vulnerability in the expand() function by providing a specially crafted string. This string, containing consecutive non-expanding brace groups, can trigger exponential-time complexity, leading to significant CPU consumption and event-loop blocking. This can result in a Denial of Service (DoS) for the affected system.

Severity

Important

References


crypto/x509: golang: golang crypto/x509: Denial of Service via excessive processing of DNS SAN entries

CVE-2026-27145

More information

Details

A flaw was found in the crypto/x509 package of golang. This vulnerability allows a remote attacker to cause a Denial of Service (DoS) by presenting a specially crafted X.509 certificate with a large number of DNS Subject Alternative Name (SAN) entries. The certificate verification process, specifically the VerifyHostname function, incurs excessive computational overhead due to repeated string operations when processing these entries. This can lead to a significant performance degradation or unresponsiveness of systems validating such certificates.

Severity

Important

References


mime: golang: Golang MIME: Denial of Service via maliciously-crafted MIME header

CVE-2026-42504

More information

Details

A flaw was found in the Golang MIME (Multipurpose Internet Mail Extensions) package. A remote attacker could exploit this vulnerability by sending a maliciously-crafted MIME header containing many invalid encoded-words. This could lead to excessive CPU consumption, resulting in a Denial of Service (DoS) for the affected system.

Severity

Important

References


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

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

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • 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 force-pushed the konflux/mintmaker/tech-preview/docker-registry.redhat.io-openshift4-ose-operator-sdk-rhel9-vulnerability branch from df5bc3b to 9634765 Compare October 28, 2026 04:07
@red-hat-konflux red-hat-konflux Bot changed the title Update registry.redhat.io/openshift4/ose-operator-sdk-rhel9 Docker digest to 79651ea [SECURITY] Update registry.redhat.io/openshift4/ose-operator-sdk-rhel9 Docker digest to 6012f3f [SECURITY] Oct 28, 2026
…gest to 1657337 [SECURITY]

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/tech-preview/docker-registry.redhat.io-openshift4-ose-operator-sdk-rhel9-vulnerability branch from 9634765 to a1b2379 Compare November 7, 2026 04:14
@red-hat-konflux red-hat-konflux Bot changed the title Update registry.redhat.io/openshift4/ose-operator-sdk-rhel9 Docker digest to 6012f3f [SECURITY] Update registry.redhat.io/openshift4/ose-operator-sdk-rhel9 Docker digest to 1657337 [SECURITY] Nov 7, 2026
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.

0 participants