# CVE-2026-120367: Apache Axis2/Java: unbounded JSON request body buffering


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-78w3-p65q-wwh7

## What is CVE-2026-120367?

CVE-2026-120367 is a high-severity vulnerability in Apache Axis2/Java, published on 9 Nov 2026. 

### Official 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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-120367?


## How do I fix CVE-2026-120367?

No fix has been published for CVE-2026-120367 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120367 being exploited?

There is no known exploitation of CVE-2026-120367 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120367 and fix it if it is affected.

What it is: CVE-2026-120367 is a high-severity vulnerability in Apache Axis2/Java, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120367 in the wild and no public exploit code.

Affected product: Apache Axis2/Java. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120367/ (Markdown: https://insights.sbomify.com/CVE-2026-120367/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120367
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120367
- OSV: https://osv.dev/vulnerability/CVE-2026-120367

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120367/
Summaries are generated and may contain mistakes; the official description above is the record.
