CVE-2026-97791VulnerabilityPublished 13 Nov 2026

Wso2am:

Affects wso2amSource GCVE Database

Compare

Authoritative record:CVE-2026-97791· 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.3% chance of exploitation in 30 days – higher than 23% 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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade wso2am to 4.7.0-r4.

Affected software

Product	Affected	Fixed in
CleanStartwso2am`pkg:apk/cleanstart/wso2am`Other threats	Affected <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

Upgrade affected installations of wso2am to version 4.7.0-r4 or later, where the vulnerability is fixed. Since a patch is available, applying the official fix is the recommended remediation. No additional mitigations are specified.

Description

A security vulnerability in the wso2am package involves Apache CXF's STSTokenValidator, which improperly checks whether a SAML assertion is signed by a trusted certificate before sending it to the Security Token Service (STS). This flaw affects versions prior to 4.7.0-r4 and has been assigned CVE-2026-97791. The vulnerability has a high severity with a CVSS score of 7.5, primarily impacting availability. A patch is available in version 4.7.0-r4.

Impact

The vulnerability impacts availability, potentially allowing an attacker to disrupt service by exploiting improper validation of SAML assertions. There is no reported impact on confidentiality or integrity. No known exploits are currently in the wild.

Summary

The vulnerability in wso2am (CVE-2026-97791) arises from Apache CXF's STSTokenValidator component that validates SAML assertions. The validator checks if a SAML assertion is signed by a trusted certificate before forwarding it to the STS. Versions before 4.7.0-r4 are affected. The flaw can lead to denial of service conditions (availability impact) without compromising confidentiality or integrity. The issue has been addressed in version 4.7.0-r4, where the validation logic is corrected or improved.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2026, 01:20 UTC

Technical details

References

Community reviews

Related threats