Apache Axis2 Kernel file read and network requests via XXE in WSDL import
- Exploited
- No known exploitation
- Fix
- Fixed in 2.0.2
- Who is exposed
- Not reported
Summary
Apache Axis2/Java clients that build a service from a WSDL URL, through ServiceClient or AxisService.createClientSideAxisService, are affected by an XML external entity (XXE) injection flaw in how imported WSDL and XSD documents are parsed. An attacker who controls the WSDL or a document it imports can read local files or make the JVM issue network requests.
Written by a model
Original description
Improper Restriction of XML External Entity Reference vulnerability in Apache Axis2/Java. When a client built an AxisService from a WSDL URL, through ServiceClient or AxisService.createClientSideAxisService, wsdl4j import resolution was enabled and the documents named by wsdl:import and xsd:import were parsed by wsdl4j's own XML parser, which processes DOCTYPE declarations and external entities. An attacker who controls a WSDL, or a document it imports, could therefore read local files or make the JVM issue network requests. This issue affects Apache Axis2/Java: through 2.0.1. Users are recommended to upgrade to version 2.0.2, which fixes the issue.
What to do
Upgrade to a fixed version: 2.0.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-120761 (Apache Axis2/Java: XML External Entity (XXE) injection via imported WSDL/XSD documents), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-120761 (entry last updated 2026-11-12):
Affected:
- Maven package org.apache.axis2:axis2-kernel: fixed in 2.0.2
Fixed versions: 2.0.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-120761 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120761 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Maven): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread.html/7jw9v3qz0cdpon7fc6vsvkqp0jdt5kt0
- https://github.com/apache/axis-axis2-java-core/commit/1d3457d12399c7721ed3f52e7031d1d24d169460
- https://axis.apache.org/axis2/java/core/release-notes/2.0.2.html
- http://www.openwall.com/lists/oss-security/2026/11/06/22
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-120761
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-120761"}.Affected versions
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
- Severity10/10CVSS 9.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 85 if added to CISA KEV
- Would score about 80 if CISA's SSVC rates exploitation active
- Would score about 45 if advisories confirm default setups are exposed
Impact
- Widely used168 packages depend on org.apache.axis2:axis2-kernel. deps.dev
Timeline
- CVE published
- First seen by cve.now3 days
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
- Posted on X by cve.now
Public exploit activity
- EPSS: 0.46%
- Posted on X by cve.now Nov 12
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 2Establishes: Affected and fixed versions. | |
| Advisory | lists.apache.org · thread.html/7jw9v3qz0cdpon7fc6vsvkqp0jdt5kt0 |
| Link | axis.apache.org · axis2/java/core/release-notes/2.0.2.html |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-120761 |
| Record | NVD · CVE-2026-120761 |
| Write-ups 1Establishes: Technical detail and context. | |
| Link | openwall.com · lists/oss-security/2026/11/06/22 |
| Other links 1 | |
| Patch | GitHub · apache/axis-axis2-java-core · Commit 1d3457d1 |
Questions about CVE-2026-120761
Is CVE-2026-120761 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-120761?
org.apache.axis2:axis2-kernel (Maven): before 2.0.2.
Source: cve.now feed data
How do I fix CVE-2026-120761?
Upgrade to a fixed version: 2.0.2.
Source: cve.now feed data
Related
- CVE-2026-123753Apache Axis2/Java: SSRF via WS-Addressing ReplyTo and FaultTo endpoints
- CVE-2026-123770Apache Axis2/Java: Unbounded multipart and form-encoded request bodies
- CVE-2026-120832Apache Axis2/Java: SSRF via WSDL/XSD schema import resolution
- CVE-2026-66713Apache Axis2/Java: deserialization of untrusted Data
- CVE-2026-120367Apache Axis2/Java: unbounded JSON request body buffering
- CVE-2026-123766Apache Axis2/Java: Cross-site scripting in the OpenAPI module's Swagger UI page
No corrections so far. Something wrong on this page? Report an error.