CVE-2026-16254
Received Received - Intake

Out-of-Bounds Access in Claircore APK Scanner Causes DoS

Vulnerability report for CVE-2026-16254, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-20

Last updated on: 2026-07-20

Assigner: Red Hat, Inc.

Description

A flaw was found in claircore's apk package scanner. Malformed package-database data in a container layer can cause an out-of-bounds access that panics the scanner. If that panic is not recovered, the Clair indexer process can crash, leading to a denial of service.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-20
Last Modified
2026-07-20
Generated
2026-07-21
AI Q&A
2026-07-20
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
claircore apk_package_scanner *
claircore apk_package_scanner to 2502701 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-125 The product reads data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a denial-of-service flaw in claircore's apk package scanner. It occurs when malformed package-database data in a container layer causes an out-of-bounds access, leading the scanner to panic. If the panic is not recovered, the Clair indexer process crashes, resulting in a denial of service.

Detection Guidance

Detecting this vulnerability requires monitoring Clair indexer logs for crashes during container image indexing. Check for panic errors in logs when processing apk package databases. Use commands like 'kubectl logs <clair-pod>' or 'journalctl -u clair' to inspect logs for unhandled panics.

Impact Analysis

An attacker who submits a crafted image layer for indexing could exploit this to crash the Clair indexer. In long-lived setups, this may cause sustained outages until manual recovery. In typical Quay/Clair deployments on Kubernetes, the pod may crash but restart automatically, causing brief interruptions rather than prolonged downtime.

Compliance Impact

This vulnerability primarily causes a denial of service by crashing the Clair indexer process, which may lead to temporary unavailability of vulnerability scanning for container images. For compliance standards like GDPR or HIPAA, which require availability and integrity of systems processing sensitive data, this could result in brief disruptions in security monitoring. However, the impact is typically limited to short outages due to automatic pod restarts in Kubernetes environments, reducing long-term compliance risks.

Mitigation Strategies

Apply patches or updates to Clair and claircore to fix the apk scanner flaw. If immediate patching is not possible, restrict untrusted users from submitting container images for indexing. Monitor indexer health and ensure automatic pod restarts are configured to minimize downtime.

Chat Assistant

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

EPSS Chart