All changesredhatas of 2026-09-07
CVE-2024-3056
red hatred hat enterprise linux 10CVSS 7.7 high nowcve.org →this looks wrong →
Record history
2 dated edit eventsPublished
- CVSS 4.8 medium
- 1 product named later, not at publication
75 days between eventsRescoredSource fe9f19e — commit fe9f19e70406 in the CVE catalog
- Before4.8After7.7medium → highCVSS v3.1 · published base score
230 days between eventsProduct addedSource c4547b9 — commit c4547b974700 in the CVE catalog
- not namedred hat enterprise linux 10
461 days to snapshotSnapshot
- CVSS 7.7 high
GitHub advisories naming this CVE
5 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-rpcc-p8xm-rc6pCVE-2024-3056 | not named as affected when the advisory was published, now names github.com/containers/podman | high | |
| Package added to advisory | 3 packages | 3 rows | see each row | |
| same kind of edit as the line above | GHSA-rpcc-p8xm-rc6pCVE-2024-3056 | not named as affected when the advisory was published, now names github.com/containers/podman/v2 | high | |
| same kind of edit as the line above | GHSA-rpcc-p8xm-rc6pCVE-2024-3056 | not named as affected when the advisory was published, now names github.com/containers/podman/v3 | high | |
| same kind of edit as the line above | GHSA-rpcc-p8xm-rc6pCVE-2024-3056 | not named as affected when the advisory was published, now names github.com/containers/podman/v4 | high | |
| Advisory severity changed | GHSA-rpcc-p8xm-rc6pCVE-2024-3056 | 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 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.
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.