Every change, newest first
Showing changes seen on 2026-09-01. Every day
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.
| 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. | Kind | 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. |
|---|---|---|---|---|---|
| Tue 1 Sep 2026· 84 changes | |||||
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 5 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 5 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 6 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 7 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 8 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 11 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 12 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 14 days |
| 2026-09-01 | Forensic triage now required | MicrosoftSharePoint | stated at publication not stated, now states Yesnot counted: The prior instruction already required triage | Time to revision 14 to 47 days | |
| 2026-09-01 | same kind of change as the line above | CVE-2026-55040 | same vendor as the line above | same 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 requirement | Time to revision 14 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-50522 | same vendor as the line above | same 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 requirement | Time to revision 41 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-58644 | same vendor as the line above | same 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 requirement | Time to revision 47 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 14 days |
| 2026-09-01 | Forensic triage now required | CVE-2025-62593 | Ray-ProjectRay 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 requirement | Time to revision 15 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 21 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 25 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 27 days |
| 2026-09-01 | Forensic triage now required | N-ableN-central | stated at publication not stated, now states Yesnot counted: The prior instruction already required triage | Time to revision 28 to 29 days | |
| 2026-09-01 | same kind of change as the line above | CVE-2026-18556 | same vendor as the line above | same 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 requirement | Time to revision 28 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-18577 | same vendor as the line above | same 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 requirement | Time to revision 29 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 28 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 36 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 41 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 42 days |
| 2026-09-01 | Forensic triage now required | LangflowLangflow | stated at publication not stated, now states Yesnot counted: The prior instruction already required triage | Time to revision 42 to 56 days | |
| 2026-09-01 | same kind of change as the line above | CVE-2026-0770 | same vendor as the line above | same 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 requirement | Time to revision 42 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-55255 | same vendor as the line above | same 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 requirement | Time to revision 56 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 42 days |
| 2026-09-01 | Forensic triage now required | FortinetFortiSandbox | stated at publication not stated, now states Yesnot counted: The prior instruction already required triage | Time to revision 47 days | |
| 2026-09-01 | same kind of change as the line above | CVE-2026-25089 | same vendor as the line above | same 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 requirement | Time to revision 47 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-39808 | same vendor as the line above | same 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 requirement | Time to revision 47 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 48 days |
| 2026-09-01 | Forensic triage now required | MicrosoftSharePoint Server | stated at publication not stated, now states Yesnot counted: The prior instruction already required triage | Time to revision 49 to 62 days | |
| 2026-09-01 | same kind of change as the line above | CVE-2026-56164 | same vendor as the line above | same 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 requirement | Time to revision 49 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-45659 | same vendor as the line above | same 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 requirement | Time to revision 62 days |
| 2026-09-01 | Forensic triage now required | SonicWallSMA1000 Appliances | stated at publication not stated, now states Yesnot counted: The prior instruction already required triage | Time to revision 49 days | |
| 2026-09-01 | same kind of change as the line above | CVE-2026-15409 | same vendor as the line above | same 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 requirement | Time to revision 49 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-15410 | same vendor as the line above | same 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 requirement | Time to revision 49 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 50 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 53 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 53 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 56 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 56 days |
| 2026-09-01 | Forensic triage now required | CVE-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 requirement | Time to revision 56 days |
| 2026-09-012 commits | Product added | Patchstack | not named as affected at publication, now names the gridBranches and original-value intervals are stated on each row.not counted: Product relabelled | Time to revision 14 to 222 days | |
| 2026-09-01 | same kind of change as the line above | CVE-2026-24370 | same vendor as the line above | same change as the line aboveNot counted: Product relabelled. probable relabelling of theme-one/the grid, not a newly affected product | Time to revision 160 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-24368 | same vendor as the line above | same change as the line aboveNot counted: Product relabelled. probable relabelling of theme-one/the grid, not a newly affected product | Time to revision 222 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-24369 | same vendor as the line above | same change as the line aboveNot counted: Product relabelled. probable relabelling of theme-one/the grid, not a newly affected product | Time to revision 160 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-28191 | same vendor as the line above | same change as the line aboveNot counted: Product relabelled. probable relabelling of theme-one inc./the grid, not a newly affected product | Time to revision 14 days |
| 2026-09-01 | Product added | not named as affected at publication, now names thunderbirdnot counted: Added entry does not state affected status | Time to revision 0 days | ||
| 2026-09-01 | same kind of change as the line above | CVE-2026-84118 | same vendor as the line above | same 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 exposure | Time to revision 0 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-84119 | same vendor as the line above | same 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 exposure | Time to revision 0 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-84120 | same vendor as the line above | same 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 exposure | Time to revision 0 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-84121 | same vendor as the line above | same 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 exposure | Time to revision 0 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-84122 | same vendor as the line above | same 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 exposure | Time to revision 0 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-84123 | same vendor as the line above | same 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 exposure | Time to revision 0 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-84124 | same vendor as the line above | same 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 exposure | Time to revision 0 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-84125 | same vendor as the line above | same 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 exposure | Time to revision 0 days |
| 18 more rows in this change are not listed here. Open all 26 rows → | |||||
| 2026-09-01 | Product added | VulnCheck | not named as affected at publication, now names planet gs-4210-16p2s v3not counted: Product relabelled | Time to revision 4 days | |
| 2026-09-01 | same kind of change as the line above | CVE-2026-75121 | same vendor as the line above | same change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product | Time to revision 4 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-75122 | same vendor as the line above | same change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product | Time to revision 4 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-75123 | same vendor as the line above | same change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product | Time to revision 4 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-75124 | same vendor as the line above | same change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product | Time to revision 4 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-75125 | same vendor as the line above | same change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product | Time to revision 4 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-75126 | same vendor as the line above | same change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product | Time to revision 4 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-77217 | same vendor as the line above | same change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product | Time to revision 4 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-77218 | same vendor as the line above | same change as the line aboveNot counted: Product relabelled. probable relabelling of planet technology corp./planet gs-4210-16p2s, not a newly affected product | Time to revision 4 days |
| 2026-09-015 commits | Product added | 8 rows, one per record and product | not 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 classes | Time to revision 25 to 83 days | |
| 2026-09-01 | same kind of change as the line above | CVE-2026-15816 | same vendor as the line above | not 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 product | Time to revision 25 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-6893 | same vendor as the line above | not 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 product | Time to revision 83 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-16615 | same vendor as the line above | not 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 listing | Time to revision 41 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-18649 | same vendor as the line above | not 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 listing | Time to revision 26 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-17523 | same vendor as the line above | not 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 listing | Time to revision 36 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-17523 | same vendor as the line above | not 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 listing | Time to revision 36 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-54099 | same vendor as the line above | not 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 product | Time to revision 71 days |
| 2026-09-01 | same kind of change as the line above | CVE-2026-54100 | same vendor as the line above | not 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 product | Time to revision 71 days |
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.
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 →