How severe is CVE-2024-12369?

CVE-2024-12369 has a CVSS score of 4.2/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-12369?

CVE-2024-12369 affects the following packages: org.wildfly.security:wildfly-elytron (Maven), org.wildfly.security:wildfly-elytron (Maven), org.wildfly.security:wildfly-elytron-http-oidc (Maven), org.wildfly.security:wildfly-elytron-http-oidc (Maven). Ecosystems affected: Maven.

How do I fix CVE-2024-12369?

Update org.wildfly.security:wildfly-elytron to 2.2.9.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-12369 is resolved across your whole dependency graph.

How do I detect CVE-2024-12369 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wildfly.security:wildfly-elytron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-12369 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2024-12369 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-12369 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-12369?

CVE-2024-12369 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 16th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-12369?

CVE-2024-12369 is classified as CWE-345 (CWE-345). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-12369 published, and has it been updated?

CVE-2024-12369 was published on December 9, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2024-12369 — wildfly-elytron

MEDIUMFix: wildfly-security/wildfly-elytron@5ac5e6b

CVE-2024-12369 is a medium-severity (CVSS 4.2) CWE-345 vulnerability in org.wildfly.security:wildfly-elytron. A fix is available for org.wildfly.security:wildfly-elytron — see the affected versions and patch details below.

Elytron-oidc-client: oidc authorization code injection

Also known asGHSA-5565-3c98-g6jc

Published

Dec 9, 2024

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-12369.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs16th percentile — riskier than 16% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

☕org.wildfly.security:wildfly-elytron☕org.wildfly.security:wildfly-elytron☕org.wildfly.security:wildfly-elytron-http-oidc☕org.wildfly.security:wildfly-elytron-http-oidc

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A vulnerability was found in OIDC-Client. When using the elytron-oidc-client subsystem with WildFly, authorization code injection attacks can occur, allowing an attacker to inject a stolen authorization code into the attacker's own session with the client with a victim's identity. This is usually done with a Man-in-the-Middle (MitM) or phishing attack.

Patches

2.2.9.Final 2.6.2.Final

Workarounds

Currently, no mitigation is currently available for this vulnerability.

References

https://nvd.nist.gov/vuln/detail/CVE-2024-12369 https://access.redhat.com/security/cve/CVE-2024-12369 https://bugzilla.redhat.com/show_bug.cgi?id=2331178 https://issues.redhat.com/browse/ELY-2887

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.wildfly.security:wildfly-elytron`	≥ 1.17.0.Final&&< 2.2.9.Final	2.2.9.Final`org.wildfly.security:wildfly-elytron:2.2.9.Final`
☕Maven	`org.wildfly.security:wildfly-elytron`	≥ 2.3.0.Final&&< 2.6.2.Final	2.6.2.Final`org.wildfly.security:wildfly-elytron:2.6.2.Final`
☕Maven	`org.wildfly.security:wildfly-elytron-http-oidc`	≥ 1.17.0.Final&&< 2.2.9.Final	2.2.9.Final`org.wildfly.security:wildfly-elytron-http-oidc:2.2.9.Final`
☕Maven	`org.wildfly.security:wildfly-elytron-http-oidc`	≥ 2.3.0.Final&&< 2.6.2.Final	2.6.2.Final`org.wildfly.security:wildfly-elytron-http-oidc:2.6.2.Final`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wildfly.security:wildfly-elytron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.wildfly.security:wildfly-elytron to 2.2.9.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-12369 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat has evaluated this vulnerability. This affects the OIDC Client when using RHSSO OIDC Adapter with EAP 7.x or elytron-oidc-client with EAP 8.x.

Workaround published by Red Hat

Currently, no mitigation is currently available for this vulnerability.

Source: Red Hat security advisory for CVE-2024-12369 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat JBoss Enterprise Application Platform 8	`org.wildfly/wildfly-elytron-oidc-client-subsystem`	RHSA-2025:3992
Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 8	`eap8-apache-commons-io-0:2.16.1-1.redhat_00001.1.el8eap`	RHSA-2025:3989

Frequently Asked Questions

### Impact A vulnerability was found in OIDC-Client. When using the elytron-oidc-client subsystem with WildFly, authorization code injection attacks can occur, allowing an attacker to inject a stolen authorization code into the attacker's own session with the client with a victim's identity. This is usually done with a Man-in-the-Middle (MitM) or phishing attack. ### Patches [2.2.9.Final](https://github.com/wildfly-security/wildfly-elytron/releases/tag/2.2.9.Final) [2.6.2.Final](https://github.com/wildfly-security/wildfly-elytron/releases/tag/2.6.2.Final) ### Workarounds Currently, no mit