Skip to content

Affected range extended

What a record said when it was published, what it says now, and the commit that changed it.

16 changes · newest first · grouped by dayCSVJSONRSS

SinceClear all
ChangedSourceRows
Counted changes of "Affected range extended" from Adobe, 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.Record, 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 15 Jul 2026· 13 record changes
2026-07-15
adobeadobe experience manager 6.5
stated at publication 6.5.24, now states 6.5.25Release branch starts at 0.Days to revision 1
2026-07-15CVE-2026-48254same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Days to revision 1
2026-07-15CVE-2026-48257same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Days to revision 1
2026-07-15CVE-2026-48255same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Days to revision 1
2026-07-15CVE-2026-48252same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Days to revision 1
2026-07-15CVE-2026-48262same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Days to revision 1
2026-07-15CVE-2026-48253same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Days to revision 1
2026-07-15CVE-2026-48261same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Days to revision 1
2026-07-15CVE-2026-48355same vendor as the line abovesame change as the line aboveRelease branch starts at 0.Days to revision 1
5 more rows in this change are not listed here. Open all 13 rows
Tue 14 Jul 2026· 1 record change
2026-07-14CVE-2026-34690
adobeafter effects
stated at publication 25.6.4, now states 25.6.5Release branch starts at 0.Days to revision 63
Fri 13 Sep 2024· 2 record changes
2024-09-13CVE-2024-39420
adobeacrobat reader
stated at publication 24.001.30123, now states 24.003.20054Release branch starts at 0.Days to revision 30
2024-09-13CVE-2024-41856
adobeillustrator
stated at publication 27.9.4, now states 27.9.5Release branch starts at 0.Days to revision 30

This kind is counted once per record, product and release branch, so one record that moved the boundary on four branches counts four times and the number of records behind these changes is smaller. 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.

Use arrow keys to move between days, Home or End to reach either end, and Enter to open a day.
3,898 records with a counted edit in the 52 weeks to 7 Sep 2026 · snapshot built 03:47 UTC · scroll for earlierfewermore

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 →