Vulnerability in github.com/0xJacky/Nginx-UI (CVE-2026-84315)
Summary
Vulnerability in github.com/0xJacky/Nginx-UI (CVE-2026-84315). Data can be tampered with by attackers. Exploitable via POST /api/config. Mitigation: upgrade to 1.9.10-0.20260703131214-23d1934099b0 or later.
Original description
The description as published by the source.
Reporter: Jagadesh Achanta
Target: 0xJacky/nginx-ui
Affected version / commit tested:
- App version:
2.3.10 - Commit:
4948fba8744e82c3d7003f68ee164e9f49421066 - Disclosure channel: GitHub Private Vulnerability Reporting
- Credential reference:
cred:github-jagstack-gh-cli
AI assistance disclosure
This report was prepared by Jagadesh Achanta with assistance from OpenAI/Codex for public source review, local evidence collection, and report drafting.
Summary
Nginx UI has a short-lived OTP/passkey "secure session" step-up boundary for users with 2FA enabled. RequireSecureSession() rejects an OTP-enabled user's request unless the request includes a valid X-Secure-Session-ID issued after a fresh OTP/passkey verification.
The project already applies this step-up middleware to sensitive operations such as:
- Nginx config create/edit/rename/delete;
- site save/delete/enable/disable/rename/duplicate;
- stream save/delete/enable/disable/rename/duplicate;
- settings save and protected secret reads;
- backup restore.
However, several similarly sensitive authenticated mutation routes remain outside RequireSecureSession(). An attacker who obtains an authenticated JWT/session for a 2FA-enabled user, but does not have the victim's fresh OTP/passkey secure-session token, can still perform those operations.
The affected route groups include:
- automatic backup create/modify/delete/restore/test-S3 operations;
- DNS credential create/edit/delete operations;
- certific…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-84315 has been found in github.com/0xJacky/Nginx-UI.
Attackers can target a specific entry point like POST /api/config over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.3/10.
What to do: upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260703131214-23d1934099b0 or later.
If unsure, ask your IT team or search "github.com/0xJacky/Nginx-UI CVE-2026-84315" on the vendor's site.
CVE-2026-84315 (github.com/0xJacky/Nginx-UI) — CWE-862 / CVSS v3 8.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/config / POST /api/dns_credentials / Advanced
Patched: 1.9.10-0.20260703131214-23d1934099b0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in github.com/0xJacky/Nginx-UI. Attackers reach the vulnerable code path via POST /api/config.
Check the vendor advisory for the affected versions of github.com/0xJacky/Nginx-UI. Attack surface: POST /api/config / POST /api/dns_credentials / Advanced.
Severity: High (CVSS 8.3/10). Data can be tampered with by attackers.
Update to 1.9.10-0.20260703131214-23d1934099b0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/config requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/0xJacky/Nginx-UI' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/0xJacky/Nginx-UI' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/0xJacky/Nginx-UIを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/config' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/configへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260703131214-23d1934099b0ステージング環境で 1.9.10-0.20260703131214-23d1934099b0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/config on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com