Skip to content

All changesredhatas of 2026-09-07

CVE-2026-11332

red hatred hat satellite 6.18 for rhel 9cve.orgthis looks wrong →

Record history

10 dated edit events
  1. Published

    • 21 products named later, not at publication
    35 days between events
  2. Products addedSource 10fef19commit 10fef19cfb8e in the CVE catalog

    • not namedred hat enterprise linux 10, red hat enterprise linux 8and 1 more
    • not namedopenshift service mesh 3and 2 more
    3 days between events
  3. Product addedSource bad630acommit bad630a12e57 in the CVE catalog

    • not namedred hat discovery 2
    7 days between events
  4. Products addedSource 63a07c8commit 63a07c8d809a in the CVE catalog

    • not namedred hat ansible automation platform 2.6 for rhel 10and 1 more
    Same calendar day
  5. Products addedSource 0550248commit 055024821531 in the CVE catalog

    • not namedred hat ansible automation platform 2.5 for rhel 8and 1 more
    Same calendar day
  6. Products addedSource cc228e8commit cc228e85e595 in the CVE catalog

    • not namedred hat ansible automation platform 2.7 for rhel 10and 1 more
    3 days between events
  7. Products addedSource 20ad1fecommit 20ad1fe1013c in the CVE catalog

    • not namedmigration toolkit for applications 8and 4 more
    12 days between events
  8. Product addedSource 287e7fccommit 287e7fc238b4 in the CVE catalog

    • not namedred hat ansible automation platform 2.6
    Same calendar day
  9. Products addedSource 4e774edcommit 4e774ede342e in the CVE catalog

    • not namedred hat ansible automation platform 2.5and 1 more
    30 days between events
  10. Product addedSource f192ca5commit f192ca56d184 in the CVE catalog

    • not namedred hat satellite 6.17 for rhel 9
    1 day between events
  11. Products addedSource 82668d9commit 82668d994a22 in the CVE catalog

    • not namedred hat satellite 6.18 for rhel 9and 1 more
    3 days to snapshot
  12. 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.

3 rows marked filtered, not counted are 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-2026-11332. 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.