Servers and applications
GHSA-c2cq-7453-7xpj
Read-only service tokens still receive stored secrets (incomplete fix of GHSA-pw4f-pq6v-x57r)
- Severity
- Medium 6.5
- Published
- 20 Nov 2026
- Last changed
- 20 Nov 2026
- Added to UpHeron
- 20 Nov 2026
- Fixed in
- 2.9.2
- Weakness
- Information exposure (CWE-200)
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N- Sources
- Project advisories (GitHub)
Description
api:read service tokens are meant to be read-only and must not receive stored secrets. The fix for GHSA-pw4f-pq6v-x57r redacted credentials only on the DNS credential, ACME account and S3 auto-backup endpoints. A token with api:read but without api:write still received stored secrets on other read paths:
- certificate private keys from GET /api/certs/:id, from GET /api/config reads of key files, and from configuration history
- notifier configuration values (SMTP passwords, bot tokens, webhook secrets) from GET /api/external_notifies and /:id
- site health-check header values, request bodies and URL credentials from GET /api/site_navigation, /site_navigation/health_check/:id and the site_navigation_ws feed
- DNS provider credentials nested in GET /api/dns/domains and /:id
- files Nginx reads secrets from (password files, session ticket keys, auth_basic_user_file) through GET /api/config
- the same content through the MCP nginx_config_get and nginx_config_history tools for tokens…
Workarounds
Issue api:read tokens only to automation you would trust with the stored credentials, or revoke them until you can upgrade.
Affected software
| Software | Affected versions |
|---|---|
Nginx UIServers and applications · github:0xjacky/nginx-ui |
|
About Nginx UI
Yet another WebUI for Nginx
- Docker Hub pulls
- 1,512,532Docker Hub, 15 Nov 2026
- GitHub stars
- 11,783GitHub, 15 Nov 2026
- Forks
- 921GitHub, 15 Nov 2026
- Latest release
- v3.0.3GitHub, 15 Nov 2026
- Released
- 12 Nov 2026GitHub
- License
- AGPL-3.0GitHub
- First published on GitHub
- 19 Feb 2021GitHub
Source code Website Docker image
Vulnerabilities in Nginx UI
- In our list
- 75
- Published in the last 12 months
- 67
- Critical, last 12 months
- 11
- High, last 12 months
- 34
- Known exploited
- 0
- GHSA-57f3-39rr-2mwmNginx-UI certificate path validators read arbitrary absolute paths, enabling a file existence oracle and process-crash DoSLow 3.8 20 Nov 2026
- GHSA-xwxf-xc5j-p7hxDirective denylist bypass via mid-token '#' tokenizer differential (incomplete fix of GHSA-cf23-7qxj-xmhr)High 7.2 20 Nov 2026
- GHSA-2rjr-44wx-8qpgJwtSecret Overwrite via Settings API Causes Session Invalidation and MonopolyLow 3.8 12 Nov 2026
- GHSA-p355-qjwh-8hgmOpenAI API Key Exfiltration via Unprotected BaseUrl Setting ChangeLow 2.7 12 Nov 2026
- GHSA-hf3h-p3fr-3f2rFull backup exports expose reusable interactive login sessions to management credentialsMedium 6.6 12 Nov 2026
- GHSA-mfj4-8rf3-rpq6Unauthenticated dependency inventory + version disclosure via `/api/licenses*`Medium 5.3 12 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-c2cq-7453-7xpj
- github.com https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-c2cq-7453-7xpj