[GHSA-q4gv-pjmh-c735] Add v1.1.3 as patched version for release-1.1 backport - #8953
Open
inbharajmani wants to merge 2 commits into
Conversation
The original PR had overlapping ranges (both starting at introduced: 0), so the 0→1.2.1 range still marked v1.1.3 as vulnerable. Split into non-overlapping ranges: - Range 1: 0 → fixed 1.1.3 (release-1.1 line) - Range 2: 1.2.0 → fixed 1.2.1 (release-1.2 line) The fix was backported to release-1.1 as v1.1.3: https://github.com/open-cluster-management-io/ocm/commits/v1.1.3/
github-actions
Bot
changed the base branch from
main
to
inbharajmani/advisory-improvement-8953
August 3, 2026 08:46
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the advisory to correctly represent patched versions across OCM release lines, preventing false positives for v1.1.3.
Changes:
- Marks v1.1.3 as fixed.
- Adds a separate vulnerable range for v1.2.0 through v1.2.1.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates
Changes
The fix for CVE-2026-4740 was backported to the
release-1.1branch and tagged asv1.1.3:https://github.com/open-cluster-management-io/ocm/commits/v1.1.3/
The original advisory only listed
>= 1.2.1as patched, which caused false positives for allv1.1.xconsumers.Before (single range):
introduced: 0→fixed: 1.2.1(marks everything < 1.2.1 as vulnerable, including the patched v1.1.3)After (two non-overlapping ranges):
introduced: 0→fixed: 1.1.3(release-1.1 line)introduced: 1.2.0→fixed: 1.2.1(release-1.2 line)Evidence
release-1.1:3ff36c41— "Match the exact cluster name for csr renewal ([GHSA-2c84-35rv-6q3f] Jenkins ClearCase Release Plugin 0.3 and earlier does not... #1478)"9e70cc1e— "Match the exact cluster name for csr renewal ([GHSA-j6p9-hm3q-hwmj] A cross-site request forgery (CSRF) vulnerability in... #1476)"