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.

3,930 record edits refused · 339 advisory changes · newest first · grouped by dayCSVJSONRSS

Since
ChangedSourceRows

These rows are not counted anywhere on this site. Checked and refused means we compared this change and then rejected it: the false positive filter for this kind of change judged it to be a false positive rather than a real change. The row is shown so you can check the filter and disagree with us, and it is counted in no figure on this site. No advisory change is here: the advisory engine counts the 2,291 version pairs its filters refused by class rather than writing them out one by one, so this view holds CVE and KEV changes only.

Rows we checked and refused, counted nowhere, newest first, one line per change to a CVE record or a GHSA advisory, or per run of identical changes collapsed into one line.
Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin.KindRecord or advisory, Which record was edited: a CVE id where the change was to the CVE catalog or the CISA KEV list, a GHSA id where it was to a GitHub advisory. The two are different units and are never counted together.Vendor or package, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry.What changedDays to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong.
Thu 3 Apr 2025· 1 record change
2025-04-03CVSS base score changedCVE-2023-1030
whole record
VulDB
stated at publication 4.0, now states 5.1Assessments not comparable · base scoreMediumMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removedDays to revision 769
Mon 31 Mar 2025· 16 record changes
2025-03-312 commitsProduct addedmitrenot named as affected at publication, now names hpe athonet coreBranches and original-value intervals are stated on each row.not counted: No products named at publicationDays to revision 137
2025-03-31same kind of change as the line aboveCVE-2024-24454same vendor as the line abovesame change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 137
2025-03-31same kind of change as the line aboveCVE-2024-24455same vendor as the line abovesame change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 137
2025-03-31same kind of change as the line aboveCVE-2024-24457same vendor as the line abovesame change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 137
2025-03-31same kind of change as the line aboveCVE-2024-24458same vendor as the line abovesame change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 137
2025-03-31same kind of change as the line aboveCVE-2024-24459same vendor as the line abovesame change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 137
2025-03-31same kind of change as the line aboveCVE-2024-24452same vendor as the line abovesame change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 137
2025-03-31same kind of change as the line aboveCVE-2024-24453same vendor as the line abovesame change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 137
2025-03-31CVSS base score changedCVE-2025-1398
whole record
Mattermost
stated at publication 10.0, now states 3.3Assessments not comparable · base scoreCriticalLowNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removedDays to revision 14
2025-03-31CVSS base score changed
whole record
VulDB
stated at publication 9.0, now states 8.6Assessments not comparable · base scoreCriticalHighnot counted: CVSS assessments are not comparableDays to revision 6
2025-03-31same kind of change as the line aboveCVE-2025-2725same vendor as the line abovesame change as the line aboveNot 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 comparableDays to revision 6
2025-03-31same kind of change as the line aboveCVE-2025-2726same vendor as the line abovesame change as the line aboveNot 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 comparableDays to revision 6
2025-03-31same kind of change as the line aboveCVE-2025-2727same vendor as the line abovesame change as the line aboveNot 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 comparableDays to revision 6
2025-03-31same kind of change as the line aboveCVE-2025-2728same vendor as the line abovesame change as the line aboveNot 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 comparableDays to revision 6
2025-03-31same kind of change as the line aboveCVE-2025-2729same vendor as the line abovesame change as the line aboveNot 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 comparableDays to revision 6
2025-03-31same kind of change as the line aboveCVE-2025-2730same vendor as the line abovesame change as the line aboveNot 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 comparableDays to revision 6
2025-03-31same kind of change as the line aboveCVE-2025-2731same vendor as the line abovesame change as the line aboveNot 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 comparableDays to revision 6
2025-03-31same kind of change as the line aboveCVE-2025-2732same vendor as the line abovesame change as the line aboveNot 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 comparableDays to revision 6
Fri 28 Mar 2025· 4 record changes
2025-03-28Affected range extendedCVE-2025-1860
zeframdata::entropy
CPANSec
stated at publication 0.007, now states 0.008Release 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 operatorDays to revision 0
2025-03-28Product addedmitrenot named as affected at publication, now names mispnot counted: No products named at publicationDays to revision 1
2025-03-28same kind of change as the line aboveCVE-2024-58128same vendor as the line abovesame change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 1
2025-03-28same kind of change as the line aboveCVE-2024-58129same vendor as the line abovesame change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 1
2025-03-28same kind of change as the line aboveCVE-2024-58130same vendor as the line abovesame change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 1
Thu 27 Mar 2025· 3 record changes
2025-03-27Fix version movedCVE-2025-2565
liferaydxp
stated at publication 2024.Q1.13, now states 2024.Q1.12Release branch starts at 2024.Q1.1.Not counted: Same claim, other operator. `unaffected_start` rewritten as `lte` on the same or the next release — the same claim under the other operatorDays to revision 7
2025-03-272 commitsProduct addedmitrenot named as affected at publication, now names infocad fmBranches and original-value intervals are stated on each row.not counted: No products named at publicationDays to revision 8
2025-03-27same kind of change as the line aboveCVE-2025-26853same vendor as the line abovesame change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 8
2025-03-27same kind of change as the line aboveCVE-2025-26852same vendor as the line abovesame change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 8
Wed 26 Mar 2025· 1 record change
2025-03-26Product addedCVE-2025-30742mitrenot named as affected at publication, now names atophttpdNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 0
Tue 25 Mar 2025· 4 record changes
2025-03-25Product addedCVE-2025-30741mitrenot named as affected at publication, now names pixelfedNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 1
2025-03-25Product addedCVE-2024-52531mitrenot named as affected at publication, now names libsoupNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 135
2025-03-25Product addedCVE-2024-55551mitrenot named as affected at publication, now names jdbc driverNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 7
2025-03-25Product addedCVE-2024-44903mitrenot named as affected at publication, now names ipac20Not counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 0
Mon 24 Mar 2025· 2 record changes
2025-03-24Affected range extendedCVE-2024-13496
rubengcgamipress – gamification plugin to reward points, achievements, badges & ranks in wordpress
Wordfence
stated at publication 7.2.1, now states 7.3.1Release branch starts at 0.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpDays to revision 61
2025-03-24Product addedCVE-2024-45965mitrenot named as affected at publication, now names contaoNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 174
Fri 21 Mar 2025· 5 record changes
2025-03-21Product addedCVE-2025-30348mitrenot named as affected at publication, now names qtNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 0
2025-03-213 commitsProduct addedmitrenot named as affected at publication, now names openslidesBranches and original-value intervals are stated on each row.not counted: No products named at publicationDays to revision 0
2025-03-21same kind of change as the line aboveCVE-2025-30345same vendor as the line abovesame change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 0
2025-03-21same kind of change as the line aboveCVE-2025-30344same vendor as the line abovesame change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 0
2025-03-21same kind of change as the line aboveCVE-2025-30342same vendor as the line abovesame change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 0
2025-03-21same kind of change as the line aboveCVE-2025-30343same vendor as the line abovesame change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 0
Thu 20 Mar 2025· 2 record changes
2025-03-20Product addedCVE-2025-26318mitrenot named as affected at publication, now names tsplus remote accessNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 17
2025-03-20Product addedCVE-2024-27564mitrenot named as affected at publication, now names mm1.ltd source codeNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 380
Wed 19 Mar 2025· 4 record changes
2025-03-19Product addedCVE-2025-30259mitrenot named as affected at publication, now names whatsapp cloud serviceNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 1
2025-03-192 commitsProduct addedmitrenot named as affected at publication, now names securaccessBranches and original-value intervals are stated on each row.not counted: No products named at publicationDays to revision 0
2025-03-19same kind of change as the line aboveCVE-2025-30236same vendor as the line abovesame change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 0
2025-03-19same kind of change as the line aboveCVE-2025-30235same vendor as the line abovesame change as the line aboveNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 0
2025-03-19Product addedCVE-2025-30234mitrenot named as affected at publication, now names smartosNot counted: No products named at publication. record named no affected product at publication — there was nothing to conclude 'not affected' fromDays to revision 0
Sun 16 Mar 2025· 1 advisory change
2025-03-16published 2024-12-18Package added to advisoryGHSA-w32m-9786-jp63CVE-2024-45338highnot named as affected when the advisory was published, now names golang.org/x/net/htmlDays to revision 88
Thu 13 Mar 2025· 1 record change
2025-03-13CVSS base score changedCVE-2024-9005
whole record
schneider
stated at publication 7.1, now states 7.3Assessments 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 removedDays to revision 156
Wed 12 Mar 2025· 2 record changes
2025-03-12Fix version movedCVE-2025-1683
1e1e client
stated at publication 24.5, now states 24.5Release 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 operatorDays to revision 0
2025-03-12Fix version movedCVE-2025-1683
1e1e client
stated at publication 25.1, now states 25.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 operatorDays to revision 0
Mon 10 Mar 2025· 2 record changes
2025-03-10Fix version movedCVE-2025-1015
mozillathunderbird
stated at publication 128.7, now states 135Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 128.7 still holdsnot dated
2025-03-10CVSS base score changedCVE-2025-2030
whole record
VulDB
stated at publication 6.5, now states 7.5Assessments not comparable · base scoreMediumHighNot 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 comparableDays to revision 4
Mon 3 Mar 2025· 1 record change
2025-03-03Affected range extendedCVE-2025-24633
silverplugins217build private store for woocommerce
Patchstack
stated at publication 1.0, now states 1.1Release 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 matchednot dated
Wed 26 Feb 2025· 1 advisory change
2025-02-26published 2025-02-24Package added to advisoryGHSA-c6gw-w398-hv78CVE-2025-27144moderatenot named as affected when the advisory was published, now names github.com/go-jose/go-joseDays to revision 2
Tue 25 Feb 2025· 31 record changes
2025-02-25Affected range extended
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.not counted: Prerelease named as the boundaryDays to revision 14
2025-02-25same kind of change as the line aboveCVE-2025-24406same vendor as the line abovesame change as the line aboveRelease 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 toDays to revision 14
2025-02-25same kind of change as the line aboveCVE-2025-24407same vendor as the line abovesame change as the line aboveRelease 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 toDays to revision 14
2025-02-25same kind of change as the line aboveCVE-2025-24408same vendor as the line abovesame change as the line aboveRelease 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 toDays to revision 14
2025-02-25same kind of change as the line aboveCVE-2025-24409same vendor as the line abovesame change as the line aboveRelease 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 toDays to revision 14
2025-02-25same kind of change as the line aboveCVE-2025-24410same vendor as the line abovesame change as the line aboveRelease 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 toDays to revision 14
2025-02-25same kind of change as the line aboveCVE-2025-24411same vendor as the line abovesame change as the line aboveRelease 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 toDays to revision 14
2025-02-25same kind of change as the line aboveCVE-2025-24412same vendor as the line abovesame change as the line aboveRelease 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 toDays to revision 14
2025-02-25same kind of change as the line aboveCVE-2025-24413same vendor as the line abovesame change as the line aboveRelease 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 toDays to revision 14
23 more rows in this change are not listed here. Open all 31 rows
Thu 20 Feb 2025· 1 record change
2025-02-20Fix version movedCVE-2024-5921
palo alto networksglobalprotect app
palo_alto
stated at publication 6.2.6, now states 6.3.2Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 6.2.6 still holdsnot dated
Wed 19 Feb 2025· 1 record change
2025-02-19CVSS base score changedCVE-2024-11146
whole record
cisa-cg
stated at publication 7.3, now states 6.3Assessments not comparable · base scoreHighMediumNot 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 comparableDays to revision 34
Sun 16 Feb 2025· 1 record change
2025-02-16CVSS base score changedCVE-2024-0532
whole record
VulDB
stated at publication 8.3, now states 8.6Assessments 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 removedDays to revision 398
Tue 11 Feb 2025· 2 record changes
2025-02-11Fix version movedCVE-2023-24932
microsoftwindows 11 version 21h2
stated at publication 10.0.22000.1936, now states 10.0.22000.3079Release 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 matchednot dated
2025-02-11CVSS base score changedCVE-2024-35212
whole record
siemens
stated at publication 7.5, now states 6.9Assessments not comparable · base scoreHighMediumNot 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 comparableDays to revision 245
Fri 7 Feb 2025· 1 record change
2025-02-07CVSS base score changedCVE-2024-9404
whole record
Moxa
stated at publication 6.9, now states 8.7Assessments not comparable · base scoreMediumHighNot 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 comparableDays to revision 65
Wed 5 Feb 2025· 1 advisory change
2025-02-05published 2025-01-30Package added to advisoryGHSA-47g2-qmh2-749vCVE-2025-23216moderatenot named as affected when the advisory was published, now names github.com/argoproj/argo-cdDays to revision 6
Tue 4 Feb 2025· 2 record changes
2025-02-04CVSS base score changedCVE-2024-21544
whole record
snyk
stated at publication 7.7, now states 8.6Assessments not comparable · base scoreHighHighNot 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 comparableDays to revision 53
2025-02-04CVSS base score changedCVE-2024-21549
whole record
snyk
stated at publication 8.7, now states 8.6Assessments not comparable · base scoreHighHighNot 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 comparableDays to revision 46
Fri 31 Jan 2025· 1 record change
2025-01-31CVSS base score changedCVE-2024-12248
whole record
icscert
stated at publication 9.3, now states 9.8Assessments not comparable · base scoreCriticalCriticalNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removedDays to revision 1
Tue 28 Jan 2025· 3 record changes
2025-01-28Affected range extendedCVE-2024-37008
autodeskrevit
stated at publication 2022.1.6, now states 2022.1.7Release branch starts at 2022.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 160
2025-01-28Affected range extendedCVE-2024-37008
autodeskrevit
stated at publication 2023.1.4, now states 2023.1.5Release branch starts at 2023.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 160
2025-01-28Affected range extendedCVE-2024-37008
autodeskrevit
stated at publication 2024.2.1, now states 2024.2.2Release branch starts at 2024.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 160
Fri 17 Jan 2025· 1 record change
2025-01-17CVSS base score changedCVE-2023-50738
whole record
Lexmark
stated at publication 10.0, now states 4.3Assessments not comparable · base scoreCriticalMediumNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removedDays to revision 0
Wed 15 Jan 2025· 1 record change
2025-01-15CVSS base score changedCVE-2024-12569
whole record
Milestone
stated at publication 5.2, now states 7.8Assessments not comparable · base scoreMediumHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removedDays to revision 27
Tue 14 Jan 2025· 4 record changes
2025-01-14CVSS base score changedCVE-2023-44317
whole record
siemens
stated at publication 7.2, now states 8.6Assessments 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 removedDays to revision 427
2025-01-14CVSS base score changed
whole record
siemens
stated at publication 4.9, now states 6.9Assessments not comparable · base scoreMediumMediumnot counted: CVSS version set changedDays to revision 427
2025-01-14same kind of change as the line aboveCVE-2023-44318same vendor as the line abovesame change as the line aboveNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removedDays to revision 427
2025-01-14same kind of change as the line aboveCVE-2023-44319same vendor as the line abovesame change as the line aboveNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removedDays to revision 427
2025-01-14CVSS base score changedCVE-2023-44374
whole record
siemens
stated at publication 6.5, now states 7.1Assessments not comparable · base scoreMediumHighNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removedDays to revision 427
Fri 10 Jan 2025· 1 advisory change
2025-01-10published 2024-12-02Package added to advisoryGHSA-4cx5-89vm-833xCVE-2024-52800lownot named as affected when the advisory was published, now names org.verapdf:verapdf-libraryDays to revision 39
Thu 9 Jan 2025· 1 record change
2025-01-09CVSS base score changedCVE-2024-13205
whole record
VulDB
stated at publication 5.8, now states 5.1Assessments not comparable · base scoreMediumMediumNot 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 comparableDays to revision 0
Fri 3 Jan 2025· 1 record change
2025-01-03Fix version movedCVE-2024-12801
qos.ch sarllogback
NCSC.ch
stated at publication 1.5.12, now states 1.5.12Release 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 operatorDays to revision 15
Wed 1 Jan 2025· 205 record changes
2025-01-01Fix version moved
microsoftwindows 10 version 21h2
stated at publication 10.0.19041.3693, now states 10.0.19043.3693Release branch starts at *.not counted: Product line renumberednot dated
2025-01-01same kind of change as the line aboveCVE-2023-36017same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-36025same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-36028same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-36033same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-36036same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-36047same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-36393same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-36394same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
12 more rows in this change are not listed here. Open all 20 rows
2025-01-01Fix version moved
microsoftwindows 10 version 21h2
stated at publication 10.0.19041.3208, now states 10.0.19044.3208Release branch starts at *.not counted: Product line renumberednot dated
2025-01-01same kind of change as the line aboveCVE-2023-21526same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-21756same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-32034same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-32035same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-32037same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-32038same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-32039same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-32040same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
70 more rows in this change are not listed here. Open all 78 rows
2025-01-01Fix version moved
microsoftwindows 11 version 22h2
stated at publication 10.0.22621.2275, now states 10.0.22621.2283Release branch starts at *.not counted: Release branches rewrittennot dated
2025-01-01same kind of change as the line aboveCVE-2023-35355same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2025-01-01same kind of change as the line aboveCVE-2023-36802same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2025-01-01same kind of change as the line aboveCVE-2023-36803same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2025-01-01same kind of change as the line aboveCVE-2023-36804same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2025-01-01same kind of change as the line aboveCVE-2023-36805same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2025-01-01same kind of change as the line aboveCVE-2023-38139same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2025-01-01same kind of change as the line aboveCVE-2023-38141same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2025-01-01same kind of change as the line aboveCVE-2023-38142same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
9 more rows in this change are not listed here. Open all 17 rows
2025-01-01Fix version moved
microsoftwindows server 2022
stated at publication 10.0.20348.1960, now states 10.0.20348.1970Release branch starts at *.not counted: Release branches rewrittennot dated
2025-01-01same kind of change as the line aboveCVE-2023-35355same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2025-01-01same kind of change as the line aboveCVE-2023-36801same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2025-01-01same kind of change as the line aboveCVE-2023-36802same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2025-01-01same kind of change as the line aboveCVE-2023-36803same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2025-01-01same kind of change as the line aboveCVE-2023-36804same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2025-01-01same kind of change as the line aboveCVE-2023-36805same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2025-01-01same kind of change as the line aboveCVE-2023-38139same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2025-01-01same kind of change as the line aboveCVE-2023-38140same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
11 more rows in this change are not listed here. Open all 19 rows
2025-01-01Fix version moved
microsoftwindows 11 version 22h2
stated at publication 10.0.22000.1702, now states 10.0.22621.1702Release branch starts at *.not counted: Product line renumberednot dated
2025-01-01same kind of change as the line aboveCVE-2023-24899same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-24900same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-24901same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-24902same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-24903same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-24905same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-24939same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-24940same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
10 more rows in this change are not listed here. Open all 18 rows
2025-01-01Fix version moved
microsoftwindows 11 version 22h2
stated at publication 10.0.22000.1413, now states 10.0.22621.1413Release branch starts at *.not counted: Product line renumberednot dated
2025-01-01same kind of change as the line aboveCVE-2023-21708same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-23385same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-23388same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-23392same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-23393same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-23394same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-23401same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
2025-01-01same kind of change as the line aboveCVE-2023-23402same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
44 more rows in this change are not listed here. Open all 52 rows
2025-01-01Fix version movedCVE-2023-21712
microsoftwindows 11 version 22h2
stated at publication 10.0.22000.819, now states 10.0.22621.819Release branch starts at *.Not counted: Product line renumbered. leading component changed with meaningful tail intact — product-line renumbering, not a fix bumpnot dated
Tue 31 Dec 2024· 180 record changes
2024-12-31Fix version moved
microsoftwindows 10 version 1507
stated at publication 10.0.10240.20796, now states 10.0.10240.20826Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-43511same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43516same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version movedCVE-2024-43511
microsoft3 products
stated at publication 10.0.14393.7428, now states 10.0.14393.7515Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-43511same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43511same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43511same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version moved7 rows, one per record, product and release branch
microsoft3 products
stated at publication 10.0.17763.6414, now states 10.0.17763.6532Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-43511same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43511same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43511same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43516same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43516same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43516same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43528same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version moved
microsoftwindows 10 version 21h2
stated at publication 10.0.19044.5011, now states 10.0.19044.5131Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-43511same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43516same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version moved
microsoftwindows 10 version 22h2
stated at publication 10.0.19045.5011, now states 10.0.19045.5131Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-43511same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43516same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version moved
microsoftwindows 11 version 22h2
stated at publication 10.0.22621.4317, now states 10.0.22621.4460Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-43511same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43516same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version moved4 rows, one per record, product and release branch
microsoft2 products
stated at publication 10.0.22631.4317, now states 10.0.22631.4460Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-43511same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43511same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43516same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43516same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version moved
microsoftwindows 11 version 24h2
stated at publication 10.0.26100.2033, now states 10.0.26100.2303Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-43511same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43516same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version moved
microsoftwindows server 2022, 23h2 edition (server core installation)
stated at publication 10.0.25398.1189, now states 10.0.25398.1251Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-43511same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43516same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version movedCVE-2024-43516
microsoft3 products
stated at publication 10.0.14393.7428, now states 10.0.14393.7515Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-43516same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43516same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-43516same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version movedCVE-2024-38063
microsoft3 products
stated at publication 10.0.17763.6189, now states 10.0.17763.6293Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-38063same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-38063same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-38063same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version moved
microsoftwindows server 2022
stated at publication 10.0.20348.2655, now states 10.0.20348.2700Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-38063same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-38138same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version movedCVE-2024-38138
microsoft2 products
stated at publication 10.0.14393.7259, now states 10.0.14393.7336Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-38138same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-38138same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version movedCVE-2024-38138
microsoft2 products
stated at publication 10.0.17763.6189, now states 10.0.17763.6414Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-38138same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-38138same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version movedCVE-2024-38138
microsoftwindows server 2022, 23h2 edition (server core installation)
stated at publication 10.0.25398.1085, now states 10.0.25398.1128Release 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 matchednot dated
2024-12-31Fix version movedCVE-2024-38033
microsoft2 products
stated at publication 6.2.9200.24975, now states 6.2.9200.25222Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-38033same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-38033same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version movedCVE-2024-38033
microsoft2 products
stated at publication 6.3.9600.22074, now states 6.3.9600.22318Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-38033same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-38033same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version moved
microsoftwindows 11 version 22h2
stated at publication 10.0.22621.3435, now states 10.0.22621.3447Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-20665same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-20669same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-20678same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-20693same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-21447same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26158same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26168same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26171same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
47 more rows in this change are not listed here. Open all 55 rows
2024-12-31Fix version moved
microsoftwindows 10 version 1507
stated at publication 10.0.10240.20596, now states 10.0.10240.20651Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-26207same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26211same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26217same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-28900same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-28902same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version moved15 rows, one per record, product and release branch
microsoft3 products
stated at publication 10.0.14393.6897, now states 10.0.14393.6981Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-26207same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26207same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26207same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26211same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26211same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26211same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26217same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26217same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
7 more rows in this change are not listed here. Open all 15 rows
2024-12-31Fix version moved
microsoftwindows 10 version 21h2
stated at publication 10.0.19044.4291, now states 10.0.19044.4412Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-26207same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26211same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26217same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-28900same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-28902same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version moved
microsoftwindows 10 version 22h2
stated at publication 10.0.19045.4291, now states 10.0.19045.4412Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-26207same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26211same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26217same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-28900same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-28902same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version moved
microsoftwindows 11 version 22h2
stated at publication 10.0.22621.3435, now states 10.0.22621.3593Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-26207same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26211same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-28900same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-28902same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version moved10 rows, one per record, product and release branch
microsoft2 products
stated at publication 10.0.22631.3447, now states 10.0.22631.3593Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-26207same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26207same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26211same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26211same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26217same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26217same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-28900same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-28900same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2 more rows in this change are not listed here. Open all 10 rows
2024-12-31Fix version moved10 rows, one per record, product and release branch
microsoft2 products
stated at publication 6.3.9600.21924, now states 6.3.9600.21972Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-26207same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26207same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26211same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26211same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26217same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26217same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-28900same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-28900same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2 more rows in this change are not listed here. Open all 10 rows
2024-12-31Fix version moved10 rows, one per record, product and release branch
microsoft2 products
stated at publication 10.0.17763.5696, now states 10.0.17763.5820Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-26207same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26207same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26211same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26211same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26217same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26217same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-28900same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-28900same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2 more rows in this change are not listed here. Open all 10 rows
2024-12-31Fix version moved
microsoftwindows server 2022
stated at publication 10.0.20348.2402, now states 10.0.20348.2461Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-26207same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26211same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26217same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-28900same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-28902same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version moved
microsoftwindows server 2022, 23h2 edition (server core installation)
stated at publication 10.0.25398.830, now states 10.0.25398.887Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-26207same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26211same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-26217same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-28900same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-28902same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version movedCVE-2024-21427
microsoft2 products
stated at publication 6.3.9600.21871, now states 6.3.9600.21924Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-21427same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-21427same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version movedCVE-2024-21427
microsoft2 products
stated at publication 10.0.14393.6796, now states 10.0.14393.6897Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-21427same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-21427same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version movedCVE-2024-21427
microsoft2 products
stated at publication 10.0.17763.5576, now states 10.0.17763.5696Release branch starts at *.not counted: Release branches rewrittennot dated
2024-12-31same kind of change as the line aboveCVE-2024-21427same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31same kind of change as the line aboveCVE-2024-21427same vendor as the line abovesame change as the line aboveRelease 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 matchednot dated
2024-12-31Fix version movedCVE-2024-21427
microsoftwindows server 2022
stated at publication 10.0.20348.2340, now states 10.0.20348.2402Release 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 matchednot dated
2024-12-31Fix version movedCVE-2024-21427
microsoftwindows server 2022, 23h2 edition (server core installation)
stated at publication 10.0.25398.763, now states 10.0.25398.830Release 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 matchednot dated
Tue 24 Dec 2024· 1 record change
2024-12-24CVSS base score changedCVE-2024-52926
whole record
mitre
stated at publication 7.3, now states 6.5Assessments not comparable · base scoreHighMediumNot 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 comparableDays to revision 37
Thu 12 Dec 2024· 1 advisory change
2024-12-12published 2024-11-27Package added to advisoryGHSA-55v3-xh23-96ghCVE-2024-53859moderatenot named as affected when the advisory was published, now names github.com/cli/go-ghDays to revision 15
Tue 10 Dec 2024· 1 record change
2024-12-10Fix version movedCVE-2024-6156canonicalstated at publication 5.21.2, now states 6.1Release branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 5.21.2 still holdsnot dated
Fri 6 Dec 2024· 1 record change
2024-12-06Affected range extendedCVE-2024-9287PSFstated at publication 3.13.0, now states 3.13.1Release branch starts at 0.Original value first replaced 2024-12-03; this value first seen 2024-12-06.Not counted: Same claim, other operator. `lte` rewritten as `lt` on the same or the next release — the same claim under the other operatorDays to revision 42
Thu 5 Dec 2024· 2 record changes
2024-12-05CVSS base score changed
whole record
ABB
stated at publication 9.4, now states 10.0Assessments not comparable · base scoreCriticalCriticalnot counted: CVSS version set changedDays to revision 153
2024-12-05same kind of change as the line aboveCVE-2024-6209same vendor as the line abovesame change as the line aboveNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removedDays to revision 153
2024-12-05same kind of change as the line aboveCVE-2024-6298same vendor as the line abovesame change as the line aboveNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removedDays to revision 153
Wed 4 Dec 2024· 1 advisory change
2024-12-04published 2024-12-04Package added to advisoryGHSA-2m9h-r57g-45pjCVE-2024-54132moderatenot named as affected when the advisory was published, now names github.com/cli/cliDays to revision 0
Thu 28 Nov 2024· 1 record change
2024-11-28CVSS base score changedCVE-2024-9076
whole record
VulDB
stated at publication 6.5, now states 5.8Assessments not comparable · base scoreMediumMediumNot 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 comparableDays to revision 67
Tue 26 Nov 2024· 1 record change
2024-11-26Affected range extendedCVE-2024-7882TR-CERTstated at publication 22.11.2024, now states 22.11.2024Release 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 operatorDays to revision 4

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 or an extended range counts once per record, product and release branch; an added product once per record and product; every other kind once per record or advisory. Days to revision is how long the value first stated stood: from the record's or advisory's publication, or from the day a KEV field value was first seen, to the first commit that replaced it. An addition to KEV has no earlier value and shows none. A collapsed line is one publisher's run of identical changes on one day; it says how many, and opens to all of them.

Data sources and quality

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 →

Check my CVEs against these changes →