GHSA-78w3-p65q-wwh7
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach JSON-enabled Axis2 endpoint
-
ExploitSend oversized JSON request body
-
ExecutionBuilder buffers entire body unbounded
-
ImpactExhaust server heap, denial of 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 | The deployment must expose a service that accepts JSON requests handled by the axis2-json module - specifically the Gson JsonBuilder, the Moshi variant, or the HTTP/2 EnhancedGsonJsonBuilder - since the unbounded buffering occurs in those JSON message builders; endpoints that only accept SOAP/POX or multipart were already bounded by other limits. The affected software is Apache Axis2/Java through 2.0.1. Limiting factors: exploitation is confined to JSON-accepting endpoints, and in 2.0.2 the new jsonMaxRequestSize parameter (default 100 MB, or -1 to restore unbounded behaviour, settable per service) caps the body so the issue no longer applies on patched/default-configured installs. The advisory states the caller is unauthenticated, but no CVSS vector was provided to confirm authentication requirements independently. |
| Impact | This is a resource-exhaustion (availability-only) denial-of-service issue in Apache Axis2/Java's JSON message builders. Key decision signals are largely absent: no CVSS vector or base score is provided (input shows N/A), no EPSS probability is supplied, the issue is not in CISA KEV, and no SSVC technical-impact/automatable fields are given - the vuln.today Decision label is 'awaiting_data', meaning prioritization data is incomplete. Exploitation status: no public exploit identified at time of analysis (the only code reference is the vendor's fix commit, which is a patch, not exploit code). The vendor assigned an overall severity of 'low', which sits in tension with the mechanism described - an unauthenticated, remote, single-request memory-exhaustion DoS would ordinarily score higher on availability (my independent assessment is AV:N/A:H ≈ 7.5); the vendor's 'low' likely reflects that impact is a transient/recoverable DoS with no confidentiality or integrity loss and that a default ceiling now exists. Treat this as a genuine but bounded availability concern rather than a top-tier emergency: it is patchable, affects only JSON-accepting deployments, and carries no data-exposure or code-execution impact. Verify severity directly with the Apache advisory, as no CVSS vector was supplied to reconcile the 'low' label against the described unauthenticated remote vector. |
| Exploit ScenarioDerived | An attacker who can reach an Axis2/Java endpoint that accepts JSON (via the Gson, Moshi, or HTTP/2 Gson builders in axis2-json) sends a single very large JSON request body. Because the builder buffers the entire body into memory with no size limit prior to 2.0.2, the server's heap is exhausted, causing an OutOfMemory condition and denial of service. No public exploit code is identified; the described mechanism (one oversized request) implies low attack complexity, but the exact trigger beyond 'large JSON body' is not elaborated in the sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 06, 2026
Apache Axis2/Java through 2.0.1 buffers JSON request bodies without any size ceiling, so an unauthenticated remote caller can send an oversized JSON payload and drive the server into memory exhaustion, producing a denial of service (availability-only impact, rated low severity by the project). The flaw lives in the axis2-json message builders - the Gson JsonBuilder, the Moshi variant and the HTTP/2 EnhancedGsonJsonBuilder - with the newest assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Version 2.0.2 introduces the configurable jsonMaxRequestSize ceiling (default 100 MB) that bounds every JSON builder; no public exploit code has been identified at time of analysis and the issue is not in CISA KEV.
RemediationAI
Upgrade to Apache Axis2/Java 2.0.2, which adds the jsonMaxRequestSize ceiling (default 100 MB) to every builder in axis2-json and rejects over-sized JSON bodies instead of allocating them; the advisory points to https://axis.apache.org/axis2/java/core/release-notes/2.0.2.html for the full change set. Because the parameter is new in 2.0.2, no vendor-documented pre-2.0.2 knob limits these bodies, so the upgrade is the fix. Plan the upgrade as a behavioural migration rather than a drop-in jar swap: 2.0.2 also refuses decoupled non-anonymous WS-Addressing replies unless allowNonAnonymousResponseEndpoints is set to true (and deployments re-enabling it should also set httpFrontendHostUrl so generated reply addresses do not default to the local machine IP), turns off SOAP-body-namespace service dispatch unless allowContentBasedServiceDispatch is true, and ships the admin console disabled with empty credentials until userName and password are configured in axis2.xml. Operators who legitimately handle larger JSON messages can raise jsonMaxRequestSize per service; setting it to -1 restores the previous unbounded behaviour and reintroduces the denial-of-service exposure, so it should not be used on internet-facing services. Additional packaging notes for WAR deployments: axis2-spring no longer exports Spring, and the JMS and mail transports are no longer bundled in axis2.war.
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
Apache Axis2/Java is a SOAP/WSDL web services engine, and its axis2-json module lets deployments accept JSON payloads alongside SOAP. The advisory classifies the root cause as Allocation of Resources Without Limits or Throttling (the CWE family commonly tracked as CWE-770, though no CWE identifier was supplied in the record). Concretely, AbstractJSONDataSource materialises the entire transport stream into a single String via getJSONString(), and AbstractJSONOMBuilder plus the Gson (JsonBuilder) and gsonh2 (EnhancedGsonJsonBuilder) builders handed the raw transport InputStream straight to that buffering path. The fix commit aea2671e adds a BoundedInputStream import to those builders and wraps the incoming stream with RequestSizeLimits.resolve(messageContext, JSON_MAX_REQUEST_SIZE, DEFAULT_JSON_MAX_REQUEST_SIZE), mirroring what SOAPBuilder already did for SOAP/POX bodies; it also preserves the underlying cause when an over-sized body raises an OMException, and the gsonh2 builder notes that its payload-size strategy only chose a code path and bounded nothing. The release notes for 2.0.2 place jsonMaxRequestSize (100 MB default, settable per service, -1 restoring unbounded behaviour) alongside the existing multipartMaxRequestSize, multipartMaxFileSize, formUrlEncodedMaxRequestSize, mtomMaxRequestSize, soapMaxRequestSize and multiref maxDepth ceilings. Only the Java implementation is in scope; Apache Axis2/C is a separate codebase and is not named as affected.
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
Advisory describes a single oversized JSON request from an unauthenticated remote caller (AV:N/AC:L/PR:N/UI:N) causing memory-exhaustion DoS, so availability-only impact (A:H; C:N/I:N).
Primary rating from Vendor (CNA).
CVSS VectorVendor
Lifecycle Timeline
3Description PRE-NVD
Articles & Coverage 2
Executive ViewAI
CVE-2026-120367 is a high-severity denial-of-service vulnerability in Apache Axis2/Java that allows unauthenticated attackers to exhaust server memory via oversized JSON payloads, disrupting availability of services built on this framework. Organizations relying on Axis2 for web services or APIs are directly affected, and while no public exploit code exists, the low attack complexity and remote exploitability make it a credible threat that could lead to service outages and reputational damage.
No vendor-released patch identified at time of analysis. Interim mitigations include enforcing HTTP request body size limits at the network perimeter (e.g., reverse proxy or WAF rules), rate limiting JSON endpoints, and monitoring server memory usage for anomalies to detect and throttle abusive requests. Apply vendor patch when available.
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-119980
NVD
CVE.org
EPSS
VulDB
Exploit-DB