CVE-2026-83494

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

GHSA-4452-5gpc-g9w6 ↗EUVD-2026-117966 ↗

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.
Red Hat OpenShift AI (RHOAI)
CWE-693 Protection Mechanism Failure
ETK-2026-3712Zero's internal tracking ID, independent of the CVE number., permanent identifier
14h 09msince last run
49mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+28h22m
0
+2h
+4h
+6h
+8h
+10h

description

OpenShift AI training-operator is affected by a type-handling flaw in PyTorchJob update validation. A user permitted to modify PyTorchJob resources may bypass immutability restrictions, potentially disrupting quota tracking or changing job controller ownership and causing denial of service.

mitigation

Restrict PyTorchJob update permissions to trusted operators and review existing role bindings. Monitor for and promptly apply the Red Hat package update when a fixed version is published.

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.17%6th percentile
agent run time
49m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-06 06:39Z
Δ 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-11-06 06:39Z
    ghsa: trigger signal, started the run
  2. 2026-11-06 06:39Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3712",
  "cve_id": "CVE-2026-83494",
  "display_id": "CVE-2026-83494",
  "ghsa_id": "GHSA-4452-5gpc-g9w6",
  "euvd_id": "EUVD-2026-117966",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Immutability-check bypass in OpenShift AI training-operator",
  "summary": "OpenShift AI training-operator is affected by a type-handling flaw in PyTorchJob update validation. A user permitted to modify PyTorchJob resources may bypass immutability restrictions, potentially disrupting quota tracking or changing job controller ownership and causing denial of service.",
  "mitigation": "Restrict PyTorchJob update permissions to trusted operators and review existing role bindings. Monitor for and promptly apply the Red Hat package update when a fixed version is published.",
  "vendor": "Red Hat",
  "product": "Red Hat OpenShift AI (RHOAI)",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "rhoai/odh-training-operator-rhel9",
      "purl": null
    }
  ],
  "cwes": [
    693
  ],
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": 0.0017,
  "epss_percentile": 0.0622,
  "epss_asof": "2026-11-06",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 48.903978,
  "t0_at": "2026-11-06T06:39:12.292000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-06T06:39:12.292000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-06T06:39:12.292000+00:00",
      "url": "https://github.com/advisories/GHSA-4452-5gpc-g9w6"
    }
  }
}

published 2026-11-06 09:50Z
last change 2026-11-08 00:54Z

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.