Skip to main content
VulnerabilityPublished

CVE-2026-107937: Wso2am · In Apache CXF, the parser for multipart/MTOM attachment part headers did not fully enforce

Affects wso2amSource GCVE Database

0
Compare
Authoritative record:CVE-2026-107937· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 4.7.0-r4 soon.

Data as of 13 Nov 2026, 01:27 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.7.0-r4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.

What to do

Upgrade wso2am to 4.7.0-r4.

Affected software

ProductAffectedFixed in
CleanStartwso2ampkg:apk/cleanstart/wso2amOther threatsAffected
  • <4.7.0-r4
Fixed in
  • 4.7.0-r4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and the issue is fixed in wso2am version 4.7.0-r4. Users should upgrade to this version to remediate the vulnerability.

Description

A security vulnerability in the wso2am package affects Apache CXF's parser for multipart/MTOM attachment part headers. The parser did not fully enforce configured limits on attachment header size and count, potentially leading to denial of service. This issue is fixed in version 4.7.0-r4. The vulnerability has a high severity score of 7.5 and does not impact confidentiality or integrity but affects availability.

References

Community reviews

Loading reviews…