Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-102334 – Authentication Brute-Force via Missing Rate Limiting – Nginx Proxy Manager ≤ 2.16.

Be the first to know when new zero-days emerge:

Summary

CVE-2026-102334 is a missing rate-limiting (brute-force protection) vulnerability affecting Nginx Proxy Manager through version 2.16.0. The application’s authentication endpoints do not throttle or lock out repeated failed login attempts, allowing an unauthenticated network attacker to make unlimited password and TOTP (two-factor) code guesses against any account. Successful exploitation can lead to full administrative takeover of the Nginx Proxy Manager instance, rated high/critical severity.

Technical details

  • Root cause: The POST /api/tokens (login) and POST /api/tokens/2fa (TOTP verification) endpoints lack rate-limiting, account lockout, or CAPTCHA controls, so authentication attempts can be repeated without restriction (CWE-307: Improper Restriction of Excessive Authentication Attempts).
  • Trigger conditions: No authentication or prior access is required; the endpoints are reachable by any client that can send HTTP requests to the exposed management interface.
  • Attack vector: Network-based. An attacker scripts repeated password guesses against POST /api/tokens to brute-force a known or guessed admin username, then, if TOTP-based two-factor authentication is enabled, brute-forces the numeric TOTP code via POST /api/tokens/2fa.
  • Impact: Successful credential and/or TOTP guessing yields a valid session token, granting full administrative access to the Nginx Proxy Manager control panel — which manages reverse proxy hosts, TLS certificates, and redirect/access rules for the protected environment.

Affected software

  • NginxProxyManager nginx-proxy-manager — all versions up to and including 2.16.0

Severity

  • CVSS v3.1: 7.4 (HIGH) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
  • A CVSS v4.0 score of 9.1 (CRITICAL) — CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N — has also been published for this vulnerability.

Mitigation and recommended actions

  • Immediate: Upgrade Nginx Proxy Manager beyond version 2.16.0 once a version containing rate-limiting protections for the authentication and 2FA endpoints is released. A fix (adding a sliding-window rate limiter on POST /tokens and POST /tokens/2fa) has been submitted upstream; monitor the official GitHub releases page and apply the patched release as soon as it is published.
  • If no patch is yet available:
    • Restrict network access to the Nginx Proxy Manager admin UI/API to trusted IP ranges or a VPN — do not expose the management interface directly to the internet.
    • Enforce strong, unique passwords and enable two-factor authentication (TOTP) on all accounts to raise the brute-force cost.
    • Place the admin interface behind an additional authentication layer (e.g., reverse proxy with HTTP basic auth, IP allow-listing, or a WAF/rate-limiting proxy) to throttle repeated login attempts.
    • Monitor authentication logs for repeated failed login or 2FA verification attempts and alert on anomalous volumes.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge