Skip to content

Every change, newest first

Compare earlier and later source statements, with the dates and evidence behind each measured change.

143 record edits refused · 1 advisory changes · newest first · grouped by dayCSVJSONRSS

SinceClear the filter
ChangedSourceRows

These rows are not counted anywhere on this site. 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. No advisory change is here: the advisory engine counts the 2,291 version pairs its filters refused by class rather than writing them out one by one, so this view holds CVE and KEV changes only.

Rows we checked and refused, counted nowhere from the last 7 days, 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.
Sun 6 Sep 2026· 1 change
2026-09-06Product addedCVE-2026-75569not named as affected at publication, now names multicluster engine for kubernetes 2.1Not counted: Product relabelled. probable relabelling of red hat/multicluster engine for kubernetes, not a newly affected productTime to revision 18 days
Sat 5 Sep 2026· 11 changes
2026-09-05Product addednot named as affected at publication, now names multicluster engine for kubernetes 2.1not counted: Product relabelledTime to revision 16 to 31 days
2026-09-05same kind of change as the line aboveCVE-2026-10059same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of red hat/multicluster engine for kubernetes, not a newly affected productTime to revision 31 days
2026-09-05same kind of change as the line aboveCVE-2026-19130same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of red hat/multicluster engine for kubernetes, not a newly affected productTime to revision 24 days
2026-09-05same kind of change as the line aboveCVE-2026-66794same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of red hat/multicluster engine for kubernetes, not a newly affected productTime to revision 17 days
2026-09-05same kind of change as the line aboveCVE-2026-66795same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of red hat/multicluster engine for kubernetes, not a newly affected productTime to revision 19 days
2026-09-05same kind of change as the line aboveCVE-2026-73266same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of red hat/multicluster engine for kubernetes, not a newly affected productTime to revision 23 days
2026-09-05same kind of change as the line aboveCVE-2026-73267same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of red hat/multicluster engine for kubernetes, not a newly affected productTime to revision 16 days
2026-09-05same kind of change as the line aboveCVE-2026-73268same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of red hat/multicluster engine for kubernetes, not a newly affected productTime to revision 24 days
2026-09-05same kind of change as the line aboveCVE-2026-73269same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of red hat/multicluster engine for kubernetes, not a newly affected productTime to revision 24 days
2026-09-05Product addedCVE-2026-85599VulnChecknot named as affected at publication, now names grav-plugin-shortcode-coreNot counted: Product relabelled. probable relabelling of getgrav/grav, not a newly affected productTime to revision 1 days
2026-09-05Product addedCVE-2026-85600VulnChecknot named as affected at publication, now names grav-plugin-admin2Not counted: Product relabelled. probable relabelling of getgrav/grav, not a newly affected productTime to revision 1 days
2026-09-05Product addedCVE-2026-85602VulnChecknot named as affected at publication, now names grav-plugin-formNot counted: Product relabelled. probable relabelling of getgrav/grav, not a newly affected productTime to revision 1 days
Fri 4 Sep 2026· 25 changes
2026-09-04Affected range extendedCVE-2026-14466
stormshieldstormshield network security
airbus
stated at publication 5.0.6, now states 5.1.0Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 5.0.6 still holdsDuration unknown
2026-09-045 commitsProduct added18 rows, one per record and productmitrenot named as affected at publication, now names eds3000ps series and 5 moreBranches and original-value intervals are stated on each row.not counted: No products named at publicationTime to revision 178 days
2026-09-04same kind of change as the line aboveCVE-2025-67041same vendor as the line abovenot named as affected at publication, now names eds3000ps seriesNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromTime to revision 178 days
2026-09-04same kind of change as the line aboveCVE-2025-70082same vendor as the line abovenot named as affected at publication, now names eds3000ps seriesNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromTime to revision 178 days
2026-09-04same kind of change as the line aboveCVE-2025-67038same vendor as the line abovenot named as affected at publication, now names e210 seriesNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromTime to revision 178 days
2026-09-04same kind of change as the line aboveCVE-2025-67038same vendor as the line abovenot named as affected at publication, now names e220 seriesNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromTime to revision 178 days
2026-09-04same kind of change as the line aboveCVE-2025-67038same vendor as the line abovenot named as affected at publication, now names eds5000 seriesNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromTime to revision 178 days
2026-09-04same kind of change as the line aboveCVE-2025-67038same vendor as the line abovenot named as affected at publication, now names g520 seriesNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromTime to revision 178 days
2026-09-04same kind of change as the line aboveCVE-2025-67038same vendor as the line abovenot named as affected at publication, now names x300 seriesNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromTime to revision 178 days
2026-09-04same kind of change as the line aboveCVE-2025-67039same vendor as the line abovenot named as affected at publication, now names eds3000ps seriesNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromTime to revision 178 days
10 more rows in this change are not listed here. Open all 18 rows
2026-09-042 commitsProduct addednot named as affected at publication, now names red hat jboss enterprise application platform 8.1.6Branches and original-value intervals are stated on each row.not counted: Product relabelledTime to revision 240 to 275 days
2026-09-04same kind of change as the line aboveCVE-2024-3884same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of red hat/red hat jboss enterprise application platform 8, not a newly affected productTime to revision 275 days
2026-09-04same kind of change as the line aboveCVE-2025-12543same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of red hat/red hat jboss enterprise application platform 8, not a newly affected productTime to revision 240 days
2026-09-04Product addedCVE-2024-5971not named as affected at publication, now names red hat jboss enterprise application platformNot counted: Already named at publication. already named at publication inside red hat/red hat jboss enterprise application platform 7 — the record spelled this product out all alongTime to revision 788 days
2026-09-04Product addedCVE-2026-77995Joomlanot named as affected at publication, now names miniorange oauth client (free) extension for joomlaNot counted: Product identity rewritten with unchanged scope. unchanged affected scope with a rewritten title of removed miniorange.com/miniorange oauth client extension for joomla; a new product identity is not establishedTime to revision 11 days
2026-09-04Product addedCVE-2026-16493not named as affected at publication, now names red hat satellite 6.18 for rhel 9 and 1 morenot counted: Product relabelledTime to revision 44 days
2026-09-04same kind of change as the line aboveCVE-2026-16493same vendor as the line abovenot named as affected at publication, now names red hat satellite 6.18 for rhel 9Not counted: Product relabelled. probable relabelling of red hat/red hat satellite 6, not a newly affected productTime to revision 44 days
2026-09-04same kind of change as the line aboveCVE-2026-16493same vendor as the line abovenot named as affected at publication, now names red hat satellite 6.19 for rhel 9Not counted: Product relabelled. probable relabelling of red hat/red hat satellite 6, not a newly affected productTime to revision 44 days
Thu 3 Sep 2026· 21 changes
2026-09-03Fix version moved
watchguardfireware os
stated at publication 2026.2.2, now states 2026.3.1Release branch starts at *.not counted: Another branch advancedDuration unknown
2026-09-03same kind of change as the line aboveCVE-2026-13086same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 2026.2.2 still holdsDuration unknown
2026-09-03same kind of change as the line aboveCVE-2026-19313same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 2026.2.2 still holdsDuration unknown
2026-09-03same kind of change as the line aboveCVE-2026-19314same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 2026.2.2 still holdsDuration unknown
2026-09-03same kind of change as the line aboveCVE-2026-19315same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 2026.2.2 still holdsDuration unknown
2026-09-03same kind of change as the line aboveCVE-2026-19316same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 2026.2.2 still holdsDuration unknown
2026-09-03same kind of change as the line aboveCVE-2026-19317same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 2026.2.2 still holdsDuration unknown
2026-09-03same kind of change as the line aboveCVE-2026-19318same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 2026.2.2 still holdsDuration unknown
2026-09-036 commitsProduct addednot named as affected at publication, now names red hat satellite 6.17 for rhel 9 and 5 moreBranches and original-value intervals are stated on each row.not counted: 2 classesTime to revision 3 to 45 days
2026-09-03same kind of change as the line aboveCVE-2026-16493same vendor as the line abovenot named as affected at publication, now names red hat satellite 6.17 for rhel 9Not counted: Product relabelled. probable relabelling of red hat/red hat satellite 6, not a newly affected productTime to revision 44 days
2026-09-03same kind of change as the line aboveCVE-2026-15563same vendor as the line abovenot named as affected at publication, now names red hat fuse 7Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposureTime to revision 24 days
2026-09-03same kind of change as the line aboveCVE-2026-15927same vendor as the line abovenot named as affected at publication, now names red hat quay 3.15Not counted: Product relabelled. probable relabelling of red hat/red hat quay 3, not a newly affected productTime to revision 45 days
2026-09-03same kind of change as the line aboveCVE-2026-12894same vendor as the line abovenot named as affected at publication, now names red hat build of apache camel 3.33 for quarkus 3.33.3.sp1Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposureTime to revision 3 days
2026-09-03same kind of change as the line aboveCVE-2026-17615same vendor as the line abovenot named as affected at publication, now names red hat build of apache camel 3.33 for quarkus 3.33.3.sp1Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposureTime to revision 3 days
2026-09-03same kind of change as the line aboveCVE-2026-49332same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.17Not counted: Product relabelled. probable relabelling of red hat/red hat openshift container platform 4, not a newly affected productTime to revision 37 days
2026-09-03same kind of change as the line aboveCVE-2026-50236same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.17Not counted: Product relabelled. probable relabelling of red hat/red hat openshift container platform 4, not a newly affected productTime to revision 23 days
2026-09-03same kind of change as the line aboveCVE-2026-50237same vendor as the line abovenot named as affected at publication, now names red hat openshift container platform 4.17Not counted: Product relabelled. probable relabelling of red hat/red hat openshift container platform 4, not a newly affected productTime to revision 23 days
2 more rows in this change are not listed here. Open all 10 rows
2026-09-03Product addedCVE-2025-9189NInot named as affected at publication, now names dasylabNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposureTime to revision 366 days
2026-09-03Product addedCVE-2026-0872THA-PSIRTnot named as affected at publication, now names safenet agent for windows logonNot counted: Product relabelled. probable relabelling of thales/safenet agent for windows logon, not a newly affected productTime to revision 202 days
2026-09-03Product addedCVE-2026-3457THA-PSIRTnot named as affected at publication, now names sentinel ldk runtimeNot counted: Product relabelled. probable relabelling of thales/sentinel ldk runtime, not a newly affected productTime to revision 160 days
2026-09-03Product addedCVE-2025-12107not named as affected at publication, now names identity serverNot counted: Product relabelled. probable relabelling of wso2/wso2 identity server, not a newly affected productTime to revision 196 days
Wed 2 Sep 2026· 2 changes
2026-09-02Affected range extendedCVE-2026-82641
keploykeploy
VulnCheck
stated at publication 3.6.25, now states 3.6.26Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 3.6.25 still holdsDuration unknown
2026-09-02published 2026-06-16Package added to advisoryGHSA-9cr8-q42q-g8m7CVE-2026-53622highnot named as affected when the advisory was published, now names github.com/traefik/traefik/v3Time to revision 78 days
Tue 1 Sep 2026· 84 changes
2026-09-01Forensic triage now requiredCVE-2023-49105
ownCloudownCloud
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 5 days
2026-09-01Forensic triage now requiredCVE-2026-53362
LinuxKernel
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 5 days
2026-09-01Forensic triage now requiredCVE-2019-1068
MicrosoftSQL Server
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 6 days
2026-09-01Forensic triage now requiredCVE-2026-60004
GiteaGitea
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 7 days
2026-09-01Forensic triage now requiredCVE-2026-21962
OracleHTTP Server and Oracle Weblogic Server Proxy Plug-in
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 8 days
2026-09-01Forensic triage now requiredCVE-2026-73570
SynacorZimbra Collaboration Suite (ZCS)
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 11 days
2026-09-01Forensic triage now requiredCVE-2026-72529
TrueConfServer
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 12 days
2026-09-01Forensic triage now requiredCVE-2026-59310
BroadcomVMware vCenter
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 14 days
2026-09-01Forensic triage now required
MicrosoftSharePoint
stated at publication not stated, now states Yesnot counted: The prior instruction already required triageTime to revision 14 to 47 days
2026-09-01same kind of change as the line aboveCVE-2026-55040same vendor as the line abovesame change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 14 days
2026-09-01same kind of change as the line aboveCVE-2026-50522same vendor as the line abovesame change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 41 days
2026-09-01same kind of change as the line aboveCVE-2026-58644same vendor as the line abovesame change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 47 days
2026-09-01Forensic triage now requiredCVE-2026-65400
ApplemacOS
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 14 days
2026-09-01Forensic triage now requiredCVE-2025-62593CISA KEVstated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 15 days
2026-09-01Forensic triage now requiredCVE-2026-72898
MetabaseMetabase
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 21 days
2026-09-01Forensic triage now requiredCVE-2026-8037
ProgressLoadMaster
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 25 days
2026-09-01Forensic triage now requiredCVE-2026-63077
JetBrainsTeamCity
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 27 days
2026-09-01Forensic triage now required
N-ableN-central
stated at publication not stated, now states Yesnot counted: The prior instruction already required triageTime to revision 28 to 29 days
2026-09-01same kind of change as the line aboveCVE-2026-18556same vendor as the line abovesame change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 28 days
2026-09-01same kind of change as the line aboveCVE-2026-18577same vendor as the line abovesame change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 29 days
2026-09-01Forensic triage now requiredCVE-2026-9198
IBMLangflow
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 28 days
2026-09-01Forensic triage now requiredCVE-2026-16812
AristaVeloCloud Orchestrator
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 36 days
2026-09-01Forensic triage now requiredCVE-2026-16232
Check PointSmartConsole
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 41 days
2026-09-01Forensic triage now requiredCVE-2026-63030
WordPressCore
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 42 days
2026-09-01Forensic triage now required
LangflowLangflow
stated at publication not stated, now states Yesnot counted: The prior instruction already required triageTime to revision 42 to 56 days
2026-09-01same kind of change as the line aboveCVE-2026-0770same vendor as the line abovesame change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 42 days
2026-09-01same kind of change as the line aboveCVE-2026-55255same vendor as the line abovesame change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 56 days
2026-09-01Forensic triage now requiredCVE-2021-27137
DD-WRTDD-WRT
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 42 days
2026-09-01Forensic triage now required
FortinetFortiSandbox
stated at publication not stated, now states Yesnot counted: The prior instruction already required triageTime to revision 47 days
2026-09-01same kind of change as the line aboveCVE-2026-25089same vendor as the line abovesame change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 47 days
2026-09-01same kind of change as the line aboveCVE-2026-39808same vendor as the line abovesame change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 47 days
2026-09-01Forensic triage now requiredCVE-2026-46817
OracleE-Business Suite
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 48 days
2026-09-01Forensic triage now required
MicrosoftSharePoint Server
stated at publication not stated, now states Yesnot counted: The prior instruction already required triageTime to revision 49 to 62 days
2026-09-01same kind of change as the line aboveCVE-2026-56164same vendor as the line abovesame change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 49 days
2026-09-01same kind of change as the line aboveCVE-2026-45659same vendor as the line abovesame change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 62 days
2026-09-01Forensic triage now required
SonicWallSMA1000 Appliances
stated at publication not stated, now states Yesnot counted: The prior instruction already required triageTime to revision 49 days
2026-09-01same kind of change as the line aboveCVE-2026-15409same vendor as the line abovesame change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 49 days
2026-09-01same kind of change as the line aboveCVE-2026-15410same vendor as the line abovesame change as the line aboveNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 49 days
2026-09-01Forensic triage now requiredCVE-2008-4128
CiscoIOS
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 50 days
2026-09-01Forensic triage now requiredCVE-2026-56291
BalbooaForms
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 53 days
2026-09-01Forensic triage now requiredCVE-2026-48939
iCagendaiCagenda
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 53 days
2026-09-01Forensic triage now requiredCVE-2026-48908
JoomShaperSP Page Builder
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 56 days
2026-09-01Forensic triage now requiredCVE-2026-56290
JoomlackPage Builder
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 56 days
2026-09-01Forensic triage now requiredCVE-2026-48282
AdobeColdFusion
CISA KEV
stated at publication not stated, now states YesNot counted: The prior instruction already required triage. requiredAction already named CISA's Forensics Triage Requirements; the structured field changed, not the first stated requirementTime to revision 56 days
2026-09-012 commitsProduct addedPatchstacknot named as affected at publication, now names the gridBranches and original-value intervals are stated on each row.not counted: Product relabelledTime to revision 14 to 222 days
2026-09-01same kind of change as the line aboveCVE-2026-24370same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of theme-one/the grid, not a newly affected productTime to revision 160 days
2026-09-01same kind of change as the line aboveCVE-2026-24368same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of theme-one/the grid, not a newly affected productTime to revision 222 days
2026-09-01same kind of change as the line aboveCVE-2026-24369same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of theme-one/the grid, not a newly affected productTime to revision 160 days
2026-09-01same kind of change as the line aboveCVE-2026-28191same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of theme-one inc./the grid, not a newly affected productTime to revision 14 days
2026-09-01Product addednot named as affected at publication, now names thunderbirdnot counted: Added entry does not state affected statusTime to revision 0 days
2026-09-01same kind of change as the line aboveCVE-2026-84118same vendor as the line abovesame change as the line aboveNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposureTime to revision 0 days
2026-09-01same kind of change as the line aboveCVE-2026-84119same vendor as the line abovesame change as the line aboveNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposureTime to revision 0 days
2026-09-01same kind of change as the line aboveCVE-2026-84120same vendor as the line abovesame change as the line aboveNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposureTime to revision 0 days
2026-09-01same kind of change as the line aboveCVE-2026-84121same vendor as the line abovesame change as the line aboveNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposureTime to revision 0 days
2026-09-01same kind of change as the line aboveCVE-2026-84122same vendor as the line abovesame change as the line aboveNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposureTime to revision 0 days
2026-09-01same kind of change as the line aboveCVE-2026-84123same vendor as the line abovesame change as the line aboveNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposureTime to revision 0 days
2026-09-01same kind of change as the line aboveCVE-2026-84124same vendor as the line abovesame change as the line aboveNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposureTime to revision 0 days
2026-09-01same kind of change as the line aboveCVE-2026-84125same vendor as the line abovesame change as the line aboveNot counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposureTime to revision 0 days
18 more rows in this change are not listed here. Open all 26 rows
2026-09-01Product addedVulnChecknot named as affected at publication, now names planet gs-4210-16p2s v3not counted: Product relabelledTime to revision 4 days
2026-09-01same kind of change as the line aboveCVE-2026-75121same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected productTime to revision 4 days
2026-09-01same kind of change as the line aboveCVE-2026-75122same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected productTime to revision 4 days
2026-09-01same kind of change as the line aboveCVE-2026-75123same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected productTime to revision 4 days
2026-09-01same kind of change as the line aboveCVE-2026-75124same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected productTime to revision 4 days
2026-09-01same kind of change as the line aboveCVE-2026-75125same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected productTime to revision 4 days
2026-09-01same kind of change as the line aboveCVE-2026-75126same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected productTime to revision 4 days
2026-09-01same kind of change as the line aboveCVE-2026-77217same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected productTime to revision 4 days
2026-09-01same kind of change as the line aboveCVE-2026-77218same vendor as the line abovesame change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected productTime to revision 4 days
2026-09-015 commitsProduct added8 rows, one per record and productnot named as affected at publication, now names red hat enterprise linux 7 extended lifecycle support and 5 moreBranches and original-value intervals are stated on each row.not counted: 2 classesTime to revision 25 to 83 days
2026-09-01same kind of change as the line aboveCVE-2026-15816same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 7 extended lifecycle supportNot counted: Product relabelled. probable relabelling of red hat/red hat enterprise linux 7, not a newly affected productTime to revision 25 days
2026-09-01same kind of change as the line aboveCVE-2026-6893same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 7 extended lifecycle supportNot counted: Product relabelled. probable relabelling of red hat/red hat enterprise linux 7, not a newly affected productTime to revision 83 days
2026-09-01same kind of change as the line aboveCVE-2026-16615same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 10.0 extended update supportNot counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat enterprise linux 10; the record does not establish whether this newly names affected scope or refines the existing product listingTime to revision 41 days
2026-09-01same kind of change as the line aboveCVE-2026-18649same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 9.6 extended update supportNot counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat enterprise linux 9; the record does not establish whether this newly names affected scope or refines the existing product listingTime to revision 26 days
2026-09-01same kind of change as the line aboveCVE-2026-17523same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.8 telecommunications update serviceNot counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat enterprise linux 8; the record does not establish whether this newly names affected scope or refines the existing product listingTime to revision 36 days
2026-09-01same kind of change as the line aboveCVE-2026-17523same vendor as the line abovenot named as affected at publication, now names red hat enterprise linux 8.8 update services for sap solutionsNot counted: A variant beneath an already affected parent. support or installation label under already affected red hat/red hat enterprise linux 8; the record does not establish whether this newly names affected scope or refines the existing product listingTime to revision 36 days
2026-09-01same kind of change as the line aboveCVE-2026-54099same vendor as the line abovenot named as affected at publication, now names red hat openshift for windows containers 10.21Not counted: Product relabelled. probable relabelling of red hat/red hat openshift for windows containers, not a newly affected productTime to revision 71 days
2026-09-01same kind of change as the line aboveCVE-2026-54100same vendor as the line abovenot named as affected at publication, now names red hat openshift for windows containers 10.21Not counted: Product relabelled. probable relabelling of red hat/red hat openshift for windows containers, not a newly affected productTime to revision 71 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. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
4,561 record edits in the 52 weeks to 2026-09-07. Scroll for earlier dates.fewermore

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 →