Skip to content

Affected range extended

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

31 refused changes behind one line · newest firstCSVJSONRSS

SinceClear the filter
ChangedSourceRows

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.

One change, in full: Affected range extended: 2.4.4-p11 → 2.4.8-beta1 from adobe. The same change in 31 CVE records. Back to the ledger

Rows we checked and refused, counted nowhere of "Affected range extended", 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.
2025-02-25CVE-2025-24406
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24407
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24408
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24409
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24410
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24411
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24412
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24413
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24414
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24415
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24416
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24417
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24418
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24419
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24420
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24421
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24422
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24423
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24424
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24425
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24426
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24427
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24428
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24429
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24430
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24432
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24434
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24435
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24436
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24437
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14
2025-02-25CVE-2025-24438
adobeadobe commerce
stated at publication 2.4.4-p11, now states 2.4.8-beta1Release branch starts at 0.Not counted: Prerelease named as the boundary. a prerelease qualifier on one side — a beta or release candidate is not a version anyone was told to patch toDays to revision 14

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 →