CVE-2026-130380

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

GHSA-rv8q-c9gp-2hc7 ↗EUVD-2026-126818 ↗

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.
adminneo-org AdminNeo < 5.9.1
fixed in 5.9.1
ETK-2026-4641Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 17h 50msince last run
20mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+2h24m
0
+4h
+6h
+8h
+10h
+12h

description

AdminNeo versions before 5.9.1 are affected by an authentication bypass in the sqlsrv-based MS SQL driver. An unauthenticated attacker may obtain a session with the SQL Server privileges of the web server identity when this driver is configured.

mitigation

Upgrade AdminNeo to version 5.9.1 or later. Until upgraded, disable or restrict access to deployments using the sqlsrv-based MS SQL driver.

fixed in 5.9.1

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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.52%44th percentile
agent run time
20m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-17 01:40Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-11-17 01:40Z
    ghsa: trigger signal, started the run
  2. 2026-11-17 01:40Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4641",
  "cve_id": "CVE-2026-130380",
  "display_id": "CVE-2026-130380",
  "ghsa_id": "GHSA-rv8q-c9gp-2hc7",
  "euvd_id": "EUVD-2026-126818",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in AdminNeo sqlsrv driver",
  "summary": "AdminNeo versions before 5.9.1 are affected by an authentication bypass in the sqlsrv-based MS SQL driver. An unauthenticated attacker may obtain a session with the SQL Server privileges of the web server identity when this driver is configured.",
  "mitigation": "Upgrade AdminNeo to version 5.9.1 or later. Until upgraded, disable or restrict access to deployments using the sqlsrv-based MS SQL driver.",
  "vendor": "adminneo-org",
  "product": "AdminNeo",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 5.9.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "5.9.1"
      ],
      "package_name": "AdminNeo",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0052,
  "epss_percentile": 0.449,
  "epss_asof": "2026-11-17",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.687832266666668,
  "t0_at": "2026-11-17T01:40:36.057000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-17T01:40:36.057000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-17T01:40:36.057000+00:00",
      "url": "https://github.com/advisories/GHSA-rv8q-c9gp-2hc7"
    }
  }
}

published 2026-11-17 03:44Z
last change 2026-11-18 21:43Z

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.