Skip to main content
VulnerabilityPublished

CVE-2026-123770: Allocation of Resources Without Limits or Throttling vulnerability in Apache Axis2/Java

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-123770· High

Not known to be exploited : upgrade to 2.0.2 soon.

Data as of 9 Nov 2026, 13:05 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 2.0.2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Upgrade Apache Axis2/Java and org.apache.axis2/axis2-kernel to 2.0.2.

Affected software

ProductAffectedFixed in
Apache Axis2/Javaorg.apache.axis2:axis2-kernelAffected
  • <2.0.2
Fixed in
  • 2.0.2
Mavenorg.apache.axis2/axis2-kernelpkg:maven/org.apache.axis2/axis2-kernelOther threatsAffected
  • <2.0.2
Fixed in
  • 2.0.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade to Apache Axis2/Java version 2.0.2 or later, which includes configurable limits on request body sizes and proper deletion of temporary files, effectively mitigating this vulnerability.

Description

Apache Axis2/Java versions through 2.0.1 have a resource allocation vulnerability where multipart/form-data and application/x-www-form-urlencoded message builders do not limit request body size, bypassing servlet container post-size limits and failing to delete temporary files. This allows unauthenticated attackers to exhaust memory or disk resources. The issue is fixed in version 2.0.2 by adding configurable size limits and proper cleanup of temporary files.

References

Community reviews

Loading reviews…