GHSA-6qx5-4pcm-5fgh
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSend oversized multipart/form-data request to Axis2 endpoint
-
ExploitBuilder reads body from transport with no size limit
-
ExecutionHeap fills and temp files accumulate on disk
-
ImpactResource exhaustion denies service
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource allocation limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an Axis2/Java endpoint (version through 2.0.1) that accepts and processes multipart/form-data or application/x-www-form-urlencoded request bodies via the affected message builders - the default behavior, since these builders read the body directly from the transport stream and the servlet container's post-size limit does not apply. No authentication, user interaction, or non-default configuration is needed (AV:N/AC:L/PR:N/UI:N). The main limiting factor is impact scope: this is availability-only (no data exposure or modification), and the endpoint must be network-reachable; prior to 2.0.2 there was no configurable limit to cap the body, so patched/limit-configured deployments are not affected. |
| Impact | Signals are largely consistent and point to a genuine but non-emergency availability issue. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5) describes a network-reachable, low-complexity, unauthenticated flaw whose only impact is availability (C:N/I:N/A:H) - i.e. a pure denial-of-service, matching CWE-770 and the 'Denial Of Service' tag. Counterbalancing this, EPSS is low at 0.24% (15th percentile), the CVE is not listed in CISA KEV, and no public exploit is identified, so there is no evidence of active or widespread exploitation; the vuln.today decision label is 'this_week' rather than act_now/emergency. Net: a real priority to patch but not a drop-everything event - the easy, unauthenticated reachability is offset by DoS-only impact and low real-world exploitation probability. One caveat on data integrity: the attached GitHub commit diff (ResponseEndpointPolicy / WS-Addressing ReplyTo-FaultTo handling) describes an SSRF-style response-endpoint restriction and does NOT correspond to the resource-exhaustion fix in the description - the mechanism here is taken from the Apache advisory text, not from that mismatched code evidence. |
| Exploit ScenarioDerived | An unauthenticated attacker sends large or repeated multipart/form-data or application/x-www-form-urlencoded requests to an exposed Apache Axis2/Java endpoint. Because the message builders read the request body straight from the transport stream with no size limit (bypassing the servlet container's post-size limit) and never delete multipart temporary files, the attacker drives the server to exhaust heap memory or fill disk, denying service to legitimate users. No public exploit was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Nov 12, 2026
Memory and disk exhaustion in Apache Axis2/Java through 2.0.1 allows remote, unauthenticated callers to drain server resources by submitting oversized multipart/form-data or application/x-www-form-urlencoded request bodies. The affected message builders read the body directly from the transport stream, so the servlet container's post-size limit never applies, and multipart temporary files are left on disk rather than deleted; availability is the only impacted property (CVSS 3.1: 7.5, AV:N/AC:L/PR:N/UI:N/C:N/I:N/A:H). Any network-reachable Axis2 endpoint that processes these content types in its default configuration is exposed, though EPSS is low at 0.24% (15th percentile) and no public exploit code has been identified at the time of analysis; the vendor fix is Apache Axis2/Java 2.0.2.
Earlier versions of this analysis (1)
Memory and disk exhaustion in Apache Axis2/Java 2.0.1 and earlier is reachable by any caller who can POST to an exposed service endpoint, because the multipart/form-data and application/x-www-form-urlencoded message builders read the request body straight from the transport stream without any size cap and without the servlet container's configured post-size limit applying; the multipart path additionally left temporary files undeleted. The assessed CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L - availability-only impact, no disclosure or code execution - and while the advisory describes the caller as unauthenticated, no CVSS vector was supplied with the CVE record itself to confirm the privilege requirement. No CISA KEV entry, no confirmed exploit, no EPSS score and no public PoC are present in the supplied intelligence, and the vuln.today decision label is 'awaiting_data'. Version 2.0.2 bounds these bodies with configurable limits and deletes temporary files.
RemediationAI
Upgrade to Apache Axis2/Java 2.0.2, which introduces configurable limits on multipart/form-data and application/x-www-form-urlencoded bodies and deletes multipart temporary files after processing; this is the remedy the vendor recommends, and the release notes at https://axis.apache.org/axis2/java/core/release-notes/2.0.2.html document the new configuration. The upstream changes are referenced as commits https://github.com/apache/axis-axis2-java-core/commit/1671a68660df39459bf22f7b00309e2a8e782117, https://github.com/apache/axis-axis2-java-core/commit/2b98e5a31c793589915711f5e29fb4ffb697de70 and https://github.com/apache/axis-axis2-java-core/commit/94c935d1406bc0875daebd36994595efa2f48ae0, with the announcement at https://seclists.org/oss-sec/2026/q4/559 and an additional write-up at https://vuldb.com/vuln/432065. Versions through 2.0.1 expose no in-product limit that can cap these builders - the servlet container's post-size setting did not apply to them - so the advisory's remediation is the upgrade itself rather than a configuration change on the existing release; code changes to the WS-Addressing response-endpoint handling seen in the referenced commits are a separate hardening item and do not substitute for the body-size fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-770 (Allocation of Resources Without Limits or Throttling). Axis2's multipart/form-data and application/x-www-form-urlencoded message builders consume the inbound payload straight from the transport input stream rather than through a container-managed, size-capped buffer, which is why the servlet container's post-size setting had no effect on these requests. Each request can therefore force the server to buffer an arbitrarily large body in heap, and multipart requests additionally leave temporary files behind that are never cleaned up, so repeated traffic accumulates both memory pressure and disk consumption. The CVSS vector's AC:L and PR:N/UI:N are descriptive of severity only: the supplied evidence does not describe any special race, timing or grooming precondition, and once an endpoint is reachable the trigger is simply a large or repeated submission of these content types. Impact is availability-only (A:H, with C:N/I:N), and 2.0.2 introduces configurable limits on these bodies plus deletion of multipart temporary files. One caution when reading the patch refs: the diff surfaced for the referenced upstream commits modifies WS-Addressing handling (a ResponseEndpointPolicy that rejects non-anonymous ReplyTo/FaultTo destinations resolving to loopback, link-local, site-local/RFC-1918 or wildcard addresses) and does not itself show the body-size limiting, so the size-cap and temp-file changes should be confirmed against the 2.0.2 release notes rather than inferred from that diff.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Unauthenticated network request with no user interaction triggers unbounded body reads and undeleted temp files, so PR:N/AC:L and availability-only impact (A:H, C:N/I:N).
Primary rating from Vendor (CNA).
CVSS VectorVendor
Lifecycle Timeline
4Description PRE-NVD
Articles & Coverage 2
Executive ViewAI
Apache Axis2/Java, a widely used web services framework, contains a high-severity flaw (CVE-2026-123770) that allows unauthenticated remote attackers to exhaust server memory and disk resources via oversized request bodies. This can lead to service outages or degraded performance for any organization running an affected Axis2 endpoint, directly impacting availability and potentially disrupting business operations. Leadership should prioritize patching to prevent denial-of-service incidents.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
EUVD-2026-119934
NVD
CVE.org
EPSS
VulDB
Exploit-DB