Skip to content

Every change, newest first

Compare earlier and later source statements, with the dates and evidence behind each measured change.

10 changes refused · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows

Showing changes seen on 2026-08-26. Every day

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 changed on 2026-08-26, newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin.KindRecord, Which record was edited, by its CVE id, or how many records one collapsed line stands on.Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry.What changedDays to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong.
Wed 26 Aug 2026· 10 changes
2026-08-26Affected range extended
adobedreamweaver desktop
stated at publication 21.7, now states 21.8Release branch starts at *.not counted: Another branch advancedDuration unknown
2026-08-26same kind of change as the line aboveCVE-2026-47906same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 21.7 still holdsDuration unknown
2026-08-26same kind of change as the line aboveCVE-2026-47907same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 21.7 still holdsDuration unknown
2026-08-26same kind of change as the line aboveCVE-2026-47908same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 21.7 still holdsDuration unknown
2026-08-26same kind of change as the line aboveCVE-2026-47909same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 21.7 still holdsDuration unknown
2026-08-26same kind of change as the line aboveCVE-2026-47910same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 21.7 still holdsDuration unknown
2026-08-26Affected range extended
adobeformat plugins
stated at publication 1.1.2, now states 1.1.3Release branch starts at *.not counted: Another branch advancedDuration unknown
2026-08-26same kind of change as the line aboveCVE-2026-48291same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 1.1.2 still holdsDuration unknown
2026-08-26same kind of change as the line aboveCVE-2026-48292same vendor as the line abovesame change as the line aboveRelease branch starts at *.Not counted: Another branch advanced. another release branch was added — every branch stated at publication is still stated, so 1.1.2 still holdsDuration unknown
2026-08-26Affected range extendedCVE-2026-5917
libgit2libgit2
VulnCheck
stated at publication 1.9.0, now states 1.9.7Release branch starts at *.Not counted: Release branches rewritten. the range layout was rewritten: a branch stated at publication is gone and another appeared, so no branch can be matchedDuration unknown
2026-08-26Product addedCVE-2026-77998Joomlanot named as affected at publication, now names saml sso free for joomla extension for joomlaNot counted: Product identity rewritten with unchanged scope. unchanged affected scope with a rewritten title of removed miniorange.com/saml sso for joomla extension for joomla; a new product identity is not establishedTime to revision 1 days
2026-08-26CVSS base score changedCVE-2025-12945
whole record
NETGEAR
stated at publication 1.1, now states 2.4Assessments not comparable · base scoreLowLowNot counted: CVSS version set changed. no CVSS version was rescored — the maximum moved because a different CVSS version was added or removedTime to revision 260 days

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

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

What this page cannot see

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

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

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

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