Affected range extended
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. | Record, Which record was edited, by its CVE id, or how many records one collapsed line stands on. | Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry. | What changed | Days to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong. |
|---|---|---|---|---|
| Wed 2 Sep 2026· 1 change | ||||
| 2026-09-02 | CVE-2026-82641 | keploykeploy VulnCheck | stated at publication 3.6.25, now states 3.6.26Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 3.6.25 still holds | Duration unknown |
| Wed 26 Aug 2026· 1 change | ||||
| 2026-08-26 | CVE-2026-5917 | libgit2libgit2 VulnCheck | stated at publication 1.9.0, now states 1.9.7Release 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 |
| Tue 25 Aug 2026· 1 change | ||||
| 2026-08-25 | CVE-2026-73325 | fujitsu researchonecompression VulnCheck | stated at publication 1.2.0, now states 1.2.1Release 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 |
| Mon 3 Aug 2026· 1 change | ||||
| 2026-08-03 | CVE-2026-65321 | laughingman7743pyathena VulnCheck | stated at publication 3.35.3, now states 3.35.4Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 3.35.3 still holds | Duration unknown |
| Mon 27 Jul 2026· 1 change | ||||
| 2026-07-27 | CVE-2026-63094 | signozsignoz VulnCheck | stated at publication 0.133.0, now states 0.134.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 10 days |
| Fri 24 Jul 2026· 1 change | ||||
| 2026-07-24 | CVE-2026-29009 | u-bootu-boot VulnCheck | stated at publication 2026.04-rc3, now states 2026.07-rc2Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch to | Time to revision 16 days |
| Tue 23 Jun 2026· 1 change | ||||
| 2026-06-23 | CVE-2026-54390 | jtl softwarejtl shop VulnCheck | stated at publication 5.3.x, now states 5.4.0Release branch starts at 5.2.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 5 days |
| Wed 10 Jun 2026· 2 changes | ||||
| 2026-06-10 | limesurveylimesurvey VulnCheck | stated at publication 7.0, now states 7.0.1Release branch starts at *.not counted: Another branch advanced | Duration unknown | |
| 2026-06-10 | CVE-2026-50635 | 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 7.0 still holds | Duration unknown |
| 2026-06-10 | CVE-2026-50636 | 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 7.0 still holds | Duration unknown |
| Tue 26 May 2026· 2 changes | ||||
| 2026-05-26 | langgeniusdify VulnCheck | stated at publication 1.14.1, now states 1.14.2Release branch starts at 0.not counted: Same claim, other operator | Time to revision 8 days | |
| 2026-05-26 | CVE-2026-41947 | 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 8 days |
| 2026-05-26 | CVE-2026-41949 | 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 8 days |
| Mon 25 May 2026· 7 changes | ||||
| 2026-05-25 | smoothwallexpress VulnCheck | stated at publication 3.1 Update 13, now states 3.1 Update 13Release branch starts at 0.not counted: Same claim, other operator | Time to revision 56 days | |
| 2026-05-25 | CVE-2026-26352 | 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 56 days |
| 2026-05-25 | CVE-2026-27508 | 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 56 days |
| 2026-05-25 | CVE-2026-27510 | unitreeroboticsunitree go2 VulnCheck | stated at publication 1.1.9, now states 1.1.11Release branch starts at 1.1.7.Not counted: Description already named the later value. the record's own description at publication already named 1.1.11 — the structured field was corrected to the value the prose stated, not a fix that moved | Time to revision 88 days |
| 2026-05-25 | CVE-2026-28481 | openclawopenclaw VulnCheck | stated at publication 2026.1.30, now states 2026.2.1Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 2026.1.30 still holds | Duration unknown |
| 2026-05-25 | CVE-2026-28532 | frroutingfrr VulnCheck | stated at publication 10.5.3, now states 10.5.3Release 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-05-25 | CVE-2026-34963 | bareboxbarebox VulnCheck | stated at publication 2026.04.0, now states 2026.04.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 14 days |
| 2026-05-25 | CVE-2026-40032 | tclahruac VulnCheck | stated at publication 3.2.0, now states 3.3.0-rc1Release 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 47 days |
| Wed 13 May 2026· 2 changes | ||||
| 2026-05-13 | scott patersoneasy-paypal-events-tickets VulnCheck | stated at publication 1.3, now states 1.4.0Release branch starts at 0.not counted: Same claim, other operator | Time to revision 9 days | |
| 2026-05-13 | CVE-2026-32834 | 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 9 days |
| 2026-05-13 | CVE-2026-41471 | 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 9 days |
| Tue 21 Apr 2026· 1 change | ||||
| 2026-04-21 | CVE-2026-40525 | volcengineopenviking VulnCheck | stated at publication 0.3.8, now states 0.3.9Release 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 4 days |
| Thu 15 Jan 2026· 1 change | ||||
| 2026-01-15 | CVE-2026-22200 | enhancesoftosticket VulnCheck | stated at publication 1.18.2, now states 1.18.3Release 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 |
| Mon 15 Dec 2025· 3 changes | ||||
| 2025-12-15 | netsupport softwaremanager VulnCheck | stated at publication 14.12.0.304, now states 14.12.0001Release branch starts at 0.not counted: Same claim, other operator | Time to revision 0 days | |
| 2025-12-15 | CVE-2025-34179 | 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 0 days |
| 2025-12-15 | CVE-2025-34180 | 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 0 days |
| 2025-12-15 | CVE-2025-34181 | 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 0 days |
| Tue 4 Nov 2025· 1 change | ||||
| 2025-11-04 | CVE-2025-3248 | langflow-ailangflow VulnCheck | stated at publication 1.2.0, now states 1.3.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 211 days |
This kind is counted once per record and per product, so one record that added four products counts four times and the number of records behind these changes is smaller. 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 →