CVE-2026-104795

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-14. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The insights-runtime-extractor runs as a privileged DaemonSet (hostPID: true) that scans container processes for runtime fingerprinting. When scanning a container, the coordinator:

  • fork()s a child process
  • setns() into the target container's PID and mount namespaces
  • fchdir() back to an orphaned FD pointing at the extractor's own root
filesystem (where /crio.sock is hostPath-mounted)
  • Calls only seteuid(target_uid) — changing the effective UID but leaving
the real UID and saved-set-UID at 0 and **retaining the permitted capability set**
  • The check_no_privileged_perms() guard inspects only the Effective capability
set (so it passes), and is skipped entirely when the target runs as uid 0
  • The VersionExecutable fingerprint invokes fpr_kind_executable with
process.command_line[0] — the target's argv[0], read from /proc//cmdline and fully controlled by the workload
  • fpr_kind_executable calls exec.Command(executable, "--version").Output()
— executing the workload's own binary inside the workload's mount namespace while ruid=0 in the host user namespace

The executed process can call setuid(0) to restore full root with CAP_SYS_ADMIN, and inherits the orphaned cwd which resolves into the extractor container's filesystem containing the host CRI-O socket.

Affected Code

1. Insufficient privilege drop (Rust — extractor coordinator)

File: extractor/src/insights_runtime_extractor.rs

// Lines 139-146 — seteuid-only drop, guard skipped for root containers
join_process_namespaces(process.pid)?;
change_dir(current_dir);
switch_user(*process.uid)?;
if *process.uid != 0 {
    perms::check_no_privileged_perms()
        .expect("Must not have privileged permissions to run fingerprints");
}
fingerprint::run_fingerprints(&config, out_dir, &process);

// Lines 182-185 — only effective UID changed; ruid/suid stay 0
fn switch_user(uid: u32) -> Result<(), ScannerError> {
    debug!("... Becoming user: {uid}");
    seteuid(uid.into()).map_err(|e| ScannerError::Errno(e))
}

2. Execution of untrusted binary (Go — fingerprint)

File: fingerprints/pkg/utils/file.go

// Lines 75-80 — executes a path taken verbatim from workload's argv[0]
func GetExecutableVersionOutput(executable string) (string, error) {
    out, err := exec.Command(executable, "--version").Output()
    if err != nil {
        return "", err
    }
    return string(out), nil
}

3. Workload-controlled path forwarded (Rust — version_executable)

File: version_executable.rs

// Lines 29-34 — workload-controlled command_line[0] forwarded to fingerprint
return Some(vec![
    fpr_kind_executable,
    out_dir.to_string(),
    String::from(&process.command_line[0]),
    String::from(&version_executable.runtime_kind_name),
]);

Attack Pattern

Attacker: Any tenant able to schedule a pod (unprivileged, any namespace) Victim: The node running the insights-runtime-extractor DaemonSet Trigger: Automatic — the DaemonSet scans all container processes on the node

Attack sequence:

  • Attacker creates a pod whose process name matches a configured
versioned-executable pattern (node, python, python3, MainThread, or contains java)
  • The pod's main binary (at the path matching argv[0]) is a malicious
executable that calls setuid(0) to restore root
  • When the insights operator triggers a scan, the DaemonSet forks, enters the
attacker's mount namespace, and executes the attacker's binary with ruid=0
  • The attacker's code regains full root with CAP_SYS_ADMIN in the host user
namespace
  • The inherited cwd contains the host CRI-O socket → full node compromise

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 14, 2026

Last Modified

October 20, 2026

Advisory Details (2)

Auto-updated Oct 14, 2026
Patch available. Sources: redhat.
Red Hat

2543917 – (CVE-2026-104795) CVE-2026-104795 insights-runtime-extractor: insights-runtime-extractor: Container Escape via Privileged Binary Execution

https://bugzilla.redhat.com/show_bug.cgi?id=2543917
Red HatMentions a patch (unverified)

CVE-2026-104795 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-104795

Vendor Advisories for CVE-2026-104795(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 21× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-20 13:27 UTCEG score recompute
  4. 2026-10-20 13:26 UTCGHSA enrichmentGHSA-98f3-7g2j-289q · GitHub severity HIGH · GitHub CVSS 8.8
  5. 2026-10-20 13:09 UTCEG score recompute
  6. 2026-10-20 13:09 UTCGHSA enrichmentGHSA-98f3-7g2j-289q · GitHub severity HIGH · GitHub CVSS 8.8
  7. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-10-18 05:09 UTCEG score recompute
  10. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-10-15 16:47 UTCEG score recompute
  13. 2026-10-15 16:47 UTCGHSA enrichmentGHSA-98f3-7g2j-289q · GitHub severity HIGH · GitHub CVSS 8.8
  14. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-10-14 17:13 UTCEG score recompute
  16. 2026-10-14 17:13 UTCGHSA enrichmentGHSA-98f3-7g2j-289q · GitHub severity HIGH · GitHub CVSS 8.8
  17. 2026-10-14 15:41 UTCEG score recompute
  18. 2026-10-14 15:40 UTCGHSA enrichmentGHSA-98f3-7g2j-289q · GitHub severity HIGH · GitHub CVSS 8.8
  19. 2026-10-14 11:29 UTCEG score recompute
  20. 2026-10-14 11:02 UTCEG score recomputeFirst assessed: 8.8 HIGH
  21. 2026-10-14 10:59 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-104795?
CVE-2026-104795 is a high-severity vulnerability; its CVE record was published on October 14, 2026. The insights-runtime-extractor runs as a privileged DaemonSet (hostPID: true) that scans container processes for runtime fingerprinting. When scanning a container, the coordinator: 1. fork()s a child process 2. setns() into the target container's PID and mount namespaces 3. fchdir() back to an…
When was CVE-2026-104795 made public?
CVE-2026-104795 was made public on October 14, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on October 14, 2026. EchelonGraph's copy of the record carries a last-modified date of October 20, 2026; the record at its source may have been updated since.
Is CVE-2026-104795 actively exploited?
CVE-2026-104795 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-104795?
CVE-2026-104795 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-104795?
A fix for CVE-2026-104795 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-104795 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-104795

Explore →

Is Your Infrastructure Affected by CVE-2026-104795?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.