Skip to main content
CVE-2026-79650VulnerabilityPublished

Wso2am: Apache CXF’s OIDC relying-party component could redirect users to an attacker-controlled URL after successful

Affects wso2amSource GCVE Database

0
Compare
Authoritative record:CVE-2026-79650· Medium 6.1

Not known to be exploited · CVSS 6.1 Medium : upgrade to 4.7.0-r5 when convenient.

Data as of 11 Nov 2026, 04:17 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.7.0-r5
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 10 Nov 2026.

What to do

Upgrade wso2am to 4.7.0-r5.

Affected software

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

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-r5 or later, where this vulnerability is fixed. Since a patch is available, applying the official update is the recommended remediation. No additional mitigations are specified.

Description

A security vulnerability in the wso2am package affects Apache CXF’s OIDC relying-party component, which could redirect users to an attacker-controlled URL after successful authentication. This flaw is present in versions prior to 4.7.0-r5 and has a medium severity rating with a CVSS score of 6.1. The issue has been fixed in version 4.7.0-r5.

References

Community reviews

Loading reviews…