Skip to content

Every change, newest first

What a record said when it was published, what it says now, and the commit that changed it.

70 changes behind one line · newest firstCSVJSONRSS

SinceClear all

Showing changes seen on 2026-03-30. Every day

One change, in full: Product added: mediatek chipset named as affected from mediatek, inc.. The same change in 70 CVE records. Back to the ledger

Counted changes changed on 2026-03-30, newest first, one line per change to a CVE record or a GHSA advisory, or per run of identical changes collapsed into one line.
Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin.KindRecord or advisory, Which record was edited: a CVE id where the change was to the CVE catalog or the CISA KEV list, a GHSA id where it was to a GitHub advisory. The two are different units and are never counted together.Vendor or package, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry.What changedDays to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong.
2026-03-30Product addedCVE-2025-20760MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20761MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20762MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20778MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20779MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20780MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20781MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20782MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20783MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20784MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20785MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20786MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20787MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20793MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20794MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20795MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20796MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20797MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20798MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20799MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20800MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20801MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20802MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20803MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20804MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20805MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20806MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2025-20807MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 84 days
2026-03-30Product addedCVE-2026-20401MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20402MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20403MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20404MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20405MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20406MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20407MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20408MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20410MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20411MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20412MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20413MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20414MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20415MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20416MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20417MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20418MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20419MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20420MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20421MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20422MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days
2026-03-30Product addedCVE-2026-20423MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20424MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20425MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20426MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20427MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20428MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20429MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20430MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20434MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20435MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20436MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20437MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20438MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20439MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20440MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20441MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20442MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20443MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20444MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20445MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 28 days
2026-03-30Product addedCVE-2026-20409MediaTeknot named as affected at publication, now names mediatek chipsetTime to revision 56 days

Two units, never added: changes to a CVE record or KEV entry, and changes to a GitHub advisory. Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory.

What this page cannot see

Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.

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.

The units, the refusals, the cut-offs and every source, in full →

Paste your closed CVE tickets and see which of these changes hit them →