Skip to content

Affected range extended

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

13 changes behind one line · newest firstCSVJSONRSS

SinceClear all

One change, in full: Affected range extended: 6.5.24 → 6.5.25 from adobe. The same change in 13 CVE records. Back to the ledger

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.
2026-07-15CVE-2026-48254
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-48257
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-48255
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-48252
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-48262
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-48253
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-48261
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-48355
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-48260
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-48263
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-48359
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-48259
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-48310
adobeadobe experience manager 6.5
stated at publication 6.5.24, now states 6.5.25Release branch starts at 0.Days to revision 1

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.

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 →