Every change, newest first
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 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 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 25 Aug 2026· 4 changes | |||||
| 2026-08-25 | Product added | CVE-2024-5647 | Wordfence | not named as affected at publication, now names shortcodes ultimate – content elementsNot counted: Product identity rewritten with unchanged scope. unchanged affected scope with a rewritten title of removed gn_themes/wp shortcodes plugin — shortcodes ultimate; a new product identity is not established | Time to revision 418 days |
| 2026-08-252 commits | Product added | not named as affected at publication, now names red hat build of apicurio registry 3.3.1Branches and original-value intervals are stated on each row.not counted: Added entry does not state affected status | Time to revision 61 days | ||
| 2026-08-25 | same kind of change as the line above | CVE-2026-12993 | 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 61 days |
| 2026-08-25 | same kind of change as the line above | CVE-2026-12975 | 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 61 days |
| 2026-08-25 | same kind of change as the line above | CVE-2026-12992 | 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 61 days |
| Mon 24 Aug 2026· 3 changes | |||||
| 2026-08-24 | Product added | CVE-2026-12912 | not named as affected at publication, now names red hat enterprise linux 9.2 update services for sap solutions and 1 morenot counted: A variant beneath an already affected parent | Time to revision 56 days | |
| 2026-08-24 | same kind of change as the line above | CVE-2026-12912 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 9.2 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 9; the record does not establish whether this newly names affected scope or refines the existing product listing | Time to revision 56 days |
| 2026-08-24 | same kind of change as the line above | CVE-2026-12912 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 9.4 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 9; the record does not establish whether this newly names affected scope or refines the existing product listing | Time to revision 56 days |
| 2026-08-24 | CVSS base score changed | CVE-2026-67340 | whole record VulnCheck | stated at publication 9.8, now states 8.6Assessments not comparable · base scoreCriticalHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Time to revision 23 days |
| Sat 22 Aug 2026· 1 change | |||||
| 2026-08-22 | Product added | CVE-2026-47895 | mitre | not named as affected at publication, now names strongswanNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Time to revision 1 days |
| Fri 21 Aug 2026· 6 changes | |||||
| 2026-08-21 | Fix version moved | CVE-2026-54981 | microsoftpython extension for visual studio code | stated at publication 1.132.1, now states 2026.3.1Release branch starts at 2020.Not counted: Version scheme changed. one side is on a calendar versioning scheme and the other is not — the two are not comparable in either direction | Time to revision 10 days |
| 2026-08-21 | Fix version moved | CVE-2026-63722 | icecodericecoder VulnCheck | stated at publication 8.1, now states 8.1Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 2 days |
| 2026-08-21 | Fix version moved | CVE-2026-20672 | applemacos | stated at publication 15.7.8, now states 26.3Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 15.7.8 still holds | Duration unknown |
| 2026-08-21 | Fix version moved | applemacos | stated at publication 15.7.8, now states 26.4Release branch starts at *.not counted: Another branch advanced | Duration unknown | |
| 2026-08-21 | same kind of change as the line above | CVE-2026-28896 | same vendor as the line above | same 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 15.7.8 still holds | Duration unknown |
| 2026-08-21 | same kind of change as the line above | CVE-2026-28926 | same vendor as the line above | same 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 15.7.8 still holds | Duration unknown |
| 2026-08-21 | Removed from CISA KEV | CVE-2026-69836 | MicrosoftEntra ID CISA KEV | Previously listed from 2026-08-21Not counted: Same-day catalog correction. entry stood 1.2 hours before being withdrawn — a same-day catalog correction, not a KEV listing anyone escalated | Time to revision 0 days |
| Thu 20 Aug 2026· 8 changes | |||||
| 2026-08-204 commits | Product added | CVE-2026-15816 | not named as affected at publication, now names red hat enterprise linux 9.6 extended update support and 3 moreBranches and original-value intervals are stated on each row.not counted: A variant beneath an already affected parent | Time to revision 13 to 14 days | |
| 2026-08-20 | 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 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 14 days |
| 2026-08-20 | 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 9.4 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 9; the record does not establish whether this newly names affected scope or refines the existing product listing | Time to revision 14 days |
| 2026-08-20 | 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 9.2 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 9; the record does not establish whether this newly names affected scope or refines the existing product listing | Time to revision 13 days |
| 2026-08-20 | 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 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 13 days |
| 2026-08-204 commits | Product added | CVE-2026-6893 | not named as affected at publication, now names red hat enterprise linux 9.6 extended update support and 3 moreBranches and original-value intervals are stated on each row.not counted: A variant beneath an already affected parent | Time to revision 71 days | |
| 2026-08-20 | 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 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 71 days |
| 2026-08-20 | 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 9.4 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 9; the record does not establish whether this newly names affected scope or refines the existing product listing | Time to revision 71 days |
| 2026-08-20 | 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 9.2 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 9; the record does not establish whether this newly names affected scope or refines the existing product listing | Time to revision 71 days |
| 2026-08-20 | 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 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 71 days |
| Wed 19 Aug 2026· 18 changes | |||||
| 2026-08-19 | Affected range extended | CVE-2026-17183 | grafanagrafana oss | stated at publication 13.1.1, now states 13.1.4Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 13.1.1 still holds | Duration unknown |
| 2026-08-19 | Affected range extended | CVE-2026-19501 | sureformssureforms certcc | stated at publication 2.1.1, now states 2.12.1Release branch starts at 0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bump | Time to revision 1 days |
| 2026-08-19 | Product added | not named as affected at publication, now names power systems firmwarenot counted: Product identity rewritten with unchanged scope | Time to revision 0 days | ||
| 2026-08-19 | same kind of change as the line above | CVE-2026-16828 | same vendor as the line above | same change as the line aboveNot counted: Product identity rewritten with unchanged scope. unchanged CPE identity of removed ibm/server firmware | Time to revision 0 days |
| 2026-08-19 | same kind of change as the line above | CVE-2026-16832 | same vendor as the line above | same change as the line aboveNot counted: Product identity rewritten with unchanged scope. unchanged CPE identity of removed ibm/server firmware | Time to revision 0 days |
| 2026-08-19 | same kind of change as the line above | CVE-2026-16930 | same vendor as the line above | same change as the line aboveNot counted: Product identity rewritten with unchanged scope. unchanged CPE identity of removed ibm/power firmware | Time to revision 0 days |
| 2026-08-19 | same kind of change as the line above | CVE-2026-16938 | same vendor as the line above | same change as the line aboveNot counted: Product identity rewritten with unchanged scope. unchanged CPE identity of removed ibm/server firmware | Time to revision 0 days |
| 2026-08-19 | same kind of change as the line above | CVE-2026-17093 | same vendor as the line above | same change as the line aboveNot counted: Product identity rewritten with unchanged scope. unchanged CPE identity of removed ibm/power firmware | Time to revision 0 days |
| 2026-08-19 | same kind of change as the line above | CVE-2026-17100 | same vendor as the line above | same change as the line aboveNot counted: Product identity rewritten with unchanged scope. unchanged CPE identity of removed ibm/power firmware | Time to revision 0 days |
| 2026-08-19 | same kind of change as the line above | CVE-2026-17429 | same vendor as the line above | same change as the line aboveNot counted: Product identity rewritten with unchanged scope. unchanged affected scope with a rewritten title of removed ibm/power firmware; a new product identity is not established | Time to revision 0 days |
| 2026-08-19 | same kind of change as the line above | CVE-2026-17494 | same vendor as the line above | same change as the line aboveNot counted: Product identity rewritten with unchanged scope. unchanged CPE identity of removed ibm/power firmware | Time to revision 0 days |
| 3 more rows in this change are not listed here. Open all 11 rows → | |||||
| 2026-08-19 | Product added | not named as affected at publication, now names red hat enterprise linux 8.4 extended update support long-life add-onnot counted: A variant beneath an already affected parent | Time to revision 41 days | ||
| 2026-08-19 | same kind of change as the line above | CVE-2026-59691 | same vendor as the line above | same change as the line aboveNot 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 41 days |
| 2026-08-19 | same kind of change as the line above | CVE-2026-59692 | same vendor as the line above | same change as the line aboveNot 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 41 days |
| 2026-08-19 | Product added | not named as affected at publication, now names red hat enterprise linux 9.2 update services for sap solutionsnot counted: A variant beneath an already affected parent | Time to revision 41 days | ||
| 2026-08-19 | same kind of change as the line above | CVE-2026-59691 | same vendor as the line above | same change as the line aboveNot 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 41 days |
| 2026-08-19 | same kind of change as the line above | CVE-2026-59692 | same vendor as the line above | same change as the line aboveNot 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 41 days |
| 2026-08-19 | Product added | CVE-2026-18963 | not named as affected at publication, now names red hat build of keycloak 26.4.15Not 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 | |
| Tue 18 Aug 2026· 64 changes | |||||
| 2026-08-182 commits | Product added | not named as affected at publication, now names red hat build of keycloak 26.6.6Branches and original-value intervals are stated on each row.not counted: Added entry does not state affected status | Time to revision 0 to 83 days | ||
| 2026-08-18 | same kind of change as the line above | CVE-2026-14613 | 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 46 days |
| 2026-08-18 | same kind of change as the line above | CVE-2026-17048 | 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 25 days |
| 2026-08-18 | same kind of change as the line above | CVE-2026-9796 | 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 83 days |
| 2026-08-18 | same kind of change as the line above | CVE-2026-18963 | 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-08-18 | Product added | CVE-2026-15571 | not named as affected at publication, now names red hat build of keycloak 26.6Not counted: Already named at publication. already named at publication inside red hat/red hat build of keycloak 26.6.6 — the record spelled this product out all along | Time to revision 0 days | |
| 2026-08-18 | 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-08-18 | same kind of change as the line above | CVE-2026-74934 | 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-08-18 | same kind of change as the line above | CVE-2026-74935 | 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-08-18 | same kind of change as the line above | CVE-2026-74936 | 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-08-18 | same kind of change as the line above | CVE-2026-74937 | 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-08-18 | same kind of change as the line above | CVE-2026-74938 | 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-08-18 | same kind of change as the line above | CVE-2026-74939 | 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-08-18 | same kind of change as the line above | CVE-2026-74940 | 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-08-18 | same kind of change as the line above | CVE-2026-74941 | 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 |
| 47 more rows in this change are not listed here. Open all 55 rows → | |||||
| 2026-08-18 | Product added | CVE-2026-47632 | not named as affected at publication, now names azure connected machine agentNot counted: Product identity rewritten with unchanged scope. unchanged affected scope with a rewritten title of removed microsoft/azure monitor agent metrics extension; a new product identity is not established | Time to revision 35 days | |
| 2026-08-182 commits | Product added | CVE-2026-5674 | not named as affected at publication, now names red hat enterprise linux 9.4 update services for sap solutions and 1 moreBranches and original-value intervals are stated on each row.not counted: A variant beneath an already affected parent | Time to revision 33 days | |
| 2026-08-18 | same kind of change as the line above | CVE-2026-5674 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 9.4 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 9; the record does not establish whether this newly names affected scope or refines the existing product listing | Time to revision 33 days |
| 2026-08-18 | same kind of change as the line above | CVE-2026-5674 | 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 33 days |
| 2026-08-18 | CVSS base score changed | CVE-2026-75936 | whole record AMZN | stated at publication 9.9, now states 8.7Assessments not comparable · base scoreCriticalHighNot counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Time to revision 0 days |
| Mon 17 Aug 2026· 20 changes | |||||
| 2026-08-177 commits | Product added | 18 rows, one per record and product | not named as affected at publication, now names red hat enterprise linux 8.8 telecommunications update service and 7 moreBranches and original-value intervals are stated on each row.not counted: A variant beneath an already affected parent | Time to revision 17 to 685 days | |
| 2026-08-17 | same kind of change as the line above | CVE-2026-11788 | 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 69 days |
| 2026-08-17 | same kind of change as the line above | CVE-2026-11788 | 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 69 days |
| 2026-08-17 | same kind of change as the line above | CVE-2026-15722 | 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 18 days |
| 2026-08-17 | same kind of change as the line above | CVE-2026-15722 | 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 18 days |
| 2026-08-17 | same kind of change as the line above | CVE-2026-11788 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 8.6 extended update support long-life add-onNot 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 69 days |
| 2026-08-17 | same kind of change as the line above | CVE-2026-15722 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 8.6 extended update support long-life add-onNot 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 17 days |
| 2026-08-17 | same kind of change as the line above | CVE-2026-11788 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 8.4 extended update support long-life add-onNot 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 69 days |
| 2026-08-17 | same kind of change as the line above | CVE-2026-15722 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 8.4 extended update support long-life add-onNot 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 17 days |
| 10 more rows in this change are not listed here. Open all 18 rows → | |||||
| 2026-08-17 | CVSS base score changed | CVE-2025-7639 | whole record icscert | stated at publication 10.0, now states 7.1Assessments not comparable · base scoreCriticalHighOriginal value first replaced 2026-08-14; this value first seen 2026-08-17.Not counted: CVSS assessments are not comparable. the displayed maximum pair is not established on the same CVSS v3/v4 version, CNA and assessment context; changed scenarios, competing metrics and v2 bands are not comparable | Time to revision 0 days |
| 2026-08-17 | KEV due date moved | CVE-2025-62593 | Ray-ProjectRay CISA KEV | stated at publication 2026-08-21, now states 2026-08-20Not counted: Entry date corrected, deadline followed. dateAdded moved 2026-08-18 -> 2026-08-17 in the same commit and the due date moved by the same number of days — the entry date was corrected, the obligation did not move | Time to revision 0 days |
| Sun 16 Aug 2026· 6 changes | |||||
| 2026-08-16 | Fix version moved | CVE-2026-42976 | microsoft3 products | stated at publication 10.0.17763.8880, now states 10.0.17763.9121Release branch starts at 10.0.17763.0.Original value first replaced 2026-08-12; this value first seen 2026-08-16.not counted: Build number corrected to the one that shipped | Time to revision 1 days |
| 2026-08-16 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Original value first replaced 2026-08-12; this value first seen 2026-08-16.Not counted: Build number corrected to the one that shipped. only the build revision moved, 5.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-16 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Original value first replaced 2026-08-12; this value first seen 2026-08-16.Not counted: Build number corrected to the one that shipped. only the build revision moved, 5.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-16 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Original value first replaced 2026-08-12; this value first seen 2026-08-16.Not counted: Build number corrected to the one that shipped. only the build revision moved, 5.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-16 | Fix version moved | CVE-2026-49179 | microsoft3 products | stated at publication 10.0.17763.9115, now states 10.0.17763.9121Release branch starts at 10.0.17763.0.not counted: Build number corrected to the one that shipped | Time to revision 5 days |
| 2026-08-16 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 5.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 5 days |
| 2026-08-16 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 5.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 5 days |
| 2026-08-16 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.17763.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 5.1 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 5 days |
| Fri 14 Aug 2026· 1 change | |||||
| 2026-08-14 | Product added | CVE-2026-3885 | Wordfence | not named as affected at publication, now names shortcodes ultimate – content elementsNot counted: Product identity rewritten with unchanged scope. unchanged affected scope with a rewritten title of removed gn_themes/wp shortcodes plugin — shortcodes ultimate; a new product identity is not established | Time to revision 121 days |
| Thu 13 Aug 2026· 18 changes | |||||
| 2026-08-13 | Affected range extended | unknownsalon booking system WPScan | stated at publication 10.30.33, now states 10.30.34Release branch starts at 0.not counted: Same claim, other operator | Time to revision 3 days | |
| 2026-08-13 | same kind of change as the line above | CVE-2026-17021 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 3 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-17022 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 3 days |
| 2026-08-133 commits | Product added | 16 rows, one per record and product | not named as affected at publication, now names red hat enterprise linux 8.4 extended update support long-life add-on and 6 moreBranches and original-value intervals are stated on each row.not counted: A variant beneath an already affected parent | Time to revision 35 to 45 days | |
| 2026-08-13 | same kind of change as the line above | CVE-2026-12912 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 8.4 extended update support long-life add-onNot 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 45 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-12912 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 8.6 extended update support long-life add-onNot 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 45 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-59691 | 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 36 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-59691 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 8.6 extended update support long-life add-onNot 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-08-13 | same kind of change as the line above | CVE-2026-59691 | 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-08-13 | same kind of change as the line above | CVE-2026-59691 | 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-08-13 | same kind of change as the line above | CVE-2026-59692 | 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 36 days |
| 2026-08-13 | same kind of change as the line above | CVE-2026-59692 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 8.6 extended update support long-life add-onNot 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 |
| 8 more rows in this change are not listed here. Open all 16 rows → | |||||
| Wed 12 Aug 2026· 25 changes | |||||
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoft3 products | stated at publication 10.0.14393.9234, now states 10.0.14393.9418Release branch starts at 10.0.14393.0.not counted: Build number corrected to the one that shipped | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.14393.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.14393.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.14393.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoftwindows 10 version 21h2 | stated at publication 10.0.19044.7417, now states 10.0.19044.7663Release branch starts at 10.0.19044.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoftwindows 10 version 22h2 | stated at publication 10.0.19045.7417, now states 10.0.19045.7663Release branch starts at 10.0.19045.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoftwindows 11 version 26h1 | stated at publication 10.0.28000.2269, now states 10.0.28000.2704Release branch starts at 10.0.28000.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoft2 products | stated at publication 6.2.9200.26132, now states 6.2.9200.26280Release branch starts at 6.2.9200.0.not counted: Build number corrected to the one that shipped | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.9200.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.9200.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoft2 products | stated at publication 6.3.9600.23228, now states 6.3.9600.23338Release branch starts at 6.3.9600.0.not counted: Build number corrected to the one that shipped | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.3.9600.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.3.9600.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Fix version moved | CVE-2026-42976 | microsoft2 products | stated at publication 10.0.26100.32995, now states 10.0.26100.33296Release branch starts at 10.0.26100.0.not counted: Build number corrected to the one that shipped | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-42976 | same vendor as the line above | same change as the line aboveRelease branch starts at 10.0.26100.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 1.0 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 1 days |
| 2026-08-12 | Product added | not named as affected at publication, now names red hat jboss enterprise application platform 7.4.25not counted: Added entry does not state affected status | Time to revision 1 days | ||
| 2026-08-12 | same kind of change as the line above | CVE-2026-15554 | 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 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-15555 | 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 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-15556 | 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 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-15560 | 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 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-15561 | 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 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-15562 | 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 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-15563 | 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 1 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-15565 | 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 1 days |
| 1 more row in this change is not listed here. Open all 9 rows → | |||||
| 2026-08-123 commits | Product added | CVE-2026-56208 | not named as affected at publication, now names red hat enterprise linux 9.6 extended update support and 3 moreBranches and original-value intervals are stated on each row.not counted: A variant beneath an already affected parent | Time to revision 54 days | |
| 2026-08-12 | same kind of change as the line above | CVE-2026-56208 | 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 54 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-56208 | 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 54 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-56208 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 9.4 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 9; the record does not establish whether this newly names affected scope or refines the existing product listing | Time to revision 54 days |
| 2026-08-12 | same kind of change as the line above | CVE-2026-56208 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 9.2 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 9; the record does not establish whether this newly names affected scope or refines the existing product listing | Time to revision 54 days |
| Tue 11 Aug 2026· 6 changes | |||||
| 2026-08-11 | Fix version moved | CVE-2026-49179 | microsoft2 products | stated at publication 6.2.9200.26279, now states 6.2.9200.26280Release branch starts at 6.2.9200.0.not counted: Build number corrected to the one that shipped | Time to revision 0 days |
| 2026-08-11 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.9200.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 0.2 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 0 days |
| 2026-08-11 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.2.9200.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 0.2 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 0 days |
| 2026-08-11 | Fix version moved | CVE-2026-49179 | microsoft2 products | stated at publication 6.3.9600.23337, now states 6.3.9600.23338Release branch starts at 6.3.9600.0.not counted: Build number corrected to the one that shipped | Time to revision 0 days |
| 2026-08-11 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.3.9600.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 0.2 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 0 days |
| 2026-08-11 | same kind of change as the line above | CVE-2026-49179 | same vendor as the line above | same change as the line aboveRelease branch starts at 6.3.9600.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 0.2 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that moved | Time to revision 0 days |
| 2026-08-11 | Affected range extended | CVE-2026-13410 | garudancer::plugin::auth::google CPANSec | stated at publication 0.07, now states 0.08Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 25 days |
| 2026-08-11 | Product added | CVE-2026-10579 | not named as affected at publication, now names red hat jboss enterprise application platform 7.4.25Not 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 1 days | |
| Mon 10 Aug 2026· 115 changes | |||||
| 2026-08-10 | Fix version moved | CVE-2026-18933 | wp-downloadmanagerwp-downloadmanager TuranSec | stated at publication 1.69, now states 1.69Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 5 days |
| 2026-08-10 | Fix version moved | CVE-2026-31844 | koha communitykoha TuranSec | stated at publication 24.11.12, now states 24.11.12Release branch starts at 24.11.0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 152 days |
| 2026-08-10 | Fix version moved | CVE-2026-31844 | koha communitykoha TuranSec | stated at publication 25.05.07, now states 25.05.07Release branch starts at 25.05.0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 152 days |
| 2026-08-10 | Fix version moved | CVE-2026-31844 | koha communitykoha TuranSec | stated at publication 25.11.01, now states 25.11.01Release branch starts at 25.11.0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 152 days |
| 2026-08-10 | Fix version moved | CVE-2026-3843 | nefteprodukttekhnika llcbuk ts-g gas station automation system TuranSec | stated at publication 2.10.2, now states 2.10.2Release branch starts at 2.9.1.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 153 days |
| 2026-08-10 | Fix version moved | CVE-2026-54414 | error311filerise TuranSec | stated at publication 3.16.0, now states 3.16.0Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 52 days |
| 2026-08-10 | Fix version moved | CVE-2026-54415 | azuriomazuriom cms TuranSec | stated at publication 1.2.11, now states 1.2.11Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 54 days |
| 2026-08-10 | Fix version moved | CVE-2026-6428 | koha communitykoha TuranSec | stated at publication 22.11.38, now states 22.11.38Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 58 days |
| 2026-08-10 | Fix version moved | CVE-2026-6428 | koha communitykoha TuranSec | stated at publication 24.11.16, now states 24.11.16Release branch starts at 24.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 58 days |
| 2026-08-10 | Fix version moved | CVE-2026-6428 | koha communitykoha TuranSec | stated at publication 25.05.11, now states 25.05.11Release branch starts at 25.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 58 days |
| 2026-08-10 | Fix version moved | CVE-2026-6428 | koha communitykoha TuranSec | stated at publication 25.11.05, now states 25.11.05Release branch starts at 25.11.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 58 days |
| 2026-08-10 | Fix version moved | koha communitykoha TuranSec | stated at publication 26.05.01, now states 26.05.01Release branch starts at 26.05.00.not counted: Same claim, other operator | Time to revision 6 to 58 days | |
| 2026-08-10 | same kind of change as the line above | CVE-2026-6428 | same vendor as the line above | same change as the line aboveRelease branch starts at 26.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 58 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70369 | same vendor as the line above | same change as the line aboveRelease branch starts at 26.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70370 | same vendor as the line above | same change as the line aboveRelease branch starts at 26.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70371 | same vendor as the line above | same change as the line aboveRelease branch starts at 26.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70372 | same vendor as the line above | same change as the line aboveRelease branch starts at 26.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70373 | same vendor as the line above | same change as the line aboveRelease branch starts at 26.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | Fix version moved | koha communitykoha TuranSec | stated at publication 24.11.17, now states 24.11.17Release branch starts at 0.not counted: Same claim, other operator | Time to revision 6 days | |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70369 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70370 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70371 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70372 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70373 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | Fix version moved | koha communitykoha TuranSec | stated at publication 25.05.12, now states 25.05.12Release branch starts at 25.05.00.not counted: Same claim, other operator | Time to revision 6 days | |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70369 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70370 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70371 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70372 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70373 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.05.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | Fix version moved | koha communitykoha TuranSec | stated at publication 25.11.06, now states 25.11.06Release branch starts at 25.11.00.not counted: Same claim, other operator | Time to revision 6 days | |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70369 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.11.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70370 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.11.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70371 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.11.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70372 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.11.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-70373 | same vendor as the line above | same change as the line aboveRelease branch starts at 25.11.00.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 6 days |
| 2026-08-10 | Fix version moved | CVE-2026-70376 | pluck-cmspluck cms TuranSec | stated at publication 4.7.21, now states 4.7.21Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 5 days |
| 2026-08-10 | Fix version moved | CVE-2026-71232 | magicblackmaccms10 TuranSec | stated at publication 10, now states 10Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 5 days |
| 2026-08-10 | Fix version moved | CVE-2026-72564 | fosrlpangolin TuranSec | stated at publication 1.20.0, now states 1.20.0Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2026-08-10 | Fix version moved | cube-rootdirectory-serve TuranSec | stated at publication 1.3.7, now states 1.3.7Release branch starts at 0.not counted: Same claim, other operator | Time to revision 0 days | |
| 2026-08-10 | same kind of change as the line above | CVE-2026-72569 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-72570 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2026-08-10 | Fix version moved | CVE-2026-72574 | picocmspico TuranSec | stated at publication 2.1.4, now states 2.1.4Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2026-08-10 | Fix version moved | CVE-2026-72575 | daptindaptin TuranSec | stated at publication v0.12.34, now states v0.12.34Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2026-08-10 | Fix version moved | CVE-2026-72577 | nasafprime-gds TuranSec | stated at publication 3.4.3, now states 3.4.3Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2026-08-10 | Fix version moved | fastschemafastschema TuranSec | stated at publication 0.15.1, now states 0.15.1Release branch starts at 0.not counted: Same claim, other operator | Time to revision 0 days | |
| 2026-08-10 | same kind of change as the line above | CVE-2026-72582 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-72583 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-72584 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2026-08-10 | Fix version moved | CVE-2026-72586 | frangoteamfuxa TuranSec | stated at publication 1.3.3, now states 1.3.3Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2026-08-10 | Fix version moved | CVE-2026-72587 | corebunchinstatic TuranSec | stated at publication 0.0.14, now states 0.0.14Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2026-08-10 | Fix version moved | CVE-2026-72588 | bluewave-labscheckmate TuranSec | stated at publication 2.1.0, now states 2.1.0Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2026-08-10 | Fix version moved | alseambushercrontab-ui TuranSec | stated at publication 0.4.2, now states 0.4.2Release branch starts at 0.not counted: Same claim, other operator | Time to revision 0 days | |
| 2026-08-10 | same kind of change as the line above | CVE-2026-72589 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-72590 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2026-08-10 | Fix version moved | CVE-2026-72591 | gabehfkoito TuranSec | stated at publication 0.3.2, now states 0.3.2Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2026-08-10 | Fix version moved | dullduskphpfm TuranSec | stated at publication 1.8.0, now states 1.8.0Release branch starts at 0.not counted: Same claim, other operator | Time to revision 0 days | |
| 2026-08-10 | same kind of change as the line above | CVE-2026-72592 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-72593 | same vendor as the line above | same change as the line aboveRelease branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2026-08-10 | Fix version moved | CVE-2026-72594 | lobehublobe-chat TuranSec | stated at publication 2.2.13, now states 2.2.13Release branch starts at 0.Not counted: Same claim, other operator. `lt` rewritten as `lte` on the same or the next release — the same claim under the other operator | Time to revision 0 days |
| 2026-08-10 | Affected range extended | CVE-2026-1498 | watchguardfireware os | stated at publication 12.11.6, now states 12.11.7Release branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 192 days |
| 2026-08-10 | Affected range extended | CVE-2026-1498 | watchguardfireware os | stated at publication 2026.0, now states 2026.1Release branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 192 days |
| 2026-08-10 | Affected range extended | CVE-2025-14733 | watchguardfireware os | stated at publication 12.11.5, now states 12.11.6Release branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 235 days |
| 2026-08-10 | Affected range extended | CVE-2025-14733 | watchguardfireware os | stated at publication 2025.1.3, now states 2025.1.4Release branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 235 days |
| 2026-08-105 commits | Affected range extended | watchguardfireware os | stated at publication 12.12, now states 12.12.13 release branches. Branches and original-value intervals are stated on each row.not counted: Same claim, other operator | Time to revision 39 days | |
| 2026-08-10 | same kind of change as the line above | CVE-2026-13050 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 39 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-13053 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 39 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-13054 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 39 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-13084 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 39 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-8247 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 39 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-13722 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 39 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-13373 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.4.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 39 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-13374 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.4.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 39 days |
| 6 more rows in this change are not listed here. Open all 14 rows → | |||||
| 2026-08-105 commits | Affected range extended | watchguardfireware os | stated at publication 2026.2, now states 2026.2.1Branches and original-value intervals are stated on each row.not counted: Same claim, other operator | Time to revision 39 days | |
| 2026-08-10 | same kind of change as the line above | CVE-2026-13050 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 39 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-13053 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 39 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-13054 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 39 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-13084 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 39 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-13728 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 39 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-8247 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 39 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-13368 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 39 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-13722 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 39 days |
| 7 more rows in this change are not listed here. Open all 15 rows → | |||||
| 2026-08-10 | Affected range extended | watchguardfireware os | stated at publication 12.11.7, now states 12.11.82 release branches. Branches and original-value intervals are stated on each row.not counted: Same claim, other operator | Time to revision 160 days | |
| 2026-08-10 | same kind of change as the line above | CVE-2026-3343 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.7.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 160 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-3344 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 160 days |
| 2026-08-10 | Affected range extended | watchguardfireware os | stated at publication 2026.1.1, now states 2026.1.2Release branch starts at 2025.1.not counted: Same claim, other operator | Time to revision 160 days | |
| 2026-08-10 | same kind of change as the line above | CVE-2026-3343 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 160 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-3344 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 160 days |
| 2026-08-10 | Affected range extended | watchguardfireware os | stated at publication 12.11.8, now states 12.123 release branches. Branches and original-value intervals are stated on each row.not counted: Same claim, other operator | Time to revision 131 to 133 days | |
| 2026-08-10 | same kind of change as the line above | CVE-2026-3987 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.6.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 131 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-4266 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 133 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-4315 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 133 days |
| 2026-08-10 | Affected range extended | watchguardfireware os | stated at publication 2026.1.2, now states 2026.2Release branch starts at 2025.1.not counted: Same claim, other operator | Time to revision 131 to 133 days | |
| 2026-08-10 | same kind of change as the line above | CVE-2026-3987 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 131 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-4266 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 133 days |
| 2026-08-10 | same kind of change as the line above | CVE-2026-4315 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 133 days |
| 2026-08-10 | Affected range extended | watchguardfireware os | stated at publication 12.11.4, now states 12.11.52 release branches. Branches and original-value intervals are stated on each row.not counted: Same claim, other operator | Time to revision 249 days | |
| 2026-08-10 | same kind of change as the line above | CVE-2025-12195 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 249 days |
| 2026-08-10 | same kind of change as the line above | CVE-2025-12196 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 249 days |
| 2026-08-10 | same kind of change as the line above | CVE-2025-13939 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 249 days |
| 2026-08-10 | same kind of change as the line above | CVE-2025-13940 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.8.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 249 days |
| 2026-08-10 | same kind of change as the line above | CVE-2025-1545 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 249 days |
| 2026-08-102 commits | Affected range extended | watchguardfireware os | stated at publication 2025.1.2, now states 2025.1.3Branches and original-value intervals are stated on each row.not counted: Same claim, other operator | Time to revision 249 days | |
| 2026-08-10 | same kind of change as the line above | CVE-2025-12195 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 249 days |
| 2026-08-10 | same kind of change as the line above | CVE-2025-13937 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 249 days |
| 2026-08-10 | same kind of change as the line above | CVE-2025-13939 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 249 days |
| 2026-08-10 | same kind of change as the line above | CVE-2025-13940 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 249 days |
| 2026-08-10 | same kind of change as the line above | CVE-2025-1545 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 249 days |
| 2026-08-10 | same kind of change as the line above | CVE-2025-12026 | same vendor as the line above | same change as the line aboveRelease branch starts at 2025.1.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 249 days |
| 2026-08-10 | Affected range extended | CVE-2025-1549 | watchguardmobile vpn with ssl client | stated at publication 12.10, now states 12.11.3Release branch starts at 0.Original value first replaced 2025-12-04; this value first seen 2026-08-10.Not counted: Description already named the later value. the record's own description at publication already named 12.11.3 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 36 days |
| 2026-08-10 | Affected range extended | CVE-2025-6999 | watchguardfireware os | stated at publication 12.11.2, now states 12.11.3Release branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 329 days |
| 2026-08-10 | Affected range extended | CVE-2025-9242 | watchguardfireware os | stated at publication 12.11.3, now states 12.11.4Release branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 327 days |
| 2026-08-10 | Affected range extended | CVE-2026-11974 | unknownwp-media-folder-addon WPScan | stated at publication 4.1.6, now states 4.1.7Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 12 days |
| 2026-08-10 | Affected range extended | CVE-2026-13692 | unknownpayu commercepro plugin WPScan | stated at publication 3.8.9, now states 3.9.0Release branch starts at 0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 12 days |
| 2026-08-10 | Product added | CVE-2023-2008 | not named as affected at publication, now names red hat enterprise linux 6 and 2 morenot counted: Added entry does not state affected status | Time to revision 1,215 days | |
| 2026-08-10 | same kind of change as the line above | CVE-2023-2008 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 6Not 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 1,215 days |
| 2026-08-10 | same kind of change as the line above | CVE-2023-2008 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 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 exposure | Time to revision 1,215 days |
| 2026-08-10 | same kind of change as the line above | CVE-2023-2008 | same vendor as the line above | not named as affected at publication, now names red hat enterprise linux 8Not 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 1,215 days |
| 2026-08-10 | CVSS base score changed | CVE-2024-21489 | whole record snyk | stated at publication 8.2, now states 8.8Assessments not comparable · base scoreHighHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removed | Time to revision 678 days |
| Sat 8 Aug 2026· 4 changes | |||||
| 2026-08-08 | Affected range extended | CVE-2025-1910 | watchguardmobile vpn with ssl client | stated at publication 12.11.2, now states 12.11.3Release branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2026-08-08 | Affected range extended | watchguardfireware os | stated at publication 12.11.1, now states 12.11.2Release branch starts at 12.0.not counted: Same claim, other operator | Time to revision 448 days | |
| 2026-08-08 | same kind of change as the line above | CVE-2025-4804 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 448 days |
| 2026-08-08 | same kind of change as the line above | CVE-2025-4805 | same vendor as the line above | same change as the line aboveRelease branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 448 days |
| 2026-08-08 | Affected range extended | CVE-2025-6946 | watchguardfireware os | stated at publication 12.11.2, now states 12.11.3Release branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 246 days |
| Fri 7 Aug 2026· 3 changes | |||||
| 2026-08-07 | Affected range extended | CVE-2025-6947 | watchguardfireware os | stated at publication 12.11.2, now states 12.11.3Release branch starts at 12.0.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operator | Time to revision 326 days |
| 2026-08-07 | Affected range extended | CVE-2024-5974 | watchguardfireware os | stated at publication 12.10.3, now states 12.10.4Release branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matched | Duration unknown |
| 2026-08-07 | Product added | CVE-2025-58375 | GitHub_M | not named as affected at publication, now names frappeNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' from | Time to revision 0 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.
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 →