CVE-2026-112046

Description

A flaw was found in OW2 ASM. An attacker can cause a Denial of Service (DoS) by supplying a specially crafted Java class file with methods that grow beyond 64 kilobytes during transformation. When processing this file, an offset truncation error triggers an infinite loop within the method resolution logic, causing the application reading or analyzing the class file to hang indefinitely.

Statement

This vulnerability is rated as Moderate impact because successful exploitation requires a user or build system to process an untrusted Java class file, resulting in an unrecoverable hang without compromising system confidentiality or integrity. Within Red Hat products, OW2 ASM is primarily utilized as a build-time dependency or bytecode analysis utility, limiting exposure to scenarios where untrusted compiled code is actively inspected or manipulated. The failure affects only the active processing thread or tool execution, preventing automated tasks from finishing while leaving the underlying host operating system secure.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.5N/A5.5
Attack VectorLocalN/ALocal
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionRequiredN/ARequired
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactNoneN/ANone
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

cve.org: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Amplification

An infinite loop will cause unexpected consumption of resources, such as CPU cycles or memory. The software's operation may slow down, or cause a long time to respond.

Frequently Asked Questions

Want to get errata notifications? Sign up here.