Is CVE-2026-110591 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-110591 being exploited in the wild.

How severe is CVE-2026-110591?

Medium severity, with a CVSS score of 5.5, published 14 October 2026.

Is there a fix for CVE-2026-110591?

Yes: fixed in ASM 9.11. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-110591 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-110591?

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.

CVE-2026-110591: OW2 ASM excessive resource consumption in Analyzer.analyze()

CVE-2026-110591 · Severity: medium · CVSS 5.5 · Published 2026-10-14

OW2 ASM is a bytecode manipulation library used in Java applications to read, generate, and transform compiled Java code. An attacker can supply malformed class files that cause the Analyzer to consume unbounded memory and CPU, triggering denial of service. Affected applications that use ASM to analyze untrusted bytecode are vulnerable to crashes and service unavailability.

Technologies: OW2 ASM. Vendors: OW2.

Quick answers

Is CVE-2026-110591 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-110591 being exploited in the wild.
How severe is CVE-2026-110591?: Medium severity, with a CVSS score of 5.5, published 14 October 2026.
Which products and versions are affected?: OW2 ASM before 9.11.
Is there a fix for CVE-2026-110591?: Yes: fixed in ASM 9.11. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-110591 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-110591?: 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

Technical details

The vulnerability exists in Analyzer.analyze() when processing crafted class files through BasicVerifier, SimpleVerifier, or SourceInterpreter. The flaw is an excessive resource consumption (denial of service) triggered by unbounded per-instruction Frame allocation and fix point iterations. The fix in ASM 9.11 adds resource control APIs (issue !468) to limit the resources consumed by Analyzer.

Affected products

OW2 ASM before 9.11

Timeline

2026-10-14: disclosed
2026-10-04: patched: ASM 9.11 released with resource control APIs

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.