CVE-2026-19519
Received Received - Intake

Claircore RPM Scanner Denial of Service via Unchecked Type Assertion

Publication date: 2026-08-11

Last updated on: 2026-08-11

Assigner: Red Hat, Inc.

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-11
Last Modified
2026-08-11
Generated
2026-08-11
AI Q&A
2026-08-11
EPSS Evaluated
N/A
NVD
CVE-2026-19519
EUVD
EUVD-2026-55974

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
claircore clair *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-617 The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a flaw in claircore's RPM package scanner where crafted RPM header data in a container layer triggers an unchecked type assertion. This causes the scanner to panic, crashing the Clair indexer process and leading to a denial of service.

Detection Guidance

Detecting this vulnerability requires monitoring for crashes in the Clair indexer process. Check logs for panics or unexpected terminations in scanner workloads. Commands like 'journalctl -u clair' or 'docker logs <clair-container>' may reveal crashes. Ensure scanner processes are isolated to detect failures.

Impact Analysis

The impact is a denial of service where the Clair indexer process crashes, affecting all users of the shared indexer. Attackers could exploit this by pushing malicious container images to cause system unavailability.

Compliance Impact

This vulnerability causes a denial of service by crashing the Clair indexer process, which could disrupt security scanning and monitoring. For compliance standards like GDPR or HIPAA, which require continuous monitoring and availability of security tools, such disruptions may lead to non-compliance if critical vulnerabilities are not detected or remediated in a timely manner.

Mitigation Strategies

Isolate scanner workloads in separate processes or containers to prevent a single crash from affecting the entire indexer. Deploy multiple indexer replicas behind a load balancer to reduce downtime. Upgrade to a patched version if available. Monitor for crashes and restart failed processes promptly.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-19519. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart