Skip to content
Threat Brief

← All advisories

CVE-2026-103111

High 8.1No known exploitationFix available

PCRE2 before 10.49, when there is an attacker-controlled regular expression and certain JIT API usage, allows an out-of-bounds write with arbitrary data.

Record last updated

CVSS score

8.1

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

None

No EPSS score available

CISA remediation deadline

None

Not in the KEV catalog

Description

No description has been published yet.

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
Microsoftazl3 pcre2 10.48-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 rust 1.96.1-2 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl3 rust 1.98.1-1 on Azure Linux 3.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl4 pcre2 10.47-1.azl4 on Azure Linux 4.0Not documented0:10.49-1.azl4Microsoft MSRC

Timeline

  1. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  2. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (4.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Advisory change

    Microsoft advisory revised (5.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  6. Advisory change

    Microsoft advisory revised (6.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  7. Advisory change

    Microsoft advisory revised (7.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  8. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references