Apache Axis2/Java: unbounded JSON request body buffering
- Exploited
- No known exploitation
- Fix
- Fixed in 2.0.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.0.2.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 38/100 · provisional
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- Low (apache)
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
Apache Axis2/Java's JSON message builders (Gson, Moshi, and HTTP/2 variants) buffer entire request bodies without any size limit, so an unauthenticated remote caller could exhaust server memory with a large JSON request. The issue is fixed in a later release, which adds a configurable limit on JSON request body size.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Allocation of Resources Without Limits or Throttling vulnerability in Apache Axis2/Java. The JSON message builders, including the Gson, Moshi and HTTP/2 variants, buffered the entire request body with no size limit, so an unauthenticated caller could exhaust server memory with a large JSON request. Version 2.0.2 bounds JSON request bodies with the configurable jsonMaxRequestSize parameter. This issue affects Apache Axis2/Java: through 2.0.1. Users are recommended to upgrade to version 2.0.2, which fixes the issue.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach10/20Affects Maven packages
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 83 if added to CISA KEV
- Would score about 78 if CISA's SSVC rates exploitation active
- Would score about 43 if advisories confirm default setups are exposed
Impact
- Widely used
22 packages depend on org.apache.axis2:axis2-json.Source: deps.dev
What to do
Upgrade to a fixed version: 2.0.2.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
fixed in 2.0.2
Fixed in 2.0.2 (released Oct 29, 2026, 11 days before disclosure).
The latest release, 2.0.2, is not affected.
Evidence 4
- Advisory
- Patch
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120367
Is CVE-2026-120367 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-120367?
org.apache.axis2:axis2-json (Maven): before 2.0.2.Source: cve.now feed data
How do I fix CVE-2026-120367?
Upgrade to a fixed version: 2.0.2.Source: cve.now feed data
Why is it rated 7.5 High?
CVSS 7.5 scores the worst case. apache rates it Low.