All changesmicrosoftas of 2026-09-07
CVE-2024-29059
microsoftmicrosoft .net framework 2.0 service pack 2cve.org →this looks wrong →
In CISA KEVlisted 2025-02-04federal fix was due 2025-02-25
Record history
3 dated edit eventsPublished
- 6 release branches, each stating a fix version
47 days between eventsFix version raisedSource 4e6d978 — commit 4e6d9781bc38 in the CVE catalog
- fixed from 3.0.50727.8975, now fixed from 3.0.50727.8976microsoft .net framework 2.0 service pack 2 and 1 more
- fixed from 4.8.9206.0, now fixed from 4.8.09214.01microsoft .net framework 3.5 and 4.8.1
- fixed from 4.7.4076.0, now fixed from 4.7.04081.03microsoft .net framework 4.6.2
- and 1 more branch in this commit, listed under Where you stand
237 days between eventsFix version raisedSource 7f6b2f9 — commit 7f6b2f9b9a38 in the CVE catalog
- fixed from 4.8.4682.0, now fixed from 4.8.04690.02microsoft .net framework 3.5 and 4.8
- fixed from 4.7.4076.0, now fixed from 4.7.04081.03microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2
35 days between eventsAdded to CISA KEVSource 85e0d86 — commit 85e0d86c8c72 in the CISA KEV
- Not listedListed 2025-02-04
580 days to snapshotSnapshot
- 6 release branches, every one moved since publication
Where you stand
| Branch | Fix stated at publication | Fix stated today | Stood |
|---|---|---|---|
| microsoft .net framework 2.0 service pack 2from 2.0.0 | at publication 3.0.50727.8975 | today 3.0.50727.8976 | stood 47 days |
| microsoft .net framework 3.0 service pack 2from 3.0.0 | at publication 3.0.50727.8975 | today 3.0.50727.8976 | stood 47 days |
| microsoft .net framework 3.5 and 4.8from 4.8.0 | at publication 4.8.4682.0 | today 4.8.04690.02 | stood 47 days |
| microsoft .net framework 3.5 and 4.8.1from 4.8.1 | at publication 4.8.9206.0 | today 4.8.09214.01 | stood 47 days |
| microsoft .net framework 4.6.2from 4.7.0 | at publication 4.7.4076.0 | today 4.7.04081.03 | stood 47 days |
| microsoft .net framework 4.6.2/4.7/4.7.1/4.7.2from 4.7.0 | at publication 4.7.4076.0 | today 4.7.04081.03 | stood 47 days |
Check your tickets
Add your patched version to compare it with the recorded boundary.
Change cards link to the source commit. Compare CVE values with the first mirrored record and KEV values with the preceding catalog snapshot. The full recipe →
Data coverage & methodology
CVE values compare the first mirrored record with later source states. Initial records may have been backfilled after publication. KEV events compare consecutive catalog snapshots. Dates identify the reported value’s first observed appearance; earlier intermediate revisions may exist. Only counted rows contribute to totals. as of the 2026-09-07 snapshot.
1 row marked filtered, not counted is on the rail and counted nowhere. 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.
Under Where you stand, only branches whose boundary moved are shipped, so a branch that held is not listed. Stood is days from publication to the first recorded revision of that branch.
Not checked: a record published before 2023 cannot have its state at publication recovered, so the CVE-record checks never compared it. For such a record, silence on this page means it was not looked at, not that it held.
Not checked: a CISA KEV listing added before 2025-01-27 was never seen changing, so a record that has been in KEV for years carries no listing node here. A missing KEV node is not evidence that CISA has not listed it.
The GitHub Advisory Database was read and carries no changed advisory naming CVE-2024-29059. An advisory is an entry in the GitHub Advisory Database, the GHSA page a Dependabot alert links to. It is reached from a CVE id only when the advisory names that CVE id itself, and many advisories name none. So no advisory here means none was found among the advisories that name one of these ids. It does not mean there is nothing to find.
How every one of these figures is measured, in full →
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.
Shipped snapshot computed 2026-09-07 from catalog commit ed5547afbae2. Real findings, not live ones: records amended since are not reflected. A later fix version is evidence that the record changed, not evidence that the first fix was incomplete.