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.

6 changes refused · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows

Showing changes seen on 2026-08-11. 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-11, newest first, one line per change to a CVE record, or per run of identical changes collapsed into one line.
Changed on, The day the change first became visible in the catalog's public history. Not the day the record was amended, which is earlier by an unknown margin.KindRecord, Which record was edited, by its CVE id, or how many records one collapsed line stands on.Vendor · product, The vendor and product a CVE record names, with the organisation that publishes the record under them; or the package an advisory names and its registry.What changedDays to revision, The earlier stated value's interval. For a version boundary, it ends at the first replacement of that value; the reported current value may appear later. Starting points differ by kind: record publication, advisory publication, or the observed introduction of a KEV field value. Intervals are not directly comparable across kinds. Missing dates mean unknown, never zero. This does not date when a value became wrong.
Tue 11 Aug 2026· 6 changes
2026-08-11Fix version movedCVE-2026-49179
microsoftwindows server 2012
stated at publication 6.2.9200.26279, now states 6.2.9200.26280Release branch starts at 6.2.9200.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 0.2 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that movedTime to revision 0 days
2026-08-11Fix version movedCVE-2026-49179
microsoftwindows server 2012 (server core installation)
stated at publication 6.2.9200.26279, now states 6.2.9200.26280Release branch starts at 6.2.9200.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 0.2 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that movedTime to revision 0 days
2026-08-11Fix version movedCVE-2026-49179
microsoftwindows server 2012 r2
stated at publication 6.3.9600.23337, now states 6.3.9600.23338Release branch starts at 6.3.9600.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 0.2 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that movedTime to revision 0 days
2026-08-11Fix version movedCVE-2026-49179
microsoftwindows server 2012 r2 (server core installation)
stated at publication 6.3.9600.23337, now states 6.3.9600.23338Release branch starts at 6.3.9600.0.Not counted: Build number corrected to the one that shipped. only the build revision moved, 0.2 days after publication — the publisher corrected the build number to the one that shipped, which is not a fix that movedTime to revision 0 days
2026-08-11Affected range extendedCVE-2026-13410
garudancer::plugin::auth::google
CPANSec
stated at publication 0.07, now states 0.08Release 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 operatorTime to revision 25 days
2026-08-11Product addedCVE-2026-10579not named as affected at publication, now names red hat jboss enterprise application platform 7.4.25Not counted: Added entry does not state affected status. the added entry states no affected version or affected default — membership in affected[] alone does not establish exposureTime to revision 1 days

Rows, not records: a moved fix version and an added product count once per product, every other kind once per record or advisory.

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 →