All changesredhatas of 2026-09-07
CVE-2023-5868
red hatred hat advanced cluster security 4.2cve.org →this looks wrong →
Record history
5 dated edit eventsPublished
- 4 products named later, not at publication
1 day between eventsExcluded comparisonnot countedSource 0939e4d — commit 0939e4d97abb in the CVE catalog
- fixed from 8090020231114113712.a75119d5, now fixed from 8090020231128173330.a75119d5red hat enterprise linux 8
Filtered, not counted: another release branch was added — every branch stated at publication is still stated, so 8090020231114113712.a75119d5 still holds.
2 days between eventsProduct addedSource 9738d11 — commit 9738d1172ee0 in the CVE catalog
- not namedred hat software collections for red hat enterprise linux 7
37 days between eventsProduct addedSource a3b7743 — commit a3b77436288a in the CVE catalog
- not namedrhacs-3.74-rhel-8
3 days between eventsProduct addedSource fb645ff — commit fb645ff6cc2a in the CVE catalog
- not namedrhacs-4.1-rhel-8
3 days between eventsProduct addedSource d5af38e — commit d5af38ed30ad in the CVE catalog
- not namedred hat advanced cluster security 4.2
956 days to snapshotSnapshot
Source record: View on CVE.org ↗
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.
1 row marked filtered, not counted is 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.
The GitHub Advisory Database was read and carries no changed advisory naming CVE-2023-5868. 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.
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 ed5547afbae2. 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.