CVE-2026-107510

waiting for further signalsZero needs more public information before it can validate it.

GHSA-hgvr-pf8h-6rjx ↗EUVD-2026-94824 ↗

no check availablenot proven exploitable
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.
Infoblox NIOS >= 9.0.x, <= 9.1.0
ETK-2026-963, permanent identifier
11d 10h 55msince last run
6mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+50h56m
0
+2h
+4h
+6h
+8h
+10h

description

Infoblox NIOS troubleshooting commands are affected by an argument-injection flaw. An authenticated high-privilege user may exploit it to gain elevated privileges; access to a high-privilege account is required.

mitigation

Restrict high-privilege NIOS access to trusted administrators and review use of troubleshooting commands. Apply vendor updates when Infoblox provides a fixed release; no fixed version is recorded in the advisory.

check
no
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.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.29%20th percentile
agent run time
6m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-08 09:45Z
Δ 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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-08 09:45Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-963",
  "cve_id": "CVE-2026-107510",
  "display_id": "CVE-2026-107510",
  "ghsa_id": "GHSA-hgvr-pf8h-6rjx",
  "euvd_id": "EUVD-2026-94824",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authenticated argument injection in Infoblox NIOS",
  "summary": "Infoblox NIOS troubleshooting commands are affected by an argument-injection flaw. An authenticated high-privilege user may exploit it to gain elevated privileges; access to a high-privilege account is required.",
  "mitigation": "Restrict high-privilege NIOS access to trusted administrators and review use of troubleshooting commands. Apply vendor updates when Infoblox provides a fixed release; no fixed version is recorded in the advisory.",
  "vendor": "Infoblox",
  "product": "NIOS",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 9.0.x, <= 9.1.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "NIOS",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": 0.0029,
  "epss_percentile": 0.2085,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 5.516706383333333,
  "t0_at": "2026-10-08T09:45:04.001000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-08T09:45:04.001000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T09:45:04.001000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-107510"
    }
  }
}

published 2026-10-08 10:56Z
last change 2026-10-21 22:34Z

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.