All changesredhatas of 2026-09-07
CVE-2024-8775
red hatred hat enterprise linux 10cve.org →this looks wrong →
Record history
5 dated edit eventsPublished
- 7 products named later, not at publication
53 days between eventsProduct addedSource 2ae61d2 — commit 2ae61d2e09c2 in the CVE catalog
- not namedansible automation platform execution environments
15 days between eventsProducts addedSource 66cf12f — commit 66cf12f8ed45 in the CVE catalog
- not namedred hat ansible automation platform 2.5 for rhel 8and 1 more
12 days between eventsProducts addedSource b994e9d — commit b994e9d85cac in the CVE catalog
- not namedred hat ansible automation platform 2.4 for rhel 8and 1 more
69 days between eventsProduct addedSource 92c04f0 — commit 92c04f0ffce3 in the CVE catalog
- not nameddiscovery 1 for rhel 9
145 days between eventsProduct addedSource a7efbef — commit a7efbefa102c in the CVE catalog
- not namedred hat enterprise linux 10
429 days to snapshotSnapshot
Source record: View on CVE.org ↗
GitHub advisories naming this CVE
2 advisory rows 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-jpxc-vmjf-9fcjCVE-2024-8775 | not named as affected when the advisory was published, now names ansible-core | high | |
| Advisory severity changed | GHSA-jpxc-vmjf-9fcjCVE-2024-8775 | whole advisory | stated at publication MODERATE, now states HIGHThe severity label changed while the stated CVSS vectors stayed the same. | 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 my CVEs
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. Verify one finding yourself →
Data sources and quality
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.
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 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.