Quick answers
- Is CVE-2026-92082 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92082 being exploited in the wild.
- How severe is CVE-2026-92082?
- Informational severity, with a CVSS score of 0, published 15 September 2026.
- Which products and versions are affected?
- Azul Payara Server before 7.2.0.
- Is there a fix for CVE-2026-92082?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-92082 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-92082?
- Check whether anything you run is named in the advisory. 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.
Technical details
The vulnerability stems from the lack of default rate-limiting or account lockout mechanisms for failed authentication attempts. An attacker can make repeated login requests to the Payara Server admin console or application authentication endpoints without triggering automatic account lockout or connection throttling. This is a network-reachable attack requiring only knowledge of valid usernames. The impact is credential compromise through brute force, leading to potential system takeover. Payara provides built-in attack protection features via the security configuration framework, but these require explicit administrator setup and are not enabled by default.
Affected products
- Azul Payara Server before 7.2.0
Timeline
- 2026-09-15: disclosed: CVE-2026-92082 published; vulnerability addressed in Payara 7.2.0 with security fix FISH-13687