Product added
| 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. | Record, 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 changed | Days 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. |
|---|---|---|---|---|
| Mon 3 Jul 2023· 10 changes | ||||
| 2023-07-03 | CVE-2023-3333 | NEC | not named as affected at publication, now names aterm wg300hp | Time to revision 5 days |
| 2023-07-03 | CVE-2023-3333 | NEC | not named as affected at publication, now names aterm wg600hp | Time to revision 5 days |
| 2023-07-03 | CVE-2023-3333 | NEC | not named as affected at publication, now names aterm wr8170n | Time to revision 5 days |
| 2023-07-03 | CVE-2023-3333 | NEC | not named as affected at publication, now names aterm wr8175n | Time to revision 5 days |
| 2023-07-03 | CVE-2023-3333 | NEC | not named as affected at publication, now names aterm wr8370n | Time to revision 5 days |
| 2023-07-03 | CVE-2023-3333 | NEC | not named as affected at publication, now names aterm wr8600n | Time to revision 5 days |
| 2023-07-03 | CVE-2023-3333 | NEC | not named as affected at publication, now names aterm wr8700n | Time to revision 5 days |
| 2023-07-03 | CVE-2023-3333 | NEC | not named as affected at publication, now names aterm wr8750n | Time to revision 5 days |
| 2023-07-03 | CVE-2023-3333 | NEC | not named as affected at publication, now names aterm wr9300n | Time to revision 5 days |
| 2023-07-03 | CVE-2023-3333 | NEC | not named as affected at publication, now names aterm wr9500n | Time to revision 5 days |
| Fri 30 Jun 2023· 10 changes | ||||
| 2023-06-30 | CVE-2023-24895 | not named as affected at publication, now names powershell 7.2 | Time to revision 16 days | |
| 2023-06-30 | CVE-2023-24895 | not named as affected at publication, now names powershell 7.3 | Time to revision 16 days | |
| 2023-06-30 | CVE-2023-24936 | not named as affected at publication, now names powershell 7.2 | Time to revision 16 days | |
| 2023-06-30 | CVE-2023-24936 | not named as affected at publication, now names powershell 7.3 | Time to revision 16 days | |
| 2023-06-30 | CVE-2023-29331 | not named as affected at publication, now names powershell 7.2 | Time to revision 16 days | |
| 2023-06-30 | CVE-2023-29331 | not named as affected at publication, now names powershell 7.3 | Time to revision 16 days | |
| 2023-06-30 | CVE-2023-32032 | not named as affected at publication, now names powershell 7.3 | Time to revision 17 days | |
| 2023-06-30 | CVE-2023-33126 | not named as affected at publication, now names powershell 7.2 | Time to revision 17 days | |
| 2023-06-30 | CVE-2023-33128 | not named as affected at publication, now names powershell 7.3 | Time to revision 17 days | |
| 2023-06-30 | CVE-2023-24897 | not named as affected at publication, now names powershell 7.2 | Time to revision 16 days | |
| Wed 21 Jun 2023· 55 changes | ||||
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r00cpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r01cpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r02cpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r04cpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r04encpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r08cpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r08encpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r08pcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r08psfcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r08sfcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r120cpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r120encpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r120pcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r120psfcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r120sfcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r12ccpu-v | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r16cpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r16encpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r16pcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r16psfcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r16sfcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r32cpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r32encpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r32pcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r32psfcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series r32sfcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec iq-r series rj71en71 | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-l series l02cpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-l series l02cpu-p | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-l series l06cpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-l series l06cpu-p | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-l series l26cpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-l series l26cpu-bt | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-l series l26cpu-p | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-l series l26cpu-pbt | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-l series lj71e71-100 | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series q03udecpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series q03udvcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series q04udehcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series q04udpvcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series q04udvcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series q06udehcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series q06udpvcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series q06udvcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series q100udehcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series q10udehcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series q13udehcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series q13udpvcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series q13udvcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series q20udehcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series q26udehcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series q26udpvcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series q26udvcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series q50udehcpu | Time to revision 110 days |
| 2023-06-21 | CVE-2023-0457 | Mitsubishi | not named as affected at publication, now names melsec-q series qj71e71-100 | Time to revision 110 days |
| Mon 19 Jun 2023· 1 change | ||||
| 2023-06-19 | CVE-2023-3311 | VulDB | not named as affected at publication, now names online-shopping-system-advanced | Time to revision 1 days |
| Fri 16 Jun 2023· 1 change | ||||
| 2023-06-16 | CVE-2023-2431 | not named as affected at publication, now names kubernetes | Time to revision 0 days | |
| Wed 14 Jun 2023· 1 change | ||||
| 2023-06-14 | CVE-2023-1709 | icscert | not named as affected at publication, now names library apdfl | Time to revision 7 days |
| Thu 8 Jun 2023· 1 change | ||||
| 2023-06-08 | CVE-2023-29403 | Go | not named as affected at publication, now names runtime | Time to revision 0 days |
| Tue 6 Jun 2023· 1 change | ||||
| 2023-06-06 | CVE-2023-22833 | not named as affected at publication, now names com.palantir.lime:lime2 | Time to revision 0 days | |
| Mon 22 May 2023· 10 changes | ||||
| 2023-05-22 | CVE-2023-28649 | icscert | not named as affected at publication, now names ovrc cloud | Time to revision 0 days |
| 2023-05-22 | CVE-2023-26117 | vendor not named snyk | not named as affected at publication, now names org.webjars.bower:angular | Time to revision 53 days |
| 2023-05-22 | CVE-2023-26117 | vendor not named snyk | not named as affected at publication, now names org.webjars.bowergithub.angular:angular | Time to revision 53 days |
| 2023-05-22 | CVE-2023-26117 | vendor not named snyk | not named as affected at publication, now names org.webjars.npm:angular | Time to revision 53 days |
| 2023-05-22 | CVE-2023-26118 | vendor not named snyk | not named as affected at publication, now names org.webjars.bower:angular | Time to revision 53 days |
| 2023-05-22 | CVE-2023-26118 | vendor not named snyk | not named as affected at publication, now names org.webjars.bowergithub.angular:angular | Time to revision 53 days |
| 2023-05-22 | CVE-2023-26118 | vendor not named snyk | not named as affected at publication, now names org.webjars.npm:angular | Time to revision 53 days |
| 2023-05-22 | CVE-2023-26116 | vendor not named snyk | not named as affected at publication, now names org.webjars.bower:angular | Time to revision 53 days |
| 2023-05-22 | CVE-2023-26116 | vendor not named snyk | not named as affected at publication, now names org.webjars.bowergithub.angular:angular | Time to revision 53 days |
| 2023-05-22 | CVE-2023-26116 | vendor not named snyk | not named as affected at publication, now names org.webjars.npm:angular | Time to revision 53 days |
| Fri 19 May 2023· 1 change | ||||
| 2023-05-19 | CVE-2023-27945 | not named as affected at publication, now names macos | Time to revision 12 days | |
| Wed 17 May 2023· 1 change | ||||
| 2023-05-17 | CVE-2023-27482 | GitHub_M | not named as affected at publication, now names supervisor | Time to revision 71 days |
| Wed 10 May 2023· 1 change | ||||
| 2023-05-10 | CVE-2023-25568 | GitHub_M | not named as affected at publication, now names boxo | Time to revision 1 days |
| Fri 28 Apr 2023· 1 change | ||||
| 2023-04-28 | CVE-2023-24934 | not named as affected at publication, now names microsoft malware protection platform | Time to revision 14 days | |
| Tue 18 Apr 2023· 4 changes | ||||
| 2023-04-18 | CVE-2023-0595 | schneider | not named as affected at publication, now names ecostruxure geo scada expert 2019 | Time to revision 54 days |
| 2023-04-18 | CVE-2023-0595 | schneider | not named as affected at publication, now names ecostruxure geo scada expert 2020 | Time to revision 54 days |
| 2023-04-18 | CVE-2023-0595 | schneider | not named as affected at publication, now names ecostruxure geo scada expert 2021 | Time to revision 54 days |
| 2023-04-18 | CVE-2023-2043 | VulDB | not named as affected at publication, now names rhid | Time to revision 4 days |
This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller.
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 →