Quick answers
- Is CVE-2026-47424 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47424 being exploited in the wild.
- How severe is CVE-2026-47424?
- High severity, with a CVSS score of 4, published 15 September 2026.
- Which products and versions are affected?
- org.openidentityplatform.openam:openam-scripting (Maven) <= 16.0.6, ECOSYSTEM:introduced=0,fixed=16.1.1; Open Identity Platform OpenAM Community Edition <= 16.0.6.
- Is there a fix for CVE-2026-47424?
- Yes. org.openidentityplatform.openam:openam-scripting (Maven): upgrade to 16.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47424 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-47424?
- Check whether you run org.openidentityplatform.openam:openam-scripting (Maven) or Open Identity Platform OpenAM Community Edition at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- org.openidentityplatform.openam:openam-scripting (Maven): upgrade to 16.1.1 or later
# set org.openidentityplatform.openam:openam-scripting to 16.1.1 in your pom.xml or build.gradle
Technical details
A Protection Mechanism Failure (CWE-693) exists in the OpenAM server-side scripting sandbox. The vulnerability stems from insufficient class allow and deny lists, which allow an authenticated user with script-authoring privileges (such as a Realm Admin) to escape the Groovy sandbox. By crafting a malicious script, an attacker can execute arbitrary operating system commands within the context of the OpenAM JVM. This bypasses the intended administrative boundaries between sub-realms and the host system. The issue is fixed in OpenAM Community Edition version 16.1.1.
Affected products
- OpenIdentityPlatform OpenAM Community Edition <= 16.0.6
Identifiers
- CVE-2026-47424
- GHSA-69j4-qvqr-hpw3
Timeline
- 2026-06-27: disclosed
- 2026-06-29: advisory: GitHub Advisory published