CVE-2026-96658

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

GHSA-g2wg-rx2f-4j5r ↗EUVD-2026-90921 ↗

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 Satellite 6.19 for RHEL 9
ETK-2026-257, permanent identifier
19d 17h 38msince last run
1h 28mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h38m
0
+2h
+6h
+8h
+10h
+12h

description

Red Hat Satellite 6.19 for RHEL 9 includes an affected Foreman component. An authenticated user with low-level permissions could bypass template sandbox restrictions and execute commands on the hosting server. Exploitation requires access to an account with the necessary low-level permissions.

mitigation

Restrict low-level Foreman permissions and limit access to the Satellite service to trusted users and networks. Apply the vendor-provided update when it becomes available; the supplied package data does not identify a fixed version.

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.
0.69%51st percentile
agent run time
1h 28m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 16:23Z
Δ 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-01 16:23Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-257",
  "cve_id": "CVE-2026-96658",
  "display_id": "CVE-2026-96658",
  "ghsa_id": "GHSA-g2wg-rx2f-4j5r",
  "euvd_id": "EUVD-2026-90921",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Template sandbox bypass in Foreman",
  "summary": "Red Hat Satellite 6.19 for RHEL 9 includes an affected Foreman component. An authenticated user with low-level permissions could bypass template sandbox restrictions and execute commands on the hosting server. Exploitation requires access to an account with the necessary low-level permissions.",
  "mitigation": "Restrict low-level Foreman permissions and limit access to the Satellite service to trusted users and networks. Apply the vendor-provided update when it becomes available; the supplied package data does not identify a fixed version.",
  "vendor": "Red Hat",
  "product": "Red Hat Satellite 6.19 for RHEL 9",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "foreman",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": 0.0069,
  "epss_percentile": 0.5178,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 88.26206231666667,
  "t0_at": "2026-10-01T16:23:23.688000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T16:23:23.688000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T16:23:23.688000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-96658"
    }
  }
}

published 2026-10-01 16:37Z
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.