All changesredhatas of 2026-09-07
CVE-2024-9355
red hatsatellite client 6 for rhel 10cve.org →this looks wrong →
Record history
4 dated edit eventsPublished
- 4 products named later, not at publication
51 days between eventsProduct addedSource 8d9521f — commit 8d9521ffc50c in the CVE catalog
- not namedred hat enterprise linux 7 extended lifecycle support
174 days between eventsProducts addedSource 76ddeb8 — commit 76ddeb8f0f58 in the CVE catalog
- not namedsatellite client 6 for rhel 8and 1 more
234 days between eventsProduct addedSource c28028b — commit c28028ba81c2 in the CVE catalog
- not namedsatellite client 6 for rhel 10
226 days between eventsExcluded comparisonnot countedSource bbdfd6a — commit bbdfd6a42ce3 in the CVE catalog
- not namedred hat enterprise linux 9.2 update services for sap solutionsand 1 more
Filtered, not counted: support or installation label under already affected red hat/red hat enterprise linux 9; the record does not establish whether this newly names affected scope or refines the existing product listing.
21 days to snapshotSnapshot
Source record: View on CVE.org ↗
GitHub advisories naming this CVE
1 advisory row across 1 advisory, counted separately from the record's own rows above.
| Change | Advisory | Ecosystem / package | What the advisory says now | Severity |
|---|---|---|---|---|
| Package added to advisory | GHSA-3h3x-2hwv-hr52CVE-2024-9355 | not named as affected when the advisory was published, now names github.com/golang-fips/openssl | high |
An advisory is an entry in the GitHub Advisory Database, the GHSA page a Dependabot alert links to. It is reached from a CVE id only when the advisory names that CVE id itself, and many advisories name none. So no advisory here means none was found among the advisories that name one of these ids. It does not mean there is nothing to find.
Check your tickets
Add your patched version to compare it with the recorded boundary.
Change cards link to the source commit. Compare CVE values with the first mirrored record and KEV values with the preceding catalog snapshot. The full recipe →
Data coverage & methodology
CVE values compare the first mirrored record with later source states. Initial records may have been backfilled after publication. KEV events compare consecutive catalog snapshots. Dates identify the reported value’s first observed appearance; earlier intermediate revisions may exist. Only counted rows contribute to totals. as of the 2026-09-07 snapshot.
2 rows marked filtered, not counted are on the rail and counted nowhere. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site.
Not checked: a record published before 2023 cannot have its state at publication recovered, so the CVE-record checks never compared it. For such a record, silence on this page means it was not looked at, not that it held.
Not checked: a CISA KEV listing added before 2025-01-27 was never seen changing, so a record that has been in KEV for years carries no listing node here. A missing KEV node is not evidence that CISA has not listed it.
How every one of these figures is measured, in full →
A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.
Shipped snapshot computed 2026-09-07 from catalog commit f5f9fc6fd7dc. Real findings, not live ones: records amended since are not reflected. A later fix version is evidence that the record changed, not evidence that the first fix was incomplete.