PCRE2 before 10.48 allows a pcre2_dfa_match out-of-bounds write because reuse of a cached workspace block, in a recursive DFA matching workspace, lacks a size check (even though a newly allocated block, for the same purpose, does have a size check). This outcome requires an attacker-controlled regular expression, or a recursive pattern in conjunction with a small heap limit (this can be set through the API).

• azl3 pcre2 10.42-3 on Azure Linux 3.0

SecurityAlert records field-level changes from the point we begin following a bulletin. Earlier vendor changes may not have a field-by-field record.

1. Sep 27, 2026 at 11:11 PM UTC
   • The vendor changed the advisory's last-updated date.
2. Sep 17, 2026 at 10:05 AM UTC
   • Added fixed versions: 10.48-1.

1. Sep 6, 2026 at 4:37 AM UTC
   Published by Microsoft Security Response Center

   The publication date reported by the vendor.

2. Sep 8, 2026 at 7:05 AM UTC
   Added to SecurityAlert

   We collected the advisory from the official source.

3. Sep 19, 2026 at 1:59 AM UTC
   Updated by Microsoft Security Response Center

   The vendor changed the advisory after it was first published.

4. Oct 28, 2026 at 3:45 AM UTC
   Confirmed at the source

   Our collector saw this advisory during a later source check.