CVE-2026-104019

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

GHSA-w64x-664p-7w66 ↗EUVD-2026-91795 ↗

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.
AWS sagemaker-distribution 2.14.x: < 2.14.12; 3.9.x: < 3.9.12; 4.0.x: < 4.0.11; 4.1.x: < 4.1.11; 4.2.x: < 4.2.8; 4.3.x: < 4.3.5; 4.4.x: < 4.4.3; 2.8.x - 2.13.x
fixed in 2.x before 2.14.12, 3.x before 3.9.12, 4.0.x before 4.0.11, 4.1.x before 4.1.11, 4.2.x before 4.2.8, 4.3.x before 4.3.5, and 4.4.x before 4.4.3
CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
ETK-2026-378, permanent identifier
18d 18h 53msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h53m
0
+4h
+6h
+8h
+10h
+12h

description

Affected sagemaker-distribution releases contain a command-injection flaw in Studio Space startup validation. An authenticated Amazon SageMaker Unified Studio project contributor could run commands in another member's Studio Space and obtain that member's temporary execution-role credentials through a crafted connection resource property.

mitigation

Upgrade to 2.14.12, 3.9.12, 4.0.11, 4.1.11, 4.2.8, 4.3.5, or 4.4.3, as appropriate for the deployed minor line; move end-of-support minor lines to a supported release. In Unified Studio, restart Studio Spaces after patched images are deployed so they use the updated patch release.

fixed in 2.x before 2.14.12, 3.x before 3.9.12, 4.0.x before 4.0.11, 4.1.x before 4.1.11, 4.2.x before 4.2.8, 4.3.x before 4.3.5, and 4.4.x before 4.4.3

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, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
1.4%72nd percentile
agent run time
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-02 20:08Z
Δ 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-02 20:08Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-378",
  "cve_id": "CVE-2026-104019",
  "display_id": "CVE-2026-104019",
  "ghsa_id": "GHSA-w64x-664p-7w66",
  "euvd_id": "EUVD-2026-91795",
  "status": "published",
  "anchor_state": "anchored",
  "title": "OS command injection in sagemaker-distribution",
  "summary": "Affected sagemaker-distribution releases contain a command-injection flaw in Studio Space startup validation. An authenticated Amazon SageMaker Unified Studio project contributor could run commands in another member's Studio Space and obtain that member's temporary execution-role credentials through a crafted connection resource property.",
  "mitigation": "Upgrade to 2.14.12, 3.9.12, 4.0.11, 4.1.11, 4.2.8, 4.3.5, or 4.4.3, as appropriate for the deployed minor line; move end-of-support minor lines to a supported release. In Unified Studio, restart Studio Spaces after patched images are deployed so they use the updated patch release.",
  "vendor": "AWS",
  "product": "sagemaker-distribution",
  "affected": [
    {
      "affected_notes": [
        "2.8.x - 2.13.x"
      ],
      "affected_ranges": [
        "2.14.x: < 2.14.12",
        "3.9.x: < 3.9.12",
        "4.0.x: < 4.0.11",
        "4.1.x: < 4.1.11",
        "4.2.x: < 4.2.8",
        "4.3.x: < 4.3.5",
        "4.4.x: < 4.4.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.x before 2.14.12",
        "3.x before 3.9.12",
        "4.0.x before 4.0.11",
        "4.1.x before 4.1.11",
        "4.2.x before 4.2.8",
        "4.3.x before 4.3.5",
        "and 4.4.x before 4.4.3"
      ],
      "package_name": null,
      "purl": null
    }
  ],
  "cwes": [
    78
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L",
  "epss_score": 0.0142,
  "epss_percentile": 0.7244,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 18.21292795,
  "t0_at": "2026-10-02T20:08:10.061000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T20:08:10.061000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T20:08:10.061000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-104019"
    }
  }
}

published 2026-10-02 21:43Z
last change 2026-10-21 12:26Z

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.