CVERadar
CRITICAL · CVSS 3.1 9.6EPSS 0.51% (p44)Threat level 48

CVE-2026-107360: CVE-2026-107360: A flaw was found in rubygem-safemode. Compound assignment expressions in sandboxed code ar…

Unknown · · NVD published 2026-11-13 · posted 2026-11-12 · last modified 2026-11-13

CVE-2026-107360 at a glance

CVE-2026-107360 is a critical-severity vulnerability in the affected product, with a CVSS 3.1 base score of 9.6. NVD published it on 2026-11-13 and classifies the weakness as CWE-183. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 0.51% (percentile 44.2, scored 2026-11-14). NVD does not list a fixed version, so the vendor advisory is the reference for the fix. Its CVERadar threat level is 48/100.

What it is

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.

WeaknessCWE-183 definition
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N (source: Red Hat)
ATT&CK tacticsn/a

Exploitation evidence

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

GitHub proof-of-concept repositories below quality bar

1 public repositories from 1 accounts, first seen 2026-11-13.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: nomi-sec/PoC-in-GitHub.

No ATT&CK techniques could be mapped or inferred for this CVE yet.

Patches, mitigations and detection

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

No vendor-tagged reference yet; see the full reference list.

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources