Skip to content

[Project Darkstar] ROSAENG-60658: Remediate CVE-2026-27145, CVE-2026-42504 in rosa#3382

Draft
kseiter-rh wants to merge 1 commit into
openshift:masterfrom
kseiter-rh:cve-fix/rosa-darkstar-2026-07-16
Draft

[Project Darkstar] ROSAENG-60658: Remediate CVE-2026-27145, CVE-2026-42504 in rosa#3382
kseiter-rh wants to merge 1 commit into
openshift:masterfrom
kseiter-rh:cve-fix/rosa-darkstar-2026-07-16

Conversation

@kseiter-rh

@kseiter-rh kseiter-rh commented Jul 16, 2026

Copy link
Copy Markdown

Project Darkstar — Automated CVE Remediation

This PR was generated by Project Darkstar, an automated CVE remediation tool.
For questions or concerns, contact Kevin Seiter (ROSA Trust Engineering).

Summary

  • Fixes 2 Important Go stdlib CVEs by bumping go directive in go.mod from 1.26.3 to 1.26.4
  • Builder Dockerfiles already reference go-toolset:1.26.4; this update formally enforces the minimum Go toolchain requirement

CVE Details

CVE-2026-27145 (Important, CVSS 7.5)

  • Package: crypto/x509 (Go stdlib)
  • Description: (*x509.Certificate).VerifyHostname called strings.Split(host, ".") repeatedly in a loop over all DNS SAN entries, causing quadratic verification cost with large SAN lists. Exploitable by unauthenticated clients presenting a crafted certificate.
  • Fixed in: Go 1.26.4
  • Jira: ROSAENG-60658

CVE-2026-42504 (Important, CVSS 7.5)

  • Package: mime (Go stdlib)
  • Description: WordDecoder.DecodeHeader exhibited quadratic complexity when processing maliciously crafted MIME headers, enabling denial-of-service attacks.
  • Fixed in: Go 1.26.4
  • Jira: ROSAENG-60661

Changes

  • go.mod: go 1.26.3go 1.26.4

Already Fixed (11 CVEs — no action needed)

The following CVEs discovered in Jira were already resolved by previous automated dependency updates:

CVE Component Current Fix Version
CVE-2026-39828 golang.org/x/crypto/ssh v0.54.0 v0.52.0
CVE-2026-39829 golang.org/x/crypto/ssh v0.54.0 v0.52.0
CVE-2026-39830 golang.org/x/crypto/ssh v0.54.0 v0.52.0
CVE-2026-39831 golang.org/x/crypto/ssh v0.54.0 v0.52.0
CVE-2026-46595 golang.org/x/crypto/ssh v0.54.0 v0.52.0
CVE-2026-46597 golang.org/x/crypto/ssh v0.54.0 v0.52.0
CVE-2026-39835 golang.org/x/crypto/ssh v0.54.0 v0.53.0
CVE-2026-33811 Go stdlib net go1.26.3 go1.26.3
CVE-2026-39821 golang.org/x/net/idna v0.56.0 v0.55.0
CVE-2026-25681 golang.org/x/net/html v0.56.0 v0.55.0
CVE-2026-27136 golang.org/x/net/html v0.56.0 v0.55.0

Verification

  • go build ./... passes
  • No dependency graph changes (only Go toolchain minimum version bumped)
  • Consistent with Dockerfile builder image (go-toolset:1.26.4)

References


Project Darkstar — Automated CVE Remediation | Contact: Kevin Seiter (ROSA Trust Engineering)

Summary by CodeRabbit

  • Chores
    • Updated the Go toolchain version to 1.26.4.

…42504 — update Go toolchain directive to 1.26.4

Addresses CVE-2026-27145 (Important, CVSS 7.5) and CVE-2026-42504 (Important, CVSS 7.5),
both fixed in Go 1.26.4. Bumps the go directive in go.mod from 1.26.3 to 1.26.4 to formally
enforce the minimum Go toolchain version; builder Dockerfiles already use go-toolset:1.26.4.

Ref: ROSAENG-60658, ROSAENG-60661
Project Darkstar — automated CVE remediation (contact: Kevin Seiter)

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 16, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 16, 2026

Copy link
Copy Markdown

@kseiter-rh: This pull request references ROSAENG-60658 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the vulnerability to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Project Darkstar — Automated CVE Remediation

This PR was generated by Project Darkstar, an automated CVE remediation tool.
For questions or concerns, contact Kevin Seiter (ROSA Trust Engineering).

Summary

  • Fixes 2 Important Go stdlib CVEs by bumping go directive in go.mod from 1.26.3 to 1.26.4
  • Builder Dockerfiles already reference go-toolset:1.26.4; this update formally enforces the minimum Go toolchain requirement

CVE Details

CVE-2026-27145 (Important, CVSS 7.5)

  • Package: crypto/x509 (Go stdlib)
  • Description: (*x509.Certificate).VerifyHostname called strings.Split(host, ".") repeatedly in a loop over all DNS SAN entries, causing quadratic verification cost with large SAN lists. Exploitable by unauthenticated clients presenting a crafted certificate.
  • Fixed in: Go 1.26.4
  • Jira: ROSAENG-60658

CVE-2026-42504 (Important, CVSS 7.5)

  • Package: mime (Go stdlib)
  • Description: WordDecoder.DecodeHeader exhibited quadratic complexity when processing maliciously crafted MIME headers, enabling denial-of-service attacks.
  • Fixed in: Go 1.26.4
  • Jira: ROSAENG-60661

Changes

  • go.mod: go 1.26.3go 1.26.4

Already Fixed (11 CVEs — no action needed)

The following CVEs discovered in Jira were already resolved by previous automated dependency updates:

CVE Component Current Fix Version
CVE-2026-39828 golang.org/x/crypto/ssh v0.54.0 v0.52.0
CVE-2026-39829 golang.org/x/crypto/ssh v0.54.0 v0.52.0
CVE-2026-39830 golang.org/x/crypto/ssh v0.54.0 v0.52.0
CVE-2026-39831 golang.org/x/crypto/ssh v0.54.0 v0.52.0
CVE-2026-46595 golang.org/x/crypto/ssh v0.54.0 v0.52.0
CVE-2026-46597 golang.org/x/crypto/ssh v0.54.0 v0.52.0
CVE-2026-39835 golang.org/x/crypto/ssh v0.54.0 v0.53.0
CVE-2026-33811 Go stdlib net go1.26.3 go1.26.3
CVE-2026-39821 golang.org/x/net/idna v0.56.0 v0.55.0
CVE-2026-25681 golang.org/x/net/html v0.56.0 v0.55.0
CVE-2026-27136 golang.org/x/net/html v0.56.0 v0.55.0

Verification

  • go build ./... passes
  • No dependency graph changes (only Go toolchain minimum version bumped)
  • Consistent with Dockerfile builder image (go-toolset:1.26.4)

References


Project Darkstar — Automated CVE Remediation | Contact: Kevin Seiter (ROSA Trust Engineering)

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.

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 16, 2026
@openshift-ci

openshift-ci Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@coderabbitai

coderabbitai Bot commented Jul 16, 2026

Copy link
Copy Markdown
📝 Walkthrough

Walkthrough

The Go toolchain directive in go.mod is updated from version 1.26.3 to 1.26.4. No other module declarations or exported entities are changed.

Possibly related issues

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly states the CVE remediation and the Go version bump, matching the main change in the PR.
Description check ✅ Passed The description covers the problem, the fix, Jira links, and validation, though it does not follow the template headings exactly.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed Only go.mod changed; no test files or Ginkgo titles were modified, so there are no unstable test names to flag.
Test Structure And Quality ✅ Passed Only go.mod changed; no test files or Ginkgo blocks were modified, so the test-quality check is not applicable.
Microshift Test Compatibility ✅ Passed Only go.mod changed; no new Ginkgo e2e tests or MicroShift-unsupported APIs were added.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The PR only bumps go.mod from 1.26.3 to 1.26.4; no Ginkgo e2e tests were added or changed, so SNO compatibility isn’t implicated.
Topology-Aware Scheduling Compatibility ✅ Passed Only go.mod's Go version changed; no deployment manifests, controllers, or scheduling logic were modified, so topology-aware scheduling isn't implicated.
Ote Binary Stdout Contract ✅ Passed Only go.mod changed, and no process-level code or stdout writes were modified.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR only bumps go.mod to 1.26.4; no new Ginkgo e2e tests or network-related code were added.
No-Weak-Crypto ✅ Passed PASS: The diff only bumps the go directive in go.mod; no crypto code or secret comparisons changed in the PR.
Container-Privileges ✅ Passed HEAD changes only go.mod; no container/K8s manifest files were modified, so no privileged/root/allowPrivilegeEscalation flags were introduced.
No-Sensitive-Data-In-Logs ✅ Passed The PR only changes go.mod’s Go version directive; no logging code or log messages were added or modified.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@openshift-ci

openshift-ci Bot commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kseiter-rh
Once this PR has been reviewed and has the lgtm label, please assign jerichokeyne for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@go.mod`:
- Line 3: Update the Go version pin in renovate.json to match the approved
version declared in go.mod, changing it from 1.26.3 to 1.26.4 so Renovate
targets the current version.
- Line 3: Update the Go version from 1.26.4 to at least 1.26.5 consistently in
the go.mod toolchain declaration, the Go builder image pins in Dockerfile,
images/Dockerfile.e2e, and images/Dockerfile.konflux, and the corresponding
version configuration in renovate.json.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: bfcf9269-515a-454f-bf3e-e4ec013e5d1f

📥 Commits

Reviewing files that changed from the base of the PR and between b05862a and 0b2b686.

📒 Files selected for processing (1)
  • go.mod

Comment thread go.mod
module github.com/openshift/rosa

go 1.26.3
go 1.26.4

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Synchronize the Renovate Go pin.

renovate.json still specifies Go 1.26.3, so automation can continue targeting a stale version after this change. Update that pin to the same approved Go version as go.mod.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@go.mod` at line 3, Update the Go version pin in renovate.json to match the
approved version declared in go.mod, changing it from 1.26.3 to 1.26.4 so
Renovate targets the current version.

🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '--- go.mod ---\n'
cat -n go.mod | sed -n '1,20p'

printf '\n--- Dockerfile matches ---\n'
rg -n 'go\s+1\.26|1\.26\.' Dockerfile* . || true

printf '\n--- renovate.json ---\n'
cat -n renovate.json | sed -n '1,220p' || true

Repository: openshift/rosa

Length of output: 243


🌐 Web query:

Go 1.26.5 release July 7 2026 CVE-2026-42505 OSV Go 1.26.4 1.26.5

💡 Result:

Go 1.26.5 was released on July 7, 2026, to address security vulnerabilities and include various bug fixes [1][2]. CVE-2026-42505 refers to a privacy vulnerability in the crypto/tls package where the Encrypted Client Hello (ECH) implementation would leak pre-shared key (PSK) identities during the handshake [3][4]. This leak allowed a passive network observer to de-anonymize the server's hostname even when ECH was in use [5][3]. The fix, addressed in Go 1.26.5 and Go 1.25.12, involves omitting the PSK extension in the outer client hello when using ECH [6]. Additionally, Go 1.26.5 addresses CVE-2026-39822, a root escape vulnerability in the os package on Unix systems where paths with trailing slashes could improperly follow symlinks outside of a specified os.Root [3][4]. Go 1.26.5 includes the following changes from Go 1.26.4: - Security fixes for CVE-2026-42505 and CVE-2026-39822 [1][3]. - Bug fixes to the compiler, the runtime, the go command, and the net, os, and syscall packages [1][7]. For users compiling from source, the release can be accessed by checking out the tag go1.26.5 [2].

Citations:


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '--- go.mod ---'
cat -n go.mod | sed -n '1,20p'

echo
echo '--- Dockerfile* Go version matches ---'
rg -n '1\.26\.[0-9]+' Dockerfile* . || true

echo
echo '--- renovate.json ---'
if [ -f renovate.json ]; then
  cat -n renovate.json | sed -n '1,240p'
fi

Repository: openshift/rosa

Length of output: 18204


Bump the Go toolchain to 1.26.5+

go.mod is still on 1.26.4, and the Go builder images are pinned there too (Dockerfile, images/Dockerfile.e2e, images/Dockerfile.konflux). Update these pins together and align renovate.json, since 1.26.5 carries the current Go 1.26 security fixes.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@go.mod` at line 3, Update the Go version from 1.26.4 to at least 1.26.5
consistently in the go.mod toolchain declaration, the Go builder image pins in
Dockerfile, images/Dockerfile.e2e, and images/Dockerfile.konflux, and the
corresponding version configuration in renovate.json.

Source: Path instructions

@amandahla

Copy link
Copy Markdown
Contributor

Hi @kseiter-rh , thanks for submitting the PR

Bumping Go is planned after this PR is merged:
#3366

Would be OK to wait and follow this plan instead of bumping immediately? Our CI is not prepared for that.

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

Labels

dco-signoff: yes do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants