CVE-2026-107807

validatedZero produced an exploit or a check.

GHSA-pvgv-gcp7-v38g ↗EUVD-2026-95882 ↗

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).+2h03mkevAttacks confirmed in the real world.
go:github.com/0xJacky/Nginx-UI >= 1.9.10-0.20250517140552-daee3ac7ade1, < 1.9.10-0.20260728074433-a3999bd78a3b
fixed in 1.9.10-0.20260728074433-a3999bd78a3b
ETK-2026-1099Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:golang/github.com/0xJacky/Nginx-UI
+6h19mTTV
30mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hpublic poc+2h03mcheck available+6h19magent stopped
0
+4h

description

nginx-ui deployments that accept the node secret in URL query data can expose that administrative credential through logs, browser metadata, or cluster configuration. An attacker who obtains the credential from one of those sources can access the API with administrative privileges, bypassing ordinary login controls. Read access to affected logging, configuration, environment, or database data is the relevant precondition.

mitigation

Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260728074433-a3999bd78a3b. Remove node secrets from URLs and deployment variables, rotate any existing node secrets, and restrict access to historical logs and configuration data.

fixed in 1.9.10-0.20260728074433-a3999bd78a3b

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%22nd percentile
agent run time
30m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-09 15:04Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+2h03m
Δ 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:04Z
    ghsa: trigger signal, started the run
  2. 2026-10-09 15:04Z
    public poc, published 2026-10-09 17:07Z
  3. 2026-10-09 15:04Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1099",
  "cve_id": "CVE-2026-107807",
  "display_id": "CVE-2026-107807",
  "ghsa_id": "GHSA-pvgv-gcp7-v38g",
  "euvd_id": "EUVD-2026-95882",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Node-secret query exposure in nginx-ui",
  "summary": "nginx-ui deployments that accept the node secret in URL query data can expose that administrative credential through logs, browser metadata, or cluster configuration. An attacker who obtains the credential from one of those sources can access the API with administrative privileges, bypassing ordinary login controls. Read access to affected logging, configuration, environment, or database data is the relevant precondition.",
  "mitigation": "Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260728074433-a3999bd78a3b. Remove node secrets from URLs and deployment variables, rotate any existing node secrets, and restrict access to historical logs and configuration data.",
  "vendor": "go",
  "product": "go:github.com/0xJacky/Nginx-UI",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.9.10-0.20250517140552-daee3ac7ade1, < 1.9.10-0.20260728074433-a3999bd78a3b"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "1.9.10-0.20260728074433-a3999bd78a3b"
      ],
      "package_name": "github.com/0xJacky/Nginx-UI",
      "purl": "pkg:golang/github.com/0xJacky/Nginx-UI"
    }
  ],
  "cwes": null,
  "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.2232,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 29.723193033333335,
  "t0_at": "2026-10-09T15:04:18.109000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-09T21:23:14.011124+00:00",
      "days": 0.2631470153240741,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T15:04:18.109000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-10-09T17:07:09+00:00",
      "days": 0.08531123842592593,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T15:04:18.109000+00:00",
      "url": "https://github.com/advisories/GHSA-pvgv-gcp7-v38g"
    },
    "trigger_signal": {
      "at": "2026-10-09T15:04:18.109000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T15:04:18.109000+00:00",
      "url": "https://github.com/advisories/GHSA-pvgv-gcp7-v38g"
    }
  }
}

published 2026-10-09 20:53Z
last change 2026-10-21 11:38Z

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.