CVE-2026-33030

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 0.3% (20th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.8 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-03-30) is not newer than that change (2026-06-17), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-17156 (ENISA EUVD) · GHSA-5hf2-vhj6-gj9m (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.9Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

Nginx UI is a web user interface for the Nginx web server. In versions 2.3.3 and prior, 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. At time of publication, there are no publicly available patches.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
61
EG Risk 61/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 30, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Oct 27, 2026
No fix on record yet. Sources: github.
GitHub advisoryMentions a patch (unverified)

Unencrypted Storage of DNS API Tokens and ACME Private Keys · Advisory · 0xJacky/nginx-ui · GitHub

https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-5hf2-vhj6-gj9m

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/0xJacky/nginx-ui—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/0xJacky/nginx-ui—
  • every version through 1.99: no fix on record
  • every version on: no fix on record
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 72× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 174 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 77 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-29 23:55 UTCEG score recompute
  2. 2026-10-29 23:55 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  3. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  4. 2026-10-29 01:57 UTCEG score recompute
  5. 2026-10-29 01:57 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  6. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-10-28 03:56 UTCEG score recompute
  8. 2026-10-28 03:56 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-10-27 05:45 UTCEG score recompute
  11. 2026-10-27 05:45 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  12. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  13. 2026-10-26 03:45 UTCEG score recompute
  14. 2026-10-26 03:45 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  15. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  16. 2026-10-25 14:35 UTCEG score recompute
  17. 2026-10-25 05:48 UTCEG score recompute
  18. 2026-10-25 05:47 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  19. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-10-24 07:50 UTCEG score recompute
  21. 2026-10-24 07:49 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  22. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  23. 2026-10-23 09:49 UTCEG score recompute
  24. 2026-10-23 09:48 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  25. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
Show 72 more
  1. 2026-10-22 11:46 UTCEG score recompute
  2. 2026-10-22 11:46 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  3. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  4. 2026-10-21 13:44 UTCEG score recompute
  5. 2026-10-21 13:44 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  6. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  7. 2026-10-20 15:44 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  8. 2026-10-19 17:01 UTCEG score recompute
  9. 2026-10-19 17:00 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-10-18 19:00 UTCEG score recompute
  12. 2026-10-18 19:00 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  13. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-10-18 03:47 UTCEG score recompute
  15. 2026-10-17 21:02 UTCEG score recompute
  16. 2026-10-17 21:02 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  17. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-10-16 23:01 UTCEG score recompute
  19. 2026-10-16 23:01 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-10-15 20:07 UTCEG score recompute
  22. 2026-10-15 20:07 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  23. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  24. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  25. 2026-10-14 14:03 UTCEG score recompute
  26. 2026-10-14 14:02 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  27. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  28. 2026-10-13 13:34 UTCEG score recompute
  29. 2026-10-13 13:34 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  30. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  31. 2026-10-12 15:35 UTCEG score recompute
  32. 2026-10-12 15:35 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  33. 2026-10-12 08:29 UTCGHSA enrichmentGHSA-5hf2-vhj6-gj9m · GitHub severity HIGH · GitHub CVSS 8.8
  34. 2026-10-11 19:56 UTCEG score recompute
  35. 2026-10-11 17:09 UTCEG score recompute
  36. 2026-10-11 14:36 UTCEG score recompute
  37. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  38. 2026-10-11 03:31 UTCOSV refresh
  39. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  40. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  41. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  42. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  43. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  44. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  45. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  46. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  47. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  48. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  49. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  50. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  51. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  52. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  53. 2026-09-21 15:19 UTCOSV refresh
  54. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  55. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  56. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  57. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  58. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  59. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  60. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  61. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  62. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  63. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  64. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  65. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  66. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  67. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  68. 2026-09-02 12:44 UTCOSV refresh
  69. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  70. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  71. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  72. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 20th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-33030?
CVE-2026-33030 is a critical-severity vulnerability; its CVE record was published on March 30, 2026. Nginx UI is a web user interface for the Nginx web server. In versions 2.3.3 and prior, 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…
When was the CVE record for CVE-2026-33030 published?
The CVE record for CVE-2026-33030 was published on March 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-33030 actively exploited?
CVE-2026-33030 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33030?
CVE-2026-33030 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-33030?
No fix for CVE-2026-33030 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33030

Explore →

Is Your Infrastructure Affected by CVE-2026-33030?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs