Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA redhat

CVE-2026-12405: Rubygem-foreman_remote_execution: command injection in job invocations via effective_user parameter

Noroxi assessment

Priority: Monitor (action score 35/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 75.7% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: foreman (Red Hat:satellite_capsule:6.16::el8) 0:3.12.0.23-1.el8sat; foreman-debug (Red Hat:satellite_capsule:6.16::el8) 0:3.12.0.23-1.el8sat; foreman-pcp (Red Hat:satellite_capsule:6.16::el8) 0:3.12.0.23-1.el8sat.

Low priority for now. Upgrade to foreman (Red Hat:satellite_capsule:6.16::el8) 0:3.12.0.23-1.el8sat; foreman-debug (Red Hat:satellite_capsule:6.16::el8) 0:3.12.0.23-1.el8sat; foreman-pcp (Red Hat:satellite_capsule:6.16::el8) 0:3.12.0.23-1.el8sat or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A flaw was found in rubygem-foreman_remote_execution. A command injection vulnerability exists in the Red Hat Satellite API (/api/v2/job_invocations). When a job template has the effective_user property marked as overridable: true, the application fails to properly sanitize the effective_user input provided during the API request. The exploitation does not rely on the content or logic of the Job Template/playbook itself; rather, the injection occurs during the instantiation of the job execution environment by the Satellite server. An attacker with permissions to execute job templates can inject arbitrary shell commands into this parameter, which are executed on the target infrastructure with the privileges of the execution user.

HighCVSS 8.8 · v3.1—No exploit Fix available
Published
Oct 1, 2026
Updated
Nov 2, 2026
EPSS
1.5% · 75th percentile

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · redhat
8.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-12405

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • Red Hat Red Hat Satellite 6

    • all versionsaffected
  • Red Hat Red Hat Satellite 6.16 for RHEL 8

    • 0:13.2.8-2.el8sat and laternot affected · rpm
  • Red Hat Red Hat Satellite 6.16 for RHEL 9

    • 0:13.2.8-2.el9sat and laternot affected · rpm
  • Red Hat Red Hat Satellite 6.17 for RHEL 9

    • 0:15.0.2-2.el9sat and laternot affected · rpm
  • Red Hat Red Hat Satellite 6.18 for RHEL 9

    • 0:16.2.3-2.el9sat and laternot affected · rpm
  • Red Hat Red Hat Satellite 6.19 for RHEL 9

    • 0:16.5.3-2.el9sat and laternot affected · rpm

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Red Hat:satellite_capsule:6.16::el8foremanbefore 0:3.12.0.23-1.el8sat0:3.12.0.23-1.el8sat
Red Hat:satellite_capsule:6.16::el8foreman-debugbefore 0:3.12.0.23-1.el8sat0:3.12.0.23-1.el8sat
Red Hat:satellite_capsule:6.16::el8foreman-pcpbefore 0:3.12.0.23-1.el8sat0:3.12.0.23-1.el8sat
Red Hat:satellite_capsule:6.16::el8python-dynaconfbefore 0:3.2.13-1.el8pc0:3.2.13-1.el8pc
Red Hat:satellite_capsule:6.16::el8python-gitpythonbefore 0:3.1.62-1.el8pc0:3.1.62-1.el8pc
Red Hat:satellite_capsule:6.16::el8python-lxmlbefore 0:4.9.2-5.el8pc0:4.9.2-5.el8pc
Red Hat:satellite_capsule:6.16::el8python-lxml-debugsourcebefore 0:4.9.2-5.el8pc0:4.9.2-5.el8pc
Red Hat:satellite_capsule:6.16::el8python-pulpcorebefore 0:3.49.39-4.el8pc0:3.49.39-4.el8pc
Red Hat:satellite_capsule:6.16::el8python-sqlparsebefore 0:0.6.0-1.el8pc0:0.6.0-1.el8pc
Red Hat:satellite_capsule:6.16::el8python3.11-dynaconfbefore 0:3.2.13-1.el8pc0:3.2.13-1.el8pc
Red Hat:satellite_capsule:6.16::el8python3.11-gitpythonbefore 0:3.1.62-1.el8pc0:3.1.62-1.el8pc
Red Hat:satellite_capsule:6.16::el8python3.11-lxmlbefore 0:4.9.2-5.el8pc0:4.9.2-5.el8pc
Red Hat:satellite_capsule:6.16::el8python3.11-lxml-debuginfobefore 0:4.9.2-5.el8pc0:4.9.2-5.el8pc
Red Hat:satellite_capsule:6.16::el8python3.11-pulpcorebefore 0:3.49.39-4.el8pc0:3.49.39-4.el8pc
Red Hat:satellite_capsule:6.16::el8python3.11-sqlparsebefore 0:0.6.0-1.el8pc0:0.6.0-1.el8pc
Red Hat:satellite_capsule:6.16::el8satellitebefore 0:6.16.14-1.el8sat0:6.16.14-1.el8sat
Red Hat:satellite_capsule:6.16::el8satellite-capsulebefore 0:6.16.14-1.el8sat0:6.16.14-1.el8sat
Red Hat:satellite_capsule:6.16::el8satellite-commonbefore 0:6.16.14-1.el8sat0:6.16.14-1.el8sat
Red Hat:satellite_capsule:6.16::el9foremanbefore 0:3.12.0.23-1.el9sat0:3.12.0.23-1.el9sat
Red Hat:satellite_capsule:6.16::el9foreman-debugbefore 0:3.12.0.23-1.el9sat0:3.12.0.23-1.el9sat
Red Hat:satellite_capsule:6.16::el9foreman-pcpbefore 0:3.12.0.23-1.el9sat0:3.12.0.23-1.el9sat
Red Hat:satellite_capsule:6.16::el9python-lxmlbefore 0:4.9.2-5.el9pc0:4.9.2-5.el9pc
Red Hat:satellite_capsule:6.16::el9python-lxml-debugsourcebefore 0:4.9.2-5.el9pc0:4.9.2-5.el9pc
Red Hat:satellite_capsule:6.16::el9python-pulpcorebefore 0:3.49.39-4.el9pc0:3.49.39-4.el9pc

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-56097Rubygem-katello: sql injection in registry proxy via labels
    26Monitor
  • CVE-2026-12545Rubygem-hammer_cli: command injection via insecure editor invocation
    26Monitor
  • CVE-2026-56098Rubygem-katello: improper authorization logic allows resource enumeration
    17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
red hat:foreman0:3.18.0.14-1.el9sat · Red Hat:satellite_capsule:6.19::el9Package registry (OSV)
red hat:foreman-cli0:3.18.0.14-1.el9sat · Red Hat:satellite_utils:6.19::el9Package registry (OSV)
red hat:foreman-debug0:3.18.0.14-1.el9sat · Red Hat:satellite_capsule:6.19::el9Package registry (OSV)
red hat:foreman-dynflow-sidekiq0:3.18.0.14-1.el9sat · Red Hat:satellite:6.19::el9Package registry (OSV)
red hat:foreman-ec20:3.18.0.14-1.el9sat · Red Hat:satellite:6.19::el9Package registry (OSV)
red hat:foreman-journald0:3.18.0.14-1.el9sat · Red Hat:satellite:6.19::el9Package registry (OSV)
red hat:foreman-libvirt0:3.18.0.14-1.el9sat · Red Hat:satellite:6.19::el9Package registry (OSV)
red hat:foreman-openstack0:3.18.0.14-1.el9sat · Red Hat:satellite:6.19::el9Package registry (OSV)
red hat:foreman-pcp0:3.18.0.14-1.el9sat · Red Hat:satellite_capsule:6.19::el9Package registry (OSV)
red hat:foreman-postgresql0:3.18.0.14-1.el9sat · Red Hat:satellite:6.19::el9Package registry (OSV)
red hat:rubygem-foreman_remote_execution0:16.5.3-2.el9sat · Red Hat:satellite:6.19::el9Package registry (OSV)
red hat:rubygem-foreman_remote_execution-cockpit0:16.5.3-2.el9sat · Red Hat:satellite:6.19::el9Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recorded+1 d
  3. TodayNov 9, 2026+39 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-125450 days apartRubygem-hammer_cli: command injection via insecure editor invocation
    26Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const host = req.body.host;exec("ping -c 1 " + host, onResult);

Fixed

ts
const host = req.body.host;if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);execFile("ping", ["-c", "1", host], onResult);

Change log

  1. Fix✗ → ✓
  2. SSVC exploitation— → none
  3. Exploit maturity— → none

For records you follow, these changes also arrive as notifications. →

References

All records