CVE-2026-107360

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

GHSA-xrw4-g928-4w5v ↗EUVD-2026-124669 ↗

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
ETK-2026-4326Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 48msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h06m
0
+4h
+6h
+8h
+10h
+12h

description

Red Hat Satellite 6 is affected by a sandbox-handling flaw in rubygem-safemode. An authenticated user able to provide template content may circumvent method restrictions and invoke exposed no-argument methods, potentially disclosing object state or making destructive changes.

mitigation

Restrict template creation and modification permissions to trusted administrators, and review existing template-authoring access. Apply the relevant Red Hat Satellite 6 update after confirming the vendor-provided fixed release.

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.
–
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-12 20:04Z
Δ 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-12 20:04Z
    ghsa: trigger signal, started the run
  2. 2026-11-12 20:04Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4326",
  "cve_id": "CVE-2026-107360",
  "display_id": "CVE-2026-107360",
  "ghsa_id": "GHSA-xrw4-g928-4w5v",
  "euvd_id": "EUVD-2026-124669",
  "status": "published",
  "anchor_state": "anchored",
  "title": "rubygem-safemode sandbox allow-list bypass",
  "summary": "Red Hat Satellite 6 is affected by a sandbox-handling flaw in rubygem-safemode. An authenticated user able to provide template content may circumvent method restrictions and invoke exposed no-argument methods, potentially disclosing object state or making destructive changes.",
  "mitigation": "Restrict template creation and modification permissions to trusted administrators, and review existing template-authoring access. Apply the relevant Red Hat Satellite 6 update after confirming the vendor-provided fixed release.",
  "vendor": "Red Hat",
  "product": "Red Hat Satellite 6",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "rubygem-safemode",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.368698916666666,
  "t0_at": "2026-11-12T20:04:13.447000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-12T20:04:13.447000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T20:04:13.447000+00:00",
      "url": "https://github.com/advisories/GHSA-xrw4-g928-4w5v"
    }
  }
}

published 2026-11-12 21:56Z
last change 2026-11-12 23:23Z

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.