SQLite often runs inside an application that never exposes a database port. If an Azure Linux 3.0 application opens imported databases or evaluates untrusted SQL, check which SQLite library it actually loads.

What changed on November 22, 2026
Microsoft added 3.44.0-5 to the Azure Linux 3.0 fix matrix on November 21 for the listed affected package 3.44.0-4. The initial MSRC entries date to October 31 UTC. On November 22, both production base repositories served sqlite 3.44.0-5.azl3 for x86-64 and ARM64. Both RPMs matched their repository SHA-256 checksums. The Microsoft mapping and supported repository establish the Azure Linux backport path. The upstream SQLite fix is 3.54.0, released October 9.
Where the update applies
Microsoft rates CVE-2026-119373 and CVE-2026-119374 Important, CVSS 3.1 7.8. Those bugs affect FTS5 processing when the feature is present and a consumer handles untrusted input. The other mapped issues are CVE-2026-119371, CVE-2026-119372, CVE-2026-119375, CVE-2026-119376, CVE-2026-119377, CVE-2026-119378 and CVE-2026-119591. They cover denial of service, information disclosure or a SQLite authorizer bypass under specific conditions, with Azure Linux 3.0 CVSS 3.1 scores of 5.5 for six and 2.5 for CVE-2026-119377. Applicability depends on the code path, enabled features and who controls the inputs. The named Azure Linux 3.0 affected build does not establish complete older bounds.
No CVE in this group was listed in CISA KEV on November 22. Confirmed malicious exploitation, a federal KEV deadline and vendor-directed incident-response steps were not verified. The Azure Linux 4.0 SQLite rows for seven CVEs and the separate libdb row for CVE-2026-119378 still have blank fix fields in the reviewed Microsoft matrix. Track their supported fixes separately.
What I would do across customer environments
Suggested MSP priority: High for affected applications that accept untrusted SQLite files or SQL, particularly those using FTS5. Prioritize other deployments through normal patch triage.
- Inventory the OS and installed package and identify the library each running application loads. Include containers and statically linked applications in that check.
- Restrict unnecessary untrusted database imports or SQL inputs while affected consumers await rollout. Preserve expected application workflows.
- Pilot the supported Azure Linux 3.0 production update. Restart or redeploy affected consumers and update separately bundled copies through their own supported release.
- Verify the running library and exercise ordinary database and search workflows. Track container images, AKS node images and managed services separately.
Official sources
Last verified November 22, 2026 ET. Microsoft October CVRF · SQLite vulnerability and release notes · Microsoft x86-64 repository metadata · Microsoft ARM64 repository metadata · CISA KEV data.