# CVE-2026-112046: OW2 ASM infinite loop in Label.resolve with large methods

Source: https://junglewise.ai/threats/cve-2026-112046-ow2-asm-9-11-before-9-11-1-contains-an-infinite-loop  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-18. Updated: 2026-10-18  
License: CC BY 4.0 with a link back

CVE-2026-112046 · Severity: medium · CVSS 5.5 · Published 2026-10-18

OW2 ASM is a bytecode manipulation library used by build tools, Java agents, and code analyzers. A crafted malicious class file can cause an infinite loop in the label resolution code when the transformed method bytecode exceeds 64 KB, hanging the application and denying service to build pipelines and analysis tools.

Technologies: [OW2 ASM](https://junglewise.ai/threats/technologies/asm). Vendors: [OW2](https://junglewise.ai/threats/vendors/ow2).

## Quick answers

**Is CVE-2026-112046 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-112046 being exploited in the wild.

**How severe is CVE-2026-112046?** Medium severity, with a CVSS score of 5.5, published 18 October 2026.

**Which products and versions are affected?** OW2 ASM 9.11 before 9.11.1.

**Is there a fix for CVE-2026-112046?** Yes: fixed in ASM 9.11.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-112046 attacked?** It is attacked with local access.

**Am I affected by CVE-2026-112046?** Check whether you run OW2 ASM at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in ASM 9.11.1

## Technical details

The vulnerability is a denial-of-service infinite loop in Label.resolve() caused by 16-bit forward-reference offsets truncating when rewritten methods exceed 65535 bytes. An attacker supplies a class file whose transformed code grows past this threshold, triggering ClassReader.accept() to hang indefinitely. The issue stems from storing forward references with insufficient precision for large methods.

## Affected products

- OW2 ASM 9.11 before 9.11.1

## Timeline

- 2026-10-18: disclosed

## References

- [https://repo1.maven.org/maven2/](https://repo1.maven.org/maven2/)
- [https://asm.ow2.io/versions.html](https://asm.ow2.io/versions.html)

## Related threats

- [OW2 ASM excessive resource consumption in Analyzer.analyze()](https://junglewise.ai/threats/cve-2026-110591-ow2-asm-1-4-3-before-9-11-contains-an-excessive-resource)
- [OW2 ASM uncontrolled memory allocation in JSRInlinerAdapter](https://junglewise.ai/threats/cve-2026-110270-ow2-asm-3-0-before-9-11-contains-an-uncontrolled-memory)
- [OW2 ASM quadratic memory allocation in MethodWriter](https://junglewise.ai/threats/cve-2026-110260-ow2-asm-3-0-before-9-11-contains-a-quadratic-memory-allocation)
- [OW2 ASM uncontrolled recursion in ClassWriter](https://junglewise.ai/threats/cve-2026-110259-ow2-asm-3-0-before-9-11-contains-an-uncontrolled-recursion)
