CVE-2026-10757

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

GHSA-34qg-vwfc-f4rm ↗EUVD-2026-110057 ↗

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.
Esri ArcGIS Server >= 11.1, < 12.1
fixed in 12.1
ETK-2026-2680Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 45msince last run
51mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h31m
0
+4h
+6h
+8h
+10h
+12h

description

Esri ArcGIS Server on Windows and Linux through version 12.1 is affected. An attacker with service access may invoke unauthorized database-specific functions; anonymous access may be possible if the service is configured as public.

mitigation

Apply Esri's available security patch for supported ArcGIS Server releases 11.1, 11.3, 11.5, 12.0, or 12.1. Upgrade unlisted mature or retired releases to a supported version, and restrict public service access where it is not required.

fixed in 12.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.
contextual
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.
–
agent run time
51m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-26 18:05Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-26 18:05Z
    ghsa: trigger signal, started the run
  2. 2026-10-26 18:05Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2680",
  "cve_id": "CVE-2026-10757",
  "display_id": "CVE-2026-10757",
  "ghsa_id": "GHSA-34qg-vwfc-f4rm",
  "euvd_id": "EUVD-2026-110057",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in Esri ArcGIS Server",
  "summary": "Esri ArcGIS Server on Windows and Linux through version 12.1 is affected. An attacker with service access may invoke unauthorized database-specific functions; anonymous access may be possible if the service is configured as public.",
  "mitigation": "Apply Esri's available security patch for supported ArcGIS Server releases 11.1, 11.3, 11.5, 12.0, or 12.1. Upgrade unlisted mature or retired releases to a supported version, and restrict public service access where it is not required.",
  "vendor": "Esri",
  "product": "ArcGIS Server",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 11.1, < 12.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "12.1"
      ],
      "package_name": "ArcGIS Server",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 50.8423112,
  "t0_at": "2026-10-26T18:05:59.365000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T18:05:59.365000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-26T18:05:59.365000+00:00",
      "url": "https://github.com/advisories/GHSA-34qg-vwfc-f4rm"
    }
  }
}

published 2026-10-26 18:45Z
last change 2026-10-26 21:18Z

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.