CVE-2022-0866

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2022-05-11. NVD baseline CVSS 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 5.3Exploit: NoneExposed: 0

A fix is available — apply it.

This is a concurrency issue that can result in the wrong caller principal being returned from the session context of an EJB that is configured with a RunAs principal. In particular, the org.jboss.as.ejb3.component.EJBComponent class has an incomingRunAsIdentity field. This field is used by the org.jboss.as.ejb3.security.RunAsPrincipalInterceptor to keep track of the current identity prior to switching to a new identity created using the RunAs principal. The exploit consist that the EJBComponent#incomingRunAsIdentity field is currently just a SecurityIdentity. This means in a concurrent environment, where multiple users are repeatedly invoking an EJB that is configured with a RunAs principal, it's possible for the wrong the caller principal to be returned from EJBComponent#getCallerPrincipal. Similarly, it's also possible for EJBComponent#isCallerInRole to return the wrong value. Both of these methods rely on incomingRunAsIdentity. Affects all versions of JBoss EAP from 7.1.0 and all versions of WildFly 11+ when Elytron is enabled.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
—
EPSS
54.1%
KEV
Not listed

Published

May 10, 2022

Last Modified

November 6, 2025

References (2)

Vendor Advisories for CVE-2022-0866(10)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrh-sso7-keycloak-0:18.0.3-1.redhat_00001.1.el8sso2022-11-03redhat
redhatwildfly2022-11-03redhat
redhatrh-sso7-keycloak-0:18.0.3-1.redhat_00001.1.el7sso2022-11-03redhat
redhatrh-sso7-keycloak-0:18.0.3-1.redhat_00001.1.el9sso2022-11-03redhat
redhatrh-sso7-keycloak-0:15.0.8-1.redhat_00001.1.el8sso2022-10-04redhat
redhatrh-sso7-keycloak-0:15.0.8-1.redhat_00001.1.el7sso2022-10-04redhat
redhateap7-wildfly-0:7.4.5-3.GA_redhat_00001.1.el8eap2022-06-06redhat
redhateap7-wildfly-0:7.4.5-3.GA_redhat_00001.1.el7eap2022-06-06redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 101 total refreshes for this CVE.

  1. 2026-07-22 22:53 UTCEG score recompute
  2. 2026-07-22 14:06 UTCEPSS rescore
  3. 2026-07-21 15:22 UTCEPSS rescore
  4. 2026-07-21 15:22 UTCEPSS rescore
  5. 2026-07-20 17:05 UTCEPSS rescore
  6. 2026-07-19 14:29 UTCEPSS rescore
  7. 2026-07-19 02:27 UTCEPSS rescore
  8. 2026-07-19 02:27 UTCEPSS rescore
  9. 2026-07-18 10:02 UTCEPSS rescore
  10. 2026-07-17 11:59 UTCOSV refresh
  11. 2026-07-16 17:00 UTCEPSS rescore
  12. 2026-07-16 17:00 UTCEPSS rescore
  13. 2026-07-15 16:55 UTCEPSS rescore
  14. 2026-07-15 01:58 UTCEPSS rescore
  15. 2026-07-15 01:58 UTCEPSS rescore
  16. 2026-07-13 22:27 UTCEPSS rescore
  17. 2026-07-13 06:11 UTCEPSS rescore
  18. 2026-07-13 06:11 UTCEPSS rescore
  19. 2026-07-12 05:44 UTCEPSS rescore
  20. 2026-07-11 08:25 UTCEPSS rescore
  21. 2026-07-09 19:07 UTCEPSS rescore
  22. 2026-07-09 19:07 UTCEPSS rescore
  23. 2026-07-08 15:12 UTCEPSS rescore
  24. 2026-07-08 15:12 UTCEPSS rescore
  25. 2026-07-07 13:43 UTCEPSS rescore
Show 75 more
  1. 2026-07-06 16:25 UTCEPSS rescore
  2. 2026-07-06 16:25 UTCEPSS rescore
  3. 2026-07-06 02:21 UTCEPSS rescore
  4. 2026-07-06 02:21 UTCEPSS rescore
  5. 2026-07-05 02:28 UTCEPSS rescore
  6. 2026-07-05 02:28 UTCEPSS rescore
  7. 2026-07-04 06:29 UTCEPSS rescore
  8. 2026-07-04 06:29 UTCEPSS rescore
  9. 2026-07-01 15:04 UTCEPSS rescore
  10. 2026-06-29 14:04 UTCEPSS rescore
  11. 2026-06-29 14:04 UTCEPSS rescore
  12. 2026-06-29 10:32 UTCOSV refresh
  13. 2026-06-28 14:05 UTCEPSS rescore
  14. 2026-06-28 04:54 UTCEPSS rescore
  15. 2026-06-28 04:54 UTCEPSS rescore
  16. 2026-06-27 03:07 UTCEPSS rescore
  17. 2026-06-27 03:06 UTCEPSS rescore
  18. 2026-06-25 13:48 UTCEPSS rescore
  19. 2026-06-25 13:48 UTCEPSS rescore
  20. 2026-06-24 14:03 UTCEPSS rescore
  21. 2026-06-24 14:03 UTCEPSS rescore
  22. 2026-06-23 21:31 UTCEPSS rescore
  23. 2026-06-23 21:31 UTCEPSS rescore
  24. 2026-06-22 14:24 UTCEPSS rescore
  25. 2026-06-21 14:55 UTCEPSS rescore
  26. 2026-06-21 01:58 UTCEPSS rescore
  27. 2026-06-21 01:58 UTCEPSS rescore
  28. 2026-06-19 19:24 UTCEPSS rescore
  29. 2026-06-19 19:24 UTCEPSS rescore
  30. 2026-06-18 17:51 UTCEPSS rescore
  31. 2026-06-18 17:51 UTCEPSS rescore
  32. 2026-06-17 17:51 UTCEPSS rescore
  33. 2026-06-17 17:51 UTCEPSS rescore
  34. 2026-06-16 17:51 UTCEPSS rescore
  35. 2026-06-15 17:46 UTCEPSS rescore
  36. 2026-06-14 23:15 UTCEPSS rescore
  37. 2026-06-14 23:15 UTCEPSS rescore
  38. 2026-06-13 22:58 UTCEPSS rescore
  39. 2026-06-13 22:58 UTCEPSS rescore
  40. 2026-06-12 23:10 UTCEPSS rescore
  41. 2026-06-12 02:27 UTCOSV refresh
  42. 2026-06-11 13:58 UTCEPSS rescore
  43. 2026-06-10 22:16 UTCEPSS rescore
  44. 2026-06-10 13:20 UTCEPSS rescore
  45. 2026-06-08 14:15 UTCEPSS rescore
  46. 2026-06-08 14:15 UTCEPSS rescore
  47. 2026-06-08 14:15 UTCEPSS rescore
  48. 2026-06-07 15:23 UTCEPSS rescore
  49. 2026-06-07 15:23 UTCEPSS rescore
  50. 2026-06-06 13:46 UTCEPSS rescore
  51. 2026-06-06 13:46 UTCEPSS rescore
  52. 2026-06-05 22:45 UTCEPSS rescore
  53. 2026-06-05 22:45 UTCEPSS rescore
  54. 2026-06-05 06:09 UTCEPSS rescore
  55. 2026-06-05 06:09 UTCEPSS rescore
  56. 2026-06-04 13:11 UTCEPSS rescore
  57. 2026-06-04 13:10 UTCEPSS rescore
  58. 2026-06-02 20:11 UTCEPSS rescore
  59. 2026-06-02 20:11 UTCEPSS rescore
  60. 2026-06-01 13:50 UTCEPSS rescore
  61. 2026-06-01 13:50 UTCEPSS rescore
  62. 2026-05-31 22:29 UTCEPSS rescore
  63. 2026-05-31 00:15 UTCEPSS rescore
  64. 2026-05-31 00:15 UTCEPSS rescore
  65. 2026-05-29 13:42 UTCEPSS rescore
  66. 2026-05-28 13:43 UTCEPSS rescore
  67. 2026-05-28 13:43 UTCEPSS rescore
  68. 2026-05-27 13:39 UTCEPSS rescore
  69. 2026-05-27 13:39 UTCEPSS rescore
  70. 2026-05-26 13:43 UTCEPSS rescore
  71. 2026-05-26 13:42 UTCEPSS rescore
  72. 2026-05-26 07:17 UTCEPSS rescore
  73. 2026-05-26 07:17 UTCEPSS rescore
  74. 2026-05-25 22:29 UTCEG score recompute
  75. 2026-05-25 22:29 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-0866?
CVE-2022-0866 is a medium vulnerability published on May 10, 2022. This is a concurrency issue that can result in the wrong caller principal being returned from the session context of an EJB that is configured with a RunAs principal. In particular, the org.jboss.as.ejb3.component.EJBComponent class has an incomingRunAsIdentity field. This field is used by the…
When was CVE-2022-0866 disclosed?
CVE-2022-0866 was first published in the National Vulnerability Database on May 10, 2022, with the most recent update on November 6, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-0866 actively exploited?
CVE-2022-0866 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 54.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-0866?
CVE-2022-0866 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2022-0866?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-0866, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-0866

Explore →

Is Your Infrastructure Affected by CVE-2022-0866?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs