Skip to content

Every change, newest first

What a record said when it was published, what it says now, and the commit that changed it.

26 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
Counted changes published by qnap, newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin.KindRecord, 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 changedDays to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong.
Tue 30 Jun 2026· 4 changes
2026-06-30CVSS base score changed
whole record
qnap
stated at publication 5.1, now states 1.2CVSS v4.0 · base scoreMediumLowTime to revision 20 days
2026-06-30same kind of change as the line aboveCVE-2026-24716same vendor as the line abovesame change as the line aboveTime to revision 20 days
2026-06-30same kind of change as the line aboveCVE-2026-24717same vendor as the line abovesame change as the line aboveTime to revision 20 days
2026-06-30CVSS base score changedCVE-2026-24719
whole record
qnap
stated at publication 8.6, now states 6.1CVSS v4.0 · base scoreHighMediumTime to revision 20 days
2026-06-30CVSS base score changedCVE-2026-41539
whole record
qnap
stated at publication 8.7, now states 6.3CVSS v4.0 · base scoreHighMediumTime to revision 21 days
Wed 17 Jun 2026· 11 changes
2026-06-17Fix version movedqnapstated at publication 2.9.0, now states 2.9.1Release branch starts at 2.9.0.Time to revision 7 to 8 days
2026-06-17same kind of change as the line aboveCVE-2026-26236same vendor as the line abovesame change as the line aboveRelease branch starts at 2.9.0.Time to revision 8 days
2026-06-17same kind of change as the line aboveCVE-2026-26237same vendor as the line abovesame change as the line aboveRelease branch starts at 2.9.0.Time to revision 7 days
2026-06-17CVSS base score changedCVE-2025-62851
whole record
qnap
stated at publication 6.9, now states 4.6CVSS v4.0 · base scoreMediumMediumTime to revision 7 days
2026-06-17CVSS base score changed
whole record
qnap
stated at publication 5.3, now states 1.3CVSS v4.0 · base scoreMediumLowTime to revision 7 days
2026-06-17same kind of change as the line aboveCVE-2026-22899same vendor as the line abovesame change as the line aboveTime to revision 7 days
2026-06-17same kind of change as the line aboveCVE-2026-24720same vendor as the line abovesame change as the line aboveTime to revision 7 days
2026-06-17same kind of change as the line aboveCVE-2026-26240same vendor as the line abovesame change as the line aboveTime to revision 7 days
2026-06-17same kind of change as the line aboveCVE-2026-26241same vendor as the line abovesame change as the line aboveTime to revision 7 days
2026-06-17CVSS base score changedCVE-2026-24724
whole record
qnap
stated at publication 8.6, now states 6.2CVSS v4.0 · base scoreHighMediumTime to revision 7 days
2026-06-17CVSS base score changed
whole record
qnap
stated at publication 8.7, now states 6.6CVSS v4.0 · base scoreHighMediumTime to revision 7 to 8 days
2026-06-17same kind of change as the line aboveCVE-2026-26236same vendor as the line abovesame change as the line aboveTime to revision 8 days
2026-06-17same kind of change as the line aboveCVE-2026-26237same vendor as the line abovesame change as the line aboveTime to revision 7 days
2026-06-17CVSS base score changedCVE-2026-26239
whole record
qnap
stated at publication 8.7, now states 6.3CVSS v4.0 · base scoreHighMediumTime to revision 7 days
Fri 12 Jun 2026· 1 change
2026-06-12CVSS base score changedCVE-2025-59382
whole record
qnap
stated at publication 5.1, now states 1.2CVSS v4.0 · base scoreMediumLowTime to revision 2 days
Tue 9 Jun 2026· 4 changes
2026-06-09Product addedCVE-2025-66274qnapnot named as affected at publication, now names qtsTime to revision 118 days
2026-06-09CVSS base score changedCVE-2025-59381
whole record
qnap
stated at publication 4.6, now states 6.9CVSS v4.0 · base scoreMediumMediumTime to revision 158 days
2026-06-09CVSS base score changedCVE-2025-66274
whole record
qnap
stated at publication 1.2, now states 5.1CVSS v4.0 · base scoreLowMediumTime to revision 118 days
2026-06-09CVSS base score changedCVE-2026-22895
whole record
qnap
stated at publication 2.2, now states 6.2CVSS v4.0 · base scoreLowMediumTime to revision 81 days
Mon 12 Jan 2026· 1 change
2026-01-12CVSS base score changedCVE-2023-34976
whole record
qnap
stated at publication 4.3, now states 10.0CVSS v3.1 · base scoreMediumCriticalTime to revision 822 days
Thu 9 May 2024· 1 change
2024-05-09CVSS base score changedCVE-2023-50364
whole record
qnap
stated at publication 5.5, now states 6.4CVSS v3.1 · base scoreMediumMediumTime to revision 12 days
Fri 8 Mar 2024· 3 changes
2024-03-08Product addedCVE-2023-34975qnapnot named as affected at publication, now names qts and 1 moreTime to revision 147 days
2024-03-08same kind of change as the line aboveCVE-2023-34975same vendor as the line abovenot named as affected at publication, now names qtsTime to revision 147 days
2024-03-08same kind of change as the line aboveCVE-2023-34975same vendor as the line abovenot named as affected at publication, now names quts heroTime to revision 147 days
2024-03-08CVSS base score changedCVE-2023-34975
whole record
qnap
stated at publication 7.4, now states 6.6CVSS v3.1 · base scoreHighMediumTime to revision 147 days
Wed 30 Aug 2023· 1 change
2023-08-30Product addedCVE-2023-23355qnapnot named as affected at publication, now names qutscloudTime to revision 154 days

Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

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

What this page cannot see

Not checked: A CVE record published before 2023, and a KEV listing added before 2025-01-27, were never seen changing. An absence here is not evidence that a record held.

A change shown here is a change to a public record, evidenced by a commit anyone can read in the publisher's own history. It is not an assertion of wrongdoing, negligence or bad faith by any publisher or vendor, not evidence that any fix was incomplete, and not a statement about anyone's systems.

The units, the refusals, the cut-offs and every source, in full →

Paste your closed CVE tickets and see which of these changes hit them →