CVE-2026-107813

validatedZero produced an exploit or a check.

GHSA-h246-wpgf-vmq5 ↗EUVD-2026-95898 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
0xJacky nginx-ui >= 2.0.0, < 2.5.0
fixed in 2.5.0
CWE-862 Missing Authorization
ETK-2026-1088Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:golang/github.com/0xJacky/Nginx-UI
+1.2dTTV
1h 10mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+27h43magent stopped
0
+6h
+12h
+18h
+24h
+30h

description

nginx-ui versions from 2.0.0 before 2.5.0 do not require a fresh secure-session check for cluster node and namespace changes or cluster-wide Nginx reload and restart actions. An authenticated user with a stolen or retained JWT, but without completing the current OTP step-up, may perform those administrative operations.

mitigation

Upgrade nginx-ui to version 2.5.0 or later. Until upgrades are complete, restrict access to the nginx-ui management interface and revoke or rotate potentially exposed JWTs.

fixed in 2.5.0

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
deterministic
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.31%21st percentile
agent run time
1h 10m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-09 15:47Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-09 15:47Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-107813

{
  "etk_id": "ETK-2026-1088",
  "cve_id": "CVE-2026-107813",
  "display_id": "CVE-2026-107813",
  "ghsa_id": "GHSA-h246-wpgf-vmq5",
  "euvd_id": "EUVD-2026-95898",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing step-up authentication in nginx-ui cluster management",
  "summary": "nginx-ui versions from 2.0.0 before 2.5.0 do not require a fresh secure-session check for cluster node and namespace changes or cluster-wide Nginx reload and restart actions. An authenticated user with a stolen or retained JWT, but without completing the current OTP step-up, may perform those administrative operations.",
  "mitigation": "Upgrade nginx-ui to version 2.5.0 or later. Until upgrades are complete, restrict access to the nginx-ui management interface and revoke or rotate potentially exposed JWTs.",
  "vendor": "0xJacky",
  "product": "nginx-ui",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.0.0, < 2.5.0"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "2.5.0"
      ],
      "package_name": "github.com/0xJacky/Nginx-UI",
      "purl": "pkg:golang/github.com/0xJacky/Nginx-UI"
    }
  ],
  "cwes": [
    862
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0031,
  "epss_percentile": 0.2187,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 70.10949875,
  "t0_at": "2026-10-09T15:47:33.503000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-10T19:30:40.886802+00:00",
      "days": 1.1549465717824074,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T15:47:33.503000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-09T15:47:33.503000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T15:47:33.503000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-107813"
    }
  }
}

published 2026-10-09 17:56Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.