Medium [CVE-2026-19519] denial of service via unchecked type assertion in RPM header parser
This medium-severity Red Hat Linux advisory covers CVE-2026-19519 affecting Red Hat Advanced Cluster Security 4, Red Hat Quay 3.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
A flaw was found in claircore's RPM package scanner. Crafted RPM header data in a container layer can cause an unchecked type assertion to panic the scanner.
The panic is not recovered, causing the Clair indexer process to crash, leading to a denial of service. Red Hat Quay Clair and RHACS Scanner V4 deployments run the indexer as multiple OpenShift pods (default replica count >= 2) with automatic kubelet restart on crash.
An unrecovered panic in claircore RPM header parsing terminates one indexer pod; the remaining replicas and automatic pod restart limit the impact to a temporary interruption of image indexing rather than a lasting registry or scanning outage.
Availability impact is therefore Low (A:L), consistent with the precedent claircore panic-DoS flaw CVE-2026-16254 (apk parser out-of-bounds slice), which received the same CVSS vector and score. Red Hat severity: Moderate — CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L).
Weakness: CWE-617. Affected Red Hat products: Red Hat Advanced Cluster Security 4; Red Hat Quay 3.
Red Hat does not currently list a fixing RHSA for this CVE.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 2 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 2 days ago·verify at source
Mitigation checklist
- Where possible, configure the indexer to run scanner workloads in isolated processes or containers so that a single scanner panic cannot terminate the shared indexer. Alternatively, deploy multiple indexer replicas behind a load balancer to reduce the blast radius of a single-process crash.
Official advisory · high-confidence parse· fetched 2 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.