Repository navigation
Conversation
|
Is that actually gems/activestorage/GHSA-f3w6-w445-fwh9.yml? |
|
@simi Looks like it ... what a fucking shitshow the reporting situation is right now. |
|
Updated one advisory and deleted dup advisory - add dup to ignore file - upgraded python in GHA script. |
flavorjones
left a comment
There was a problem hiding this comment.
Seems fine, though I wonder if we'll get another CVE for this if/when github finally assigns one to the original GHSA. 🤷♂
I vote to wait until that happens and deal with it then. |
|
Hilarious, github just assigned CVE-2026-126082. 🤷♂ |
Therefore it is a duplicate of CVE-2026-126082 and will be add to the rad-ignores file. |
Added comments regarding CVE-2026-126082 and its duplicate.
jasnow
left a comment
There was a problem hiding this comment.
Fixed merge conflict. LGTM
flavorjones
left a comment
There was a problem hiding this comment.
Note that CVE-2026-126082 is no longer a "valid" CVE. On 2026-11-12 its CVE record was rejected with the reason "This CVE is a duplicate of another CVE." The same day, GitHub withdrew GHSA-wgv4-95jc-33jm ("Duplicate Advisory: Active Storage: Possible arbitrary file write and read in Active Storage image analysis") and published GHSA-f3w6-w445-fwh9 to the global advisory database with CVE-2026-122006. So cve: 2026-122006 in the advisory is right.
The Rails repository advisory still lists CVE-2026-126082, and a stale copy of the advisory database may still carry it, so a sync could still write gems/activestorage/CVE-2026-126082.yml. I think rad-ignores.sh should remove that file explicitly.
Co-authored-by: Mike Dalessio <mike.dalessio@gmail.com>
Co-authored-by: Mike Dalessio <mike.dalessio@gmail.com>
|
Applied your suggestion. Ready for re-Review. |
One new activestorage advisory