CVE-2026-33030: Github.com/0xJacky/nginx ui Nginx-UI Has Unencrypted Storage Of Vulnerability

HIGH
Advisory Identifier: GHSA-5hf2-vhj6-gj9m
CVSS 8.8
CWE-78 CWE-639
Published
Advisory Summary

CVE-2026-33030 is a HIGH (CVSS 8.8) nginx-ui has unencrypted storage of vulnerability (CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')) affecting Github.com/0xJacky/nginx ui libraries in the Go ecosystem. The issue involves nginx-ui has unencrypted storage of dns api tokens and acme private keys. Remediation is available in the latest vendor maintenance releases.

CVE-2026-33030 at a Glance

CVE Identifier CVE-2026-33030
GHSA Identifier GHSA-5hf2-vhj6-gj9m
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Affected Product Github.com/0xJacky/nginx ui
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 8.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-33030

To remediate this vulnerability, upgrade all affected Github.com/0xJacky/nginx ui dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/0xJacky/nginx-ui fixed: Latest secure release
Upgrade github.com/0xJacky/nginx-ui to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/0xJacky/nginx-ui

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-33030, inspect your project dependencies for Github.com/0xJacky/nginx ui:

inspect dependencies for github.com/0xJacky/nginx-ui

Analyze the terminal output to locate any version of Github.com/0xJacky/nginx ui in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'), where the product constructs all or part of an os command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended os command when it is sent to a downstream component. In Github.com/0xJacky/nginx ui, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary Nginx-UI contains an Insecure Direct Object Reference (IDOR) vulnerability that allows any authenticated user to access, modify, and delete resources belonging to other users. The application's base `Model` struct lacks a `user_id` field, and all resource endpoints perform queries by ID without verifying user ownership, enabling complete authorization bypass in multi-user environments. ## Severity **High** - CVSS 3.1 Score: **8.8 (High)** Vector String: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H` **Note**: Original score was 7.5. The score was updated to 8.8 after discovering that sensitive data (DNS API tokens, ACME private keys) is stored in plaintext, which when combined with IDOR allows immediate credential theft without decryption. ## Product nginx-ui ## Affected Versions All versions up to and including v2.3.3 ## CWE CWE-639: Authorization Bypass Through User-Controlled Key ## Description ### Exposed DNS Provider Credentials The `dns.Config` structure (`internal/cert/dns/config_env.go`) contains API credentials: ```go type Configuration struct { Credentials map[string]string `json:"credentials"` // API tokens here Additional map[string]string `json:"additional"` } ``` | Provider | Credential Fields | Impact if Leaked | |----------|------------------|------------------| | Cloudflare | `CF_API_TOKEN` | Full DNS zone control | | Alibaba Cloud DNS | `ALICLOUD_ACCESS_KEY`, `ALICLOUD_SECRET_KEY` | Full DNS control + potential IAM access | | Tencent Cloud DNS | `TENCENTCLOUD_SECRET_ID`, `TENCENTCLOUD_SECRET_KEY` | Full DNS control | | AWS Route53 | `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY` | Route53 + potential AWS access | | GoDaddy | `GODADDY_API_KEY`, `GODADDY_API_SECRET` | DNS record modification | ### Combined Attack: IDOR + Plaintext Storage When the IDOR vulnerability is combined with plaintext storage, attackers can directly extract API tokens from other users' resources: ``` Attack Chain: ┌─────────────────────────────────────────────────────────────────┐ │ 1. Attacker authenticates with low-privilege account │ │ 2. Uses IDOR to enumerate: /api/dns_credentials/1,2,3... │ │ 3. Reads plaintext API tokens directly from HTTP response │ │ 4. No decryption needed - tokens stored in cleartext │ │ 5. Uses stolen tokens to: │ │ - Modify DNS records (domain hijacking) │ │ - Issue fraudulent SSL certificates │ │ - Pivot to cloud infrastructure │ └─────────────────────────────────────────────────────────────────┘ ``` ### PoC: Extracting Plaintext Credentials via IDOR ```bash # Attacker with low-privilege token accessing admin's DNS credential curl -H "Authorization: $ATTACKER_TOKEN" \ https://nginx-ui.example.com/api/dns_credentials/1 # Response contains PLAINTEXT API token (no decryption required): { "id": 1, "name": "Production Cloudflare", "provider": "cloudflare", "config": { "credentials": { "CF_API_TOKEN": "yhyQ7xR...plaintext_token_visible..." } } } ``` ### Updated CVSS Score with Plaintext Storage The plaintext storage increases the confidentiality impact: **CVSS 3.1 Score: 8.8 (High)** Vector: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H` - **Scope Changed (S:C)**: Impact extends to external services (DNS providers, cloud platforms) - **High Confidentiality (C:H)**: Plaintext API tokens immediately usable - **High Integrity (I:H)**: DNS records, certificates can be modified - **High Availability (A:H)**: Services can be disrupted via DNS/certificate manipulation --- ### Attack Scenario: Certificate Hijacking ``` 1. Attacker creates low-privilege account on nginx-ui 2. Uses IDOR to enumerate all DNS credentials: /api/dns_credentials/1,2,3... 3. Steals Cloudflare API token from admin's credential 4. Uses token to: - Modify DNS records - Issue fraudulent Let's Encrypt certificates - Intercept traffic to victim domains ``` ## Credit Discovered by security researcher during authorized security audit. ## Recommendation ### Immediate Mitigation 1. **Add User Ownership to Models** ```go // model/model.go type Model struct { ID uint64 `gorm:"primary_key" json:"id"` UserID uint64 `gorm:"index" json:"user_id"` // Add this field CreatedAt time.Time `json:"created_at"` UpdatedAt time.Time `json:"updated_at"` DeletedAt *gorm.DeletedAt `gorm:"index" json:"deleted_at,omitempty"` } ``` 2. **Filter Queries by Current User** ```go // api/certificate/dns_credential.go func GetDnsCredential(c *gin.Context) { id := cast.ToUint64(c.Param("id")) currentUser := c.MustGet("user").(*model.User) d := query.DnsCredential dnsCredential, err := d.Where( d.ID.Eq(id), d.UserID.Eq(currentUser.ID), // Add user filter ).First() if err != nil { cosy.ErrHandler(c, err) return } // ... } ``` 3. **Add Authorization Middleware** ```go // middleware/authorization.go func RequireOwnership(resourceType string) gin.HandlerFunc { return func(c *gin.Context) { currentUser := c.MustGet("user").(*model.User) resourceID := cast.ToUint64(c.Param("id")) // Check if resource belongs to current user ownerID, err := getResourceOwner(resourceType, resourceID) if err != nil || ownerID != currentUser.ID { c.AbortWithStatusJSON(http.StatusForbidden, gin.H{ "message": "Access denied", }) return } c.Next() } } ``` ### Database Migration ```sql -- Add user_id column to all resource tables ALTER TABLE dns_credentials ADD COLUMN user_id BIGINT; ALTER TABLE certs ADD COLUMN user_id BIGINT; ALTER TABLE acme_users ADD COLUMN user_id BIGINT; ALTER TABLE sites ADD COLUMN user_id BIGINT; ALTER TABLE streams ADD COLUMN user_id BIGINT; ALTER TABLE configs ADD COLUMN user_id BIGINT; -- Set default owner for existing resources UPDATE dns_credentials SET user_id = 1 WHERE user_id IS NULL; UPDATE certs SET user_id = 1 WHERE user_id IS NULL; -- Add foreign key constraint ALTER TABLE dns_credentials ADD CONSTRAINT fk_dns_credentials_user FOREIGN KEY (user_id) REFERENCES users(id); ``` ### Long-term Improvements 1. Implement role-based access control (RBAC) 2. Add audit logging for resource access 3. Implement resource sharing functionality with explicit permissions 4. Add integration tests for authorization checks --- ## Remediation for Plaintext Storage ### Immediate Fix: Encrypt Sensitive Fields Apply the same `serializer:json[aes]` pattern used for S3 credentials to DNS and ACME data: **model/dns_credential.go:** ```go type DnsCredential struct { Model Name string `json:"name"` Config *dns.Config `json:"config,omitempty" gorm:"serializer:json[aes]"` // Add AES encryption Provider string `json:"provider"` ProviderCode string `json:"provider_code" gorm:"index"` } ``` **model/acme_user.go:** ```go type AcmeUser struct { Model // ... Key PrivateKey `json:"-" gorm:"serializer:json[aes]"` // Add AES encryption // ... } ``` ### Data Migration Existing plaintext data must be re-saved to trigger encryption: ```go func MigrateSensitiveData() error { // Migrate DNS credentials var dnsCreds []model.DnsCredential query.DnsCredential.Find(&dnsCreds) for _, cred := range dnsCreds { query.DnsCredential.Save(&cred) // Re-save triggers AES encryption } // Migrate ACME users var acmeUsers []model.AcmeUser query.AcmeUser.Find(&acmeUsers) for _, user := range acmeUsers { query.AcmeUser.Save(&user) } return nil } ``` ### Summary of Required Changes | File | Line | Current | Fix | |------|------|---------|-----| | `model/dns_credential.go` | 7 | `serializer:json` | `serializer:json[aes]` | | `model/acme_user.go` | Key field | `serializer:json` | `serializer:json[aes]` | ## References - [CWE-639: Authorization Bypass Through User-Controlled Key](https://cwe.mitre.org/data/definitions/639.html) - [OWASP IDOR Prevention Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Insecure_Direct_Object_Reference_Prevention_Cheat_Sheet.html) - [PortSwigger: IDOR Vulnerabilities](https://portswigger.net/web-security/access-control/idor) ## Disclosure Timeline - **2026-03-13**: Vulnerability discovered through source code audit - **2026-03-13**: Vulnerability successfully reproduced in local Docker environment - **2026-03-13**: All IDOR operations verified: READ, MODIFY, DELETE - **2026-03-13**: Security advisory prepared - **[Pending]**: Report submitted to nginx-ui maintainers - **[Pending]**: CVE ID requested - **[Pending]**: Patch developed and tested - **[Pending]**: Public disclosure (21-90 days after vendor notification)

CVE-2026-33030 Affected Github.com/0xJacky/nginx ui Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
github.com/0xJacky/nginx-ui
Go
≤ 1.99

References

Frequently Asked Questions

What is CVE-2026-33030?
CVE-2026-33030 is a security vulnerability in Github.com/0xJacky/nginx ui involving nginx-UI has Unencrypted Storage of DNS API Tokens and ACME Private Keys under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection').
Which Github.com/0xJacky/nginx ui versions are affected?
Affected versions include releases prior to current release patches across affected packages: github.com/0xJacky/nginx-ui.
What version fixes CVE-2026-33030?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/0xJacky/nginx-ui affected?
Yes, github.com/0xJacky/nginx-ui is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-33030?
CVE-2026-33030 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2026-33030?
CVE-2026-33030 is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') (The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.).
How can I check Go dependencies for CVE-2026-33030?
Run the dependency tree command: 'inspect dependencies for github.com/0xJacky/nginx-ui'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5hf2-vhj6-gj9m",
  "modified" : "2026-03-30T21:26:12Z",
  "published" : "2026-03-30T16:41:07Z",
  "aliases" : [ "CVE-2026-33030" ],
  "summary" : "nginx-UI has Unencrypted Storage of DNS API Tokens and ACME Private Keys",
  "details" : "## Summary\n\nNginx-UI contains an Insecure Direct Object Reference (IDOR) vulnerability that allows any authenticated user to access, modify, and delete resources belonging to other users. The application's base `Model` struct lacks a `user_id` field, and all resource endpoints perform queries by ID without verifying user ownership, enabling complete authorization bypass in multi-user environments.\n\n## Severity\n\n**High** - CVSS 3.1 Score: **8.8 (High)**\n\nVector String: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`\n\n**Note**: Original score was 7.5. The score was updated to 8.8 after discovering that sensitive data (DNS API tokens, ACME private keys) is stored in plaintext, which when combined with IDOR allows immediate credential theft without decryption.\n\n## Product\n\nnginx-ui\n\n## Affected Versions\n\nAll versions up to and including v2.3.3\n\n## CWE\n\nCWE-639: Authorization Bypass Through User-Controlled Key\n\n## Description\n\n### Exposed DNS Provider Credentials\n\nThe `dns.Config` structure (`internal/cert/dns/config_env.go`) contains API credentials:\n\n```go\ntype Configuration struct {\n    Credentials map[string]string `json:\"credentials\"`  // API tokens here\n    Additional  map[string]string `json:\"additional\"`\n}\n```\n\n| Provider | Credential Fields | Impact if Leaked |\n|----------|------------------|------------------|\n| Cloudflare | `CF_API_TOKEN` | Full DNS zone control |\n| Alibaba Cloud DNS | `ALICLOUD_ACCESS_KEY`, `ALICLOUD_SECRET_KEY` | Full DNS control + potential IAM access |\n| Tencent Cloud DNS | `TENCENTCLOUD_SECRET_ID`, `TENCENTCLOUD_SECRET_KEY` | Full DNS control |\n| AWS Route53 | `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY` | Route53 + potential AWS access |\n| GoDaddy | `GODADDY_API_KEY`, `GODADDY_API_SECRET` | DNS record modification |\n\n### Combined Attack: IDOR + Plaintext Storage\n\nWhen the IDOR vulnerability is combined with plaintext storage, attackers can directly extract API tokens from other users' resources:\n\n```\nAttack Chain:\n┌─────────────────────────────────────────────────────────────────┐\n│ 1. Attacker authenticates with low-privilege account            │\n│ 2. Uses IDOR to enumerate: /api/dns_credentials/1,2,3...      │\n│ 3. Reads plaintext API tokens directly from HTTP response       │\n│ 4. No decryption needed - tokens stored in cleartext            │\n│ 5. Uses stolen tokens to:                                       │\n│    - Modify DNS records (domain hijacking)                      │\n│    - Issue fraudulent SSL certificates                          │\n│    - Pivot to cloud infrastructure                              │\n└─────────────────────────────────────────────────────────────────┘\n```\n\n### PoC: Extracting Plaintext Credentials via IDOR\n\n```bash\n# Attacker with low-privilege token accessing admin's DNS credential\ncurl -H \"Authorization: $ATTACKER_TOKEN\" \\\n     https://nginx-ui.example.com/api/dns_credentials/1\n\n# Response contains PLAINTEXT API token (no decryption required):\n{\n    \"id\": 1,\n    \"name\": \"Production Cloudflare\",\n    \"provider\": \"cloudflare\",\n    \"config\": {\n        \"credentials\": {\n            \"CF_API_TOKEN\": \"yhyQ7xR...plaintext_token_visible...\"\n        }\n    }\n}\n```\n\n### Updated CVSS Score with Plaintext Storage\n\nThe plaintext storage increases the confidentiality impact:\n\n**CVSS 3.1 Score: 8.8 (High)**\n\nVector: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`\n\n- **Scope Changed (S:C)**: Impact extends to external services (DNS providers, cloud platforms)\n- **High Confidentiality (C:H)**: Plaintext API tokens immediately usable\n- **High Integrity (I:H)**: DNS records, certificates can be modified\n- **High Availability (A:H)**: Services can be disrupted via DNS/certificate manipulation\n\n---\n\n### Attack Scenario: Certificate Hijacking\n\n```\n1. Attacker creates low-privilege account on nginx-ui\n2. Uses IDOR to enumerate all DNS credentials: /api/dns_credentials/1,2,3...\n3. Steals Cloudflare API token from admin's credential\n4. Uses token to:\n   - Modify DNS records\n   - Issue fraudulent Let's Encrypt certificates\n   - Intercept traffic to victim domains\n```\n\n## Credit\n\nDiscovered by security researcher during authorized security audit.\n\n## Recommendation\n\n### Immediate Mitigation\n\n1. **Add User Ownership to Models**\n\n```go\n// model/model.go\ntype Model struct {\n    ID        uint64          `gorm:\"primary_key\" json:\"id\"`\n    UserID    uint64          `gorm:\"index\" json:\"user_id\"`  // Add this field\n    CreatedAt time.Time       `json:\"created_at\"`\n    UpdatedAt time.Time       `json:\"updated_at\"`\n    DeletedAt *gorm.DeletedAt `gorm:\"index\" json:\"deleted_at,omitempty\"`\n}\n```\n\n2. **Filter Queries by Current User**\n\n```go\n// api/certificate/dns_credential.go\nfunc GetDnsCredential(c *gin.Context) {\n    id := cast.ToUint64(c.Param(\"id\"))\n    currentUser := c.MustGet(\"user\").(*model.User)\n\n    d := query.DnsCredential\n    dnsCredential, err := d.Where(\n        d.ID.Eq(id),\n        d.UserID.Eq(currentUser.ID),  // Add user filter\n    ).First()\n\n    if err != nil {\n        cosy.ErrHandler(c, err)\n        return\n    }\n    // ...\n}\n```\n\n3. **Add Authorization Middleware**\n\n```go\n// middleware/authorization.go\nfunc RequireOwnership(resourceType string) gin.HandlerFunc {\n    return func(c *gin.Context) {\n        currentUser := c.MustGet(\"user\").(*model.User)\n        resourceID := cast.ToUint64(c.Param(\"id\"))\n\n        // Check if resource belongs to current user\n        ownerID, err := getResourceOwner(resourceType, resourceID)\n        if err != nil || ownerID != currentUser.ID {\n            c.AbortWithStatusJSON(http.StatusForbidden, gin.H{\n                \"message\": \"Access denied\",\n            })\n            return\n        }\n        c.Next()\n    }\n}\n```\n\n### Database Migration\n\n```sql\n-- Add user_id column to all resource tables\nALTER TABLE dns_credentials ADD COLUMN user_id BIGINT;\nALTER TABLE certs ADD COLUMN user_id BIGINT;\nALTER TABLE acme_users ADD COLUMN user_id BIGINT;\nALTER TABLE sites ADD COLUMN user_id BIGINT;\nALTER TABLE streams ADD COLUMN user_id BIGINT;\nALTER TABLE configs ADD COLUMN user_id BIGINT;\n\n-- Set default owner for existing resources\nUPDATE dns_credentials SET user_id = 1 WHERE user_id IS NULL;\nUPDATE certs SET user_id = 1 WHERE user_id IS NULL;\n\n-- Add foreign key constraint\nALTER TABLE dns_credentials ADD CONSTRAINT fk_dns_credentials_user\n    FOREIGN KEY (user_id) REFERENCES users(id);\n```\n\n### Long-term Improvements\n\n1. Implement role-based access control (RBAC)\n2. Add audit logging for resource access\n3. Implement resource sharing functionality with explicit permissions\n4. Add integration tests for authorization checks\n\n---\n\n## Remediation for Plaintext Storage\n\n### Immediate Fix: Encrypt Sensitive Fields\n\nApply the same `serializer:json[aes]` pattern used for S3 credentials to DNS and ACME data:\n\n**model/dns_credential.go:**\n```go\ntype DnsCredential struct {\n    Model\n    Name         string      `json:\"name\"`\n    Config       *dns.Config `json:\"config,omitempty\" gorm:\"serializer:json[aes]\"` // Add AES encryption\n    Provider     string      `json:\"provider\"`\n    ProviderCode string      `json:\"provider_code\" gorm:\"index\"`\n}\n```\n\n**model/acme_user.go:**\n```go\ntype AcmeUser struct {\n    Model\n    // ...\n    Key PrivateKey `json:\"-\" gorm:\"serializer:json[aes]\"` // Add AES encryption\n    // ...\n}\n```\n\n### Data Migration\n\nExisting plaintext data must be re-saved to trigger encryption:\n\n```go\nfunc MigrateSensitiveData() error {\n    // Migrate DNS credentials\n    var dnsCreds []model.DnsCredential\n    query.DnsCredential.Find(&dnsCreds)\n    for _, cred := range dnsCreds {\n        query.DnsCredential.Save(&cred) // Re-save triggers AES encryption\n    }\n\n    // Migrate ACME users\n    var acmeUsers []model.AcmeUser\n    query.AcmeUser.Find(&acmeUsers)\n    for _, user := range acmeUsers {\n        query.AcmeUser.Save(&user)\n    }\n\n    return nil\n}\n```\n\n### Summary of Required Changes\n\n| File | Line | Current | Fix |\n|------|------|---------|-----|\n| `model/dns_credential.go` | 7 | `serializer:json` | `serializer:json[aes]` |\n| `model/acme_user.go` | Key field | `serializer:json` | `serializer:json[aes]` |\n\n## References\n\n- [CWE-639: Authorization Bypass Through User-Controlled Key](https://cwe.mitre.org/data/definitions/639.html)\n- [OWASP IDOR Prevention Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Insecure_Direct_Object_Reference_Prevention_Cheat_Sheet.html)\n- [PortSwigger: IDOR Vulnerabilities](https://portswigger.net/web-security/access-control/idor)\n\n## Disclosure Timeline\n\n- **2026-03-13**: Vulnerability discovered through source code audit\n- **2026-03-13**: Vulnerability successfully reproduced in local Docker environment\n- **2026-03-13**: All IDOR operations verified: READ, MODIFY, DELETE\n- **2026-03-13**: Security advisory prepared\n- **[Pending]**: Report submitted to nginx-ui maintainers\n- **[Pending]**: CVE ID requested\n- **[Pending]**: Patch developed and tested\n- **[Pending]**: Public disclosure (21-90 days after vendor notification)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/0xJacky/nginx-ui"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "1.99"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-5hf2-vhj6-gj9m"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33030"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/0xJacky/nginx-ui"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/0xJacky/nginx-ui/releases/tag/v2.3.4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639", "CWE-78" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-30T16:41:07Z",
    "nvd_published_at" : "2026-03-30T18:16:19Z"
  }
}