Skip to content

All changesredhatas of 2026-09-07

CVE-2025-6020

red hatrhoss-1.36-rhel-8cve.orgthis looks wrong →

Record history

13 dated edit events
  1. Published

    • 15 products named later, not at publication
    20 days between events
  2. Products addedSource 23cbf2acommit 23cbf2a831d7 in the CVE catalog

    • not namedred hat enterprise linux 8.2 advanced update supportand 2 more
    10 days between events
  3. Product addedSource 3b0d150commit 3b0d1507bd49 in the CVE catalog

    • not namedrhel-8 based middleware containers
    4 days between events
  4. Product addedSource 2e24834commit 2e24834fc20e in the CVE catalog

    • not namedred hat discovery 2
    52 days between events
  5. Product addedSource a4cf1a5commit a4cf1a5f14d0 in the CVE catalog

    • not namedred hat openshift sandboxed containers 1.1
    4 days between events
  6. Product addedSource 670ef83commit 670ef8361c1a in the CVE catalog

    • not namedred hat web terminal 1.12 on rhel 9
    Same calendar day
  7. Product addedSource ec809f3commit ec809f3371ce in the CVE catalog

    • not namedred hat web terminal 1.11 on rhel 9
    29 days between events
  8. Product addedSource 3b2b8c2commit 3b2b8c20c9b9 in the CVE catalog

    • not namedred hat enterprise linux 10
    2 days between events
  9. Product addedSource 071aeddcommit 071aedd705c3 in the CVE catalog

    • not namedcert-manager operator for red hat openshift 1.16
    21 days between events
  10. Product addedSource efbb56bcommit efbb56bb4ba9 in the CVE catalog

    • not namedred hat insights proxy 1.5
    14 days between events
  11. Product addedSource f725b94commit f725b9464c56 in the CVE catalog

    • not namedcompliance operator 1
    5 days between events
  12. Product addedSource c08f1d0commit c08f1d096055 in the CVE catalog

    • not namedred hat enterprise linux 10.0 extended update support
    49 days between events
  13. Product addedSource fe5a7edcommit fe5a7ed27f2a in the CVE catalog

    • not namedred hat openshift distributed tracing 3.6.0
    9 days between events
  14. Product addedSource 7a3ba82commit 7a3ba82c6256 in the CVE catalog

    • not namedrhoss-1.36-rhel-8
    228 days to snapshot
  15. Snapshot

    Source record: View on CVE.org ↗

Check your tickets

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. 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.

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