CVE
Red Hat Satellite allow-list bypass in safemode jail
Affects Red Hat Satellite 6.16 (RHEL 8 and RHEL 9), 6.17 (RHEL 9) and 6.18 (RHEL 9) where users can influence Foreman/Satellite template content. No fixed version is listed yet.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The attacker must be able to supply or influence Foreman/Satellite template content.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.47% · 41st percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 33/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
Red Hat Satellite 6 is affected by a flaw in the rubygem-safemode package, where compound assignment expressions in sandboxed code skip the Jail allow-list check. An attacker who can log in with low privileges and supply template content over the network can call arbitrary no-argument methods on objects exposed to the template renderer, which allows host deletion and disclosure of non-allow-listed object state.
Read the original description
A flaw was found in rubygem-safemode. Compound assignment expressions in sandboxed code are evaluated without mediating method calls through the Jail allow-list. An authenticated attacker who can supply template content can invoke arbitrary no-argument methods on objects exposed to the template renderer without Jail mediation, including destructive operations such as host deletion and disclosure of non-allow-listed object state.
Who should check
Teams running Red Hat Satellite 6.16, 6.17 or 6.18 where users can edit Foreman/Satellite templates
Read the source excerpt
“An authenticated user who can influence Foreman/Satellite template content”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Shipped in major Linux distributions
- Severity9.6/10CVSS 9.6
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 83 if added to CISA KEV
- Would score about 78 if CISA's SSVC rates exploitation active
- Would score about 40 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
The attacker must be able to supply or influence Foreman/Satellite template content.Workaround: Restrict template edit privileges to trusted administrators until a fixed safemode release is deployed.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-107360 (Rubygem-safemode: safemode: jail allow-list bypass via op-assign expressions), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-107360 (entry last updated 2026-11-12):
Affected:
- Red Hat Red Hat Satellite 6.16 for RHEL 8: version range not reported
- Red Hat Red Hat Satellite 6.16 for RHEL 9: version range not reported
- Red Hat Red Hat Satellite 6.17 for RHEL 9: version range not reported
- Red Hat Red Hat Satellite 6.18 for RHEL 9: version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- The attacker must be able to supply or influence Foreman/Satellite template content. (source: https://bugzilla.redhat.com/show_bug.cgi?id=2547645)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
Workaround: Restrict template edit privileges to trusted administrators until a fixed safemode release is deployed. (source: https://www.cve.org/CVERecord?id=CVE-2026-107360)
CISA KEV: CVE-2026-107360 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-107360 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://access.redhat.com/errata/RHSA-2026:99949
- https://access.redhat.com/errata/RHSA-2026:99950
- https://access.redhat.com/errata/RHSA-2026:99952
- https://bugzilla.redhat.com/show_bug.cgi?id=2547645
- https://access.redhat.com/security/cve/CVE-2026-107360
- https://www.cve.org/CVERecord?id=CVE-2026-107360
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-107360
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-107360"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- Record last updated
Affected versions
- rubygem-safemode
Version range not reported
- rubygem-safemode
Version range not reported
- rubygem-safemode
Version range not reported
- rubygem-safemode
Version range not reported
Evidence 8
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Public exploit code · 1
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Exploit
Write-ups · 1
Establishes: Technical detail and context.
- Report
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-107360
Is CVE-2026-107360 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The safemode Ruby gem's jail allow-list can be bypassed using op-assign expressions. The jail is meant to restrict what template content can run.Source: bugzilla.redhat.com, cve.org
Am I affected, and how do I check?
Red Hat lists Satellite 6.16 for RHEL 8, Satellite 6.16 for RHEL 9, Satellite 6.17 for RHEL 9 and Satellite 6.18 for RHEL 9. The issue applies where authenticated users can influence Foreman/Satellite template content, so compare the installed Satellite version and who holds template edit rights against these lists.Source: bugzilla.redhat.com, cve.org
How do I fix CVE-2026-107360?
No fixed version or patch is named yet. Restrict template edit privileges to trusted administrators until a fixed safemode release is deployed.Source: bugzilla.redhat.com, cve.org
What if there's no patch?
Restrict template edit privileges to trusted administrators until a fixed safemode release is deployed.Source: bugzilla.redhat.com, cve.org