All changesmitreas of 2026-09-07
CVE-2025-45526
Record history
1 dated edit eventPublished
The CVE record was published.
1 day between eventsExcluded comparisonnot countedSource 7e08b28 — commit 7e08b288b607 in the CVE catalog
- not namedmicrolight
Filtered, not counted: record named no affected product at publication — there was nothing to conclude 'not affected' from.
446 days to snapshotSnapshot
Source record: View on CVE.org ↗
GitHub advisories naming this CVE
2 advisory rows across 1 advisory, counted separately from the record's own rows above.
| Change | Advisory | Ecosystem / package | What the advisory says now | Severity |
|---|---|---|---|---|
| Advisory severity changed | GHSA-wgc6-9f6w-h8hxCVE-2025-45526 | whole advisory | stated at publication HIGH, now states LOWA vector changed on a shared CVSS version. The band and vector edits may have occurred separately. | low |
| Advisory withdrawn | GHSA-wgc6-9f6w-h8hxCVE-2025-45526 | whole advisory | withdrawn 2025-06-18 | low |
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.
Check my CVEs
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. Verify one finding yourself →
Data sources and quality
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.
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.
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.