← back to feed
CVE-2026-89103

CVE-2026-89103

validatedZero produced an exploit or a check.

GHSA-p6vw-54fj-mjm4 ↗EUVD-2026-120662 ↗

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.
SAP_SE SAP Gateway 7.22EXT; 7.53; 8.04; 7.54; 7.77; 7.93; 9.16; 9.20; 9.21; KRNL64NUC 7.22; KRNL64UC 7.22; KERNEL 7.22
CWE-863 Incorrect Authorization
ETK-2026-4016Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss10.0cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
+39mTTV
8mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+39magent stopped
0
+10min
+20min
+30min

description

SAP Gateway is affected when its default access control list assigns excessive privileges to external network clients. An unauthenticated attacker with network access may be treated as an internal application server and perform unauthorized actions. Exposure requires network reachability to the affected SAP Gateway.

mitigation

Replace or restrict the default access control list so external network clients cannot be classified as internal application servers. Limit network access to SAP Gateway to trusted systems until vendor remediation is applied.

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.
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
8m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-10 00:18Z
Δ 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 check: a technique exists and was validated, 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-11-10 00:18Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-89103
  2. 2026-11-10 12:07Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4016",
  "cve_id": "CVE-2026-89103",
  "display_id": "CVE-2026-89103",
  "ghsa_id": "GHSA-p6vw-54fj-mjm4",
  "euvd_id": "EUVD-2026-120662",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper authorization in SAP Gateway default access control list",
  "summary": "SAP Gateway is affected when its default access control list assigns excessive privileges to external network clients. An unauthenticated attacker with network access may be treated as an internal application server and perform unauthorized actions. Exposure requires network reachability to the affected SAP Gateway.",
  "mitigation": "Replace or restrict the default access control list so external network clients cannot be classified as internal application servers. Limit network access to SAP Gateway to trusted systems until vendor remediation is applied.",
  "vendor": "SAP_SE",
  "product": "SAP Gateway",
  "affected": [
    {
      "affected_notes": [
        "KRNL64NUC 7.22",
        "KRNL64UC 7.22",
        "KERNEL 7.22"
      ],
      "affected_ranges": [
        "7.22EXT",
        "7.53",
        "8.04",
        "7.54",
        "7.77",
        "7.93",
        "9.16",
        "9.20",
        "9.21"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "SAP Gateway",
      "purl": null
    }
  ],
  "cwes": [
    863
  ],
  "cvss_score": 10,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 8.03781175,
  "t0_at": "2026-11-10T00:18:43.492000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-10T00:57:28.173040+00:00",
      "days": 0.026906030555555554,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T00:18:43.492000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-10T00:18:43.492000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T00:18:43.492000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-89103"
    }
  }
}

published 2026-11-10 00:48Z
last change 2026-11-11 04:39Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.