# CVE-2026-92082: Payara Server is vulnerable to brute-force login attacks due to the absence of a limit on failed login attempts

> Attackers can brute-force login credentials because Payara Server lacks default failed login attempt limits, requiring configuration of built-in protection.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N/AU:Y/R:U/V:C/RE:L/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-mwf3-qj4r-2qq4

## What is CVE-2026-92082?

CVE-2026-92082 is a medium-severity vulnerability in Payara Server, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

By default, Payara Server does not limit the number of failed login attempts, which can leave it vulnerable to brute force login attacks. To mitigate this, Payara Server includes built-in automatic attack protection. For configuration details, see  https://docs.azul.com/payara/technical-documentation/payara-server-documentation/security-guide/administering-system-security.html .

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2026-92082?


## How do I fix CVE-2026-92082?

No fix has been published for CVE-2026-92082 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92082 being exploited?

There is no known exploitation of CVE-2026-92082 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92082 and fix it if it is affected.

What it is: CVE-2026-92082 is a medium-severity vulnerability in Payara Server, published on 15 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92082 in the wild and no public exploit code.

Affected product: Payara Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92082/ (Markdown: https://insights.sbomify.com/CVE-2026-92082/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92082
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92082
- OSV: https://osv.dev/vulnerability/CVE-2026-92082

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92082/
Summaries are generated and may contain mistakes; the official description above is the record.