CVE-2026-1531

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (20th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
8.1EG
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.3%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in foreman_kubevirt. When configuring the connection to OpenShift, the system disables SSL verification if a Certificate Authority (CA) certificate is not explicitly set. This insecure default allows a remote attacker, capable of intercepting network traffic between Satellite and OpenShift, to perform a Man-in-the-Middle (MITM) attack. Such an attack could lead to the disclosure or alteration of sensitive information.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation0.3% × 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.3%
EPSS %ILE
20th
KEV
Not listed

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

February 2, 2026

Last Modified

July 15, 2026

Advisory Details (5)

Auto-updated Jun 30, 2026
Patch available. Sources: redhat.
Red HatMentions a patch (unverified)

2433786 – (CVE-2026-1531) CVE-2026-1531 foreman-kubevirt: foreman_kubevirt: Man-in-the-Middle due to insecure default SSL verification

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

cve-details

https://access.redhat.com/security/cve/CVE-2026-1531
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:5971
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:5970
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:5968

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrubygem-foreman_kubevirt-0:0.2.0-2.el9sat2026-03-26redhat
redhatrubygem-foreman_kubevirt-0:0.4.3-1.el9sat2026-03-26redhat
redhatyggdrasil-worker-forwarder-0:0.0.3-4.el9sat2026-03-26redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
foreman_kubevirt0.1.0 ... 0.4.2 (14 versions)
  • every version up to 0.4.3: fixed in 0.4.3
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 24× 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.

Showing the most recent 92 of 181 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 8 repeat rows among the latest 100 are merged into the row they repeat. The 89 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  4. 2026-10-12 16:32 UTCEG score recompute
  5. 2026-10-11 20:10 UTCEG score recompute
  6. 2026-10-11 17:22 UTCEG score recompute
  7. 2026-10-11 14:55 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  11. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  13. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  14. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  16. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  17. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  18. 2026-09-29 15:21 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  20. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  21. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  23. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  24. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  25. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
Show 67 more
  1. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  3. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  4. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  5. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  6. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  8. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  9. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  11. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  12. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  19. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  20. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  21. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  22. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  23. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  24. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  25. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  26. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  27. 2026-08-14 23:52 UTCVendor advisory
  28. 2026-08-14 11:44 UTCEG score recompute
  29. 2026-08-14 11:44 UTCVendor advisory
  30. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  31. 2026-08-13 03:53 UTCEG score recompute
  32. 2026-08-13 03:53 UTCVendor advisory
  33. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  34. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  35. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  36. 2026-08-10 10:06 UTCVendor advisory
  37. 2026-08-09 16:14 UTCEG score recompute
  38. 2026-08-09 16:14 UTCVendor advisory
  39. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  40. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  41. 2026-08-07 23:04 UTCEG score recompute
  42. 2026-08-07 23:04 UTCVendor advisory
  43. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  44. 2026-08-06 04:35 UTCEG score recompute
  45. 2026-08-06 04:35 UTCVendor advisory
  46. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  47. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  48. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  49. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  50. 2026-08-02 21:44 UTCEG score recompute
  51. 2026-08-02 21:44 UTCVendor advisory
  52. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  53. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  54. 2026-07-27 14:13 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  55. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  56. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  57. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  58. 2026-07-23 14:18 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  59. 2026-07-23 03:05 UTCEG score recompute
  60. 2026-07-22 14:08 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  61. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  62. 2026-07-20 17:08 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  63. 2026-07-19 14:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  64. 2026-07-19 02:28 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  65. 2026-07-18 10:04 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  66. 2026-07-16 17:03 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  67. 2026-07-15 16:57 UTCEPSS rescoreEPSS 0.3% · 19th percentile

Frequently asked(5)

What is CVE-2026-1531?
CVE-2026-1531 is a high-severity vulnerability; its CVE record was published on February 2, 2026. A flaw was found in foreman_kubevirt. When configuring the connection to OpenShift, the system disables SSL verification if a Certificate Authority (CA) certificate is not explicitly set. This insecure default allows a remote attacker, capable of intercepting network traffic between Satellite and…
When was CVE-2026-1531 made public?
CVE-2026-1531 was made public on January 28, 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 February 2, 2026. EchelonGraph's copy of the record carries a last-modified date of July 15, 2026; the record at its source may have been updated since.
Is CVE-2026-1531 actively exploited?
CVE-2026-1531 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-1531?
CVE-2026-1531 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-1531?
A fix for CVE-2026-1531 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-1531 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-1531

Explore →

Is Your Infrastructure Affected by CVE-2026-1531?

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