Authorization Bypass Through User-Controlled Key Affecting github.com/0xjacky/nginx-ui/api/certificate package, versions <2.3.5
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Authorization Bypass Through User-Controlled Key vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-GOLANG-GITHUBCOM0XJACKYNGINXUIAPICERTIFICATE-15915106
- published6 Apr 2026
- disclosed30 Mar 2026
- creditf1veT
Introduced: 30 Mar 2026
CVE-2026-33030 Â (opens in a new tab)How to fix?
Upgrade github.com/0xJacky/Nginx-UI/api/certificate to version 2.3.5 or higher.
Overview
Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key through the certificate issuance/auto-certification flows in api/certificate/issue.go and api/sites/auto_cert.go, and JSON field encryption migration in the internal/migrate. An attacker can steal DNS API tokens and ACME private keys, then use them to hijack DNS records or issue fraudulent certificates by accessing or creating affected resources that store these secrets. The issue affects dns_credentials.config, acme_users.key, and certs.resource, which are now migrated to AES-encrypted storage; before this fix, those values were stored as plain JSON and could be read directly from the database or exposed through application access paths.