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.

379 changes · newest first · grouped by dayCSVJSONRSS

SinceClear the filter
ChangedSourceRows
Counted changes published by Mitsubishi, newest first, one line per change to a CVE record, 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, Which record was edited, by its CVE id, or how many records one collapsed line stands on.Vendor · product, 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.
Thu 15 Feb 2024· 3 changes
2024-02-15Product addedCVE-2023-4625Mitsubishinot named as affected at publication, now names melsec iq-r series r32cpuTime to revision 101 days
2024-02-15Product addedCVE-2023-4625Mitsubishinot named as affected at publication, now names melsec iq-r series r32encpuTime to revision 101 days
2024-02-15Product addedCVE-2023-4625Mitsubishinot named as affected at publication, now names melsec iq-r series r32pcpuTime to revision 101 days
Fri 7 Jul 2023· 21 changes
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r00cpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r01cpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r02cpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r04cpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r04encpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r08cpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r08encpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r08pcpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r08sfcpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r120cpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r120encpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r120pcpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r120sfcpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r16cpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r16encpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r16pcpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r16sfcpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r32cpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r32encpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r32pcpuTime to revision 44 days
2023-07-07Product addedCVE-2023-1424Mitsubishinot named as affected at publication, now names melsec iq-r series r32sfcpuTime to revision 44 days
Wed 21 Jun 2023· 55 changes
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r00cpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r01cpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r02cpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r04cpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r04encpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r08cpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r08encpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r08pcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r08psfcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r08sfcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r120cpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r120encpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r120pcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r120psfcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r120sfcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r12ccpu-vTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r16cpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r16encpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r16pcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r16psfcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r16sfcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r32cpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r32encpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r32pcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r32psfcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series r32sfcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec iq-r series rj71en71Time to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-l series l02cpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-l series l02cpu-pTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-l series l06cpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-l series l06cpu-pTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-l series l26cpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-l series l26cpu-btTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-l series l26cpu-pTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-l series l26cpu-pbtTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-l series lj71e71-100Time to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series q03udecpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series q03udvcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series q04udehcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series q04udpvcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series q04udvcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series q06udehcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series q06udpvcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series q06udvcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series q100udehcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series q10udehcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series q13udehcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series q13udpvcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series q13udvcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series q20udehcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series q26udehcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series q26udpvcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series q26udvcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series q50udehcpuTime to revision 110 days
2023-06-21Product addedCVE-2023-0457Mitsubishinot named as affected at publication, now names melsec-q series qj71e71-100Time to revision 110 days

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 →