Skip to content
patchdrift.
snapshot 2026-09-07

All changesredhatas of 2026-09-07

CVE-2025-14512

red hatred hat discovery 2cve.org →this looks wrong →

Record history

7 dated edit events

  1. Published

    • 8 products named later, not at publication
    11 days between events

  2. Product addedSource c9eb92a — commit c9eb92ae124a in the CVE catalog

    • not namedglib
    112 days between events

  3. Product addedSource 9ccf0ac — commit 9ccf0ac32276 in the CVE catalog

    • not namedred hat hardened images
    37 days between events

  4. Products addedSource 266c5fe — commit 266c5fe8aabc in the CVE catalog

    • not namedred hat enterprise linux 8.4 advanced mission critical update supportand 1 more
    7 days between events

  5. Product addedSource e461971 — commit e46197134995 in the CVE catalog

    • not namedred hat update infrastructure 5
    6 days between events

  6. Product addedSource c0ee8b9 — commit c0ee8b95cedf in the CVE catalog

    • not namedred hat insights proxy 1.5
    8 days between events

  7. Product addedSource 688f27c — commit 688f27c4e7a0 in the CVE catalog

    • not namedred hat ai inference server 3.2
    14 days between events

  8. Product addedSource 049b02e — commit 049b02ef17c9 in the CVE catalog

    • not namedred hat discovery 2
    75 days to snapshot

  9. Snapshot

    Source record: View on CVE.org ↗

Check my CVEs

Add your patched version to compare it with the recorded boundary.

One per line · up to 500 IDs

Versions & supported formats

Add a patched version beside a CVE to compare it. GHSA versions are not compared. Product names are also supported. Results include a watchlist link, RSS and JSON.

Privacy & sharingData & methodology

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.

The GitHub Advisory Database was read and carries no changed advisory naming CVE-2025-14512. 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.