CVE-2022-31139: UnsafeAccessor (UA) is a bridge to access jdk.internal.misc.Unsafe & sun.misc.Unsafe
CVE-2022-31139 is a medium-severity flaw (CVSS 5.9) affecting unsafe accessor. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
UnsafeAccessor (UA) is a bridge to access jdk.internal.misc.Unsafe & sun.misc.Unsafe. Normally, if UA is loaded as a named module, the internal data of UA is protected by JVM and others can only access UA via UA's standard API. The main application can set up `SecurityCheck.AccessLimiter` for UA to limit access to UA. Starting with version 1.4.0 and prior to version 1.7.0, when `SecurityCheck.AccessLimiter` is set up, untrusted code can access UA
Why this priority
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-31139?
unsafe accessor: upgrade to 1.7.0. Exact commands for each OS are on this page.
Is CVE-2022-31139 being exploited?
CVE-2022-31139 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-31139 affect?
CVE-2022-31139 affects unsafe accessor. Severity is medium (CVSS 5.9). UnsafeAccessor (UA) is a bridge to access jdk.internal.misc.Unsafe & sun.misc.Unsafe. Normally, if UA is loaded as a named module, the internal data of UA is protected by JVM and others can only access UA via UA's standard API. The main app
How urgent is CVE-2022-31139?
Priority 43/100. Remotely exploitable, no login, no user action