CVE-2026-107360: Patch safemode's template allow-list bypass
Restrict template-editing privileges and install the corrected rubygem-safemode package on affected Red Hat Satellite systems. Red Hat’s CNA record for CVE-2026-107360 rates the flaw Critical, CVSS v3.1 9.6 and records public disclosure on November 12, 2026 at 18:46:45 UTC.
An authenticated attacker who can supply template content can bypass safemode’s Jail method allow-list through compound assignment expressions. The reported impact is invocation of otherwise-disallowed no-argument methods on objects exposed to the renderer, including host deletion and disclosure of object state. The advisory does not establish unrestricted operating-system command execution.
Match the full package revision
The Red Hat-authored record names Satellite 6.16 on RHEL 8/9, and 6.17/6.18 on RHEL 9. It marks the exact package revisions printed below unaffected. Match your product branch and operating-system release; the upstream gem version 1.5.0 alone does not identify the corrected RPM.
Save inspect-safemode-advisory.py to extract that supplier metadata locally:
import json
from pathlib import Path
import sys
record = json.loads(Path(sys.argv[1]).read_text())
if record["cveMetadata"]["cveId"] != "CVE-2026-107360":
raise SystemExit("Wrong CVE record")
cna = record["containers"]["cna"]
print(f"Public date: {cna['datePublic']}")
for product in cna["affected"]:
for version in product["versions"]:
if version["status"] == "unaffected":
print(f"{product['product']} | {product['packageName']} {version['version']}")
print("Advisory metadata only; no installed package was checked.")curl --fail --silent --show-error 'https://cveawg.mitre.org/api/cve/CVE-2026-107360' --output safemode-cve.json
python3 inspect-safemode-advisory.py safemode-cve.jsonActual output on Debian 13 with Python 3.12.14:
Public date: 2026-11-12T18:46:45.782Z
Red Hat Satellite 6.16 for RHEL 8 | rubygem-safemode 0:1.5.0-3.el8sat
Red Hat Satellite 6.16 for RHEL 9 | rubygem-safemode 0:1.5.0-3.el9sat
Red Hat Satellite 6.17 for RHEL 9 | rubygem-safemode 0:1.5.0-3.el9sat
Red Hat Satellite 6.18 for RHEL 9 | rubygem-safemode 0:1.5.0-3.el9sat
Advisory metadata only; no installed package was checked.Both commands exited successfully. This reads the public CVE record, not your package database. On each affected deployment, record the installed RPM’s full name, epoch, version, release and architecture through the host’s package inventory. Compare the supplier revision for that Satellite/RHEL pair and retain it with the deployment record. Custom gem bundles need their own confirmed fix; the CNA does not identify a universal upstream fixed gem release.
Apply the supported Satellite update
Red Hat links RHSA-2026:99949, RHSA-2026:99950 and RHSA-2026:99952. Their bodies were unavailable during this check, so the package revisions above come from Red Hat’s CNA record; no erratum-to-branch mapping is inferred.
Use the erratum and subscribed update channel applicable to your Satellite release, including its backup, maintenance and restart procedure. Verify Capsule and other relevant deployment components against their own package inventories. Do not replace packaged gems by hand or assume a general OS update installed this application fix.
After the supported restart, confirm the running service uses the updated package. In staging, render ordinary approved templates and check that existing authorization rules still behave as intended. A successful normal render is a compatibility check, not proof that the allow-list bypass is absent. No destructive template expression is needed for operational verification.
Reduce exposure until the update is deployed
Red Hat recommends limiting template editing to trusted administrators. Where feasible, avoid exposing highly privileged ActiveRecord objects to untrusted template authors. Review inherited roles, automation accounts and template-change history as well as interactive users. Network restrictions alone do not stop an already authorized template author from reaching the vulnerable renderer.
Preserve evidence if unexpected object changes or template edits suggest misuse. The cited CNA record does not report confirmed exploitation in the wild; that is not proof of absence. This Linux check inspected advisory metadata only. No RPM installation, Satellite instance or exploit was tested. Remove the downloaded JSON and helper when they are no longer needed.
Acknowledgements
This post was created with assistance from AI.