Unsafeaccessorproject Unsafe Accessor
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Unsafeaccessorproject Unsafe Accessor.
By the Year
In 2026 there have been 0 vulnerabilities in Unsafeaccessorproject Unsafe Accessor. Unsafe Accessor did not have any published security vulnerabilities last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 0 | 0.00 |
| 2025 | 0 | 0.00 |
| 2024 | 0 | 0.00 |
| 2023 | 0 | 0.00 |
| 2022 | 1 | 7.50 |
It may take a day or so for new Unsafe Accessor vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Unsafeaccessorproject Unsafe Accessor Security Vulnerabilities
UnsafeAccessor (UA) is a bridge to access jdk.internal.misc.Unsafe & sun.misc.Unsafe
CVE-2022-31139
7.5 - High
- July 11, 2022
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 without limitation, even when UA is loaded as a named module. This issue does not affect those for whom `SecurityCheck.AccessLimiter` is not set up. Version 1.7.0 contains a patch.
AuthZ
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Unsafeaccessorproject Unsafe Accessor or by Unsafeaccessorproject? Click the Watch button to subscribe.
