Wso2am: max_age authentication-freshness check
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.3% chance of exploitation in 30 days – higher than 29% 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 max_age authentication-freshness check issue is fixed. Since a patch is available, applying this official fix is the recommended remediation.
Description
A critical security vulnerability in wso2am versions prior to 4.7.0-r4 causes the max_age authentication-freshness check in OidcClientCodeRequestFilter to be ineffective due to a unit mismatch and inverted comparison logic. This flaw allows attackers to bypass the intended freshness check of authentication tokens.