Wso2am:
Affects wso2amSource GCVE Database
Not known to be exploited · CVSS 9.1 Critical : upgrade to 4.7.0-r4 as a priority.
Data as of 13 Nov 2026, 01:27 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% 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: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 12 Nov 2026.
What to do
Upgrade wso2am to 4.7.0-r4.
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-r4 or later, where the hostname verification issue in the Netty-based HTTP client transport is fixed. Since a patch is available, applying this official fix is the recommended mitigation.
Description
A critical security vulnerability in the wso2am package affects versions prior to 4.7.0-r4. The issue lies in Apache CXF's Netty-based HTTP client transport, which fails to verify that the hostname in the server's TLS certificate matches the host being called. This flaw can lead to severe confidentiality and integrity impacts. A fix is available in version 4.7.0-r4.