CVE-2026-50892
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIncorrect access control in the "Let's Encrypt" certificate download endpoint of Nginx Proxy Manager v2.14.0 allows authenticated attackers to obtain the TLS private key material via a crafted GET request.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceNginx Proxy Manager v2.14.0 contains an incorrect access control vulnerability in the Let's Encrypt certificate download endpoint. Authenticated attackers can craft GET requests to bypass authorization checks and download TLS private key material belonging to other users or domains.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Nginx Proxy Manager versionLog into the admin UI and navigate to the 'System Information' or 'About' page to view the running version. Alternatively, check the Docker image tag or package version used in your deployment.Affected if The installed version is v2.14.0 exactly, or falls between v2.14.0 and v2.14.1 (if unpatched).
-
Confirm Let's Encrypt certificate functionality is in useIn the admin UI, review the list of SSL Certificates under the 'SSL Certificates' or 'Proxy Hosts' section. Look for certificates issued by Let's Encrypt (typically showing Let's Encrypt as the issuer).Affected if Let's Encrypt certificates are configured and actively managed by the Nginx Proxy Manager instance.
-
Verify multi-user access is enabledCheck the user management settings in the admin UI or review the database for multiple user accounts. The vulnerability requires an authenticated attacker, so multiple user accounts must exist.Affected if More than one user account exists in the system, or external authentication providers are linked.
-
Review access logs for suspicious certificate download requestsExamine Nginx Proxy Manager logs (container logs or /var/log/nginx-proxy-manager.log) for GET requests to the certificate download endpoint. Look for requests accessing /api/ssl/certificates/{id}/download or similar paths where the certificate ID does not belong to the requesting user.Affected if Logs show certificate download requests where the requesting user ID does not match the owner of the requested certificate.
You are affected if running Nginx Proxy Manager v2.14.0 with Let's Encrypt certificates and multi-user access, particularly if logs show cross-user certificate download attempts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to v2.14.1 or later where the access control flaw is remediated. Alternatively, implement strict authorization checks on the certificate download endpoint to verify the requesting user owns the requested certificate before returning private key material.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50892 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50892 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data