CVE-2026-110259

Description

A flaw was found in OW2 ASM. This vulnerability allows an attacker to cause a Denial of Service (DoS) by supplying a specially crafted Java class file containing a large method with numerous forward jump instructions. Processing this file triggers excessive recursive calls during bytecode transformation, resulting in an application crash due to a stack overflow.

Statement

This vulnerability is rated as having a Moderate severity because exploitation requires an application or build pipeline to process an untrusted compiled Java class, resulting strictly in a denial of service without compromising system confidentiality or integrity. In Red Hat environments, OW2 ASM is utilized internally by application servers, runtime instrumentation frameworks, and development tooling. Under standard deployments, these tools process trusted artifacts, meaning exploitation requires an attacker to convince a user or service to ingest an untrusted bytecode payload, limiting the practical threat landscape.

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

The following CVSS metrics and score provided are preliminary and subject to review.

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: Resource Consumption (Other)

When allocating resources without limits, an attacker could prevent other systems, applications, or processes from accessing the same type of resource. It can be easy for an attacker to consume many resources by rapidly making many requests or causing larger resources to be used than is needed.

Frequently Asked Questions

Want to get errata notifications? Sign up here.