Wso2am:
Affects wso2amSource GCVE Database
Not known to be exploited · CVSS 9.1 Critical : upgrade to 4.7.0-r5 as a priority.
Data as of 11 Nov 2026, 04:04 UTC
- Patch
- Available – fixed in 4.7.0-r5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 10 Nov 2026.
What to do
Upgrade wso2am to 4.7.0-r5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
CleanStartwso2ampkg:apk/cleanstart/wso2amOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade wso2am to version 4.7.0-r5 or later, where the hostname verification issue in the Netty-based HTTP client transport has been fixed. Since a patch is available, applying this official fix is the recommended remediation.
Description
A critical security vulnerability exists in the wso2am package due to Apache CXF's Netty-based HTTP client transport not verifying that the hostname in the server's TLS certificate matches the host being called. This flaw affects versions prior to 4.7.0-r5 and can lead to high-impact confidentiality and integrity breaches. The issue has been fixed in version 4.7.0-r5.