CVE-2026-100839

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

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

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-09-27. A secondary CVSS source baseline 8.4; 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

Also known asEUVD-2026-87849 (ENISA EUVD) · GHSA-qm93-38mp-vr3v (GitHub Security Advisories)Source: ENISA EUVD

8.4EG
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.1%CVSS: 8.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Contrast is a confidential-computing runtime for Kubernetes. In versions before 1.18.0, the guest kernel's ACPI/AML handling is vulnerable to an AML injection attack ("BadAML"). ACPI tables containing AML bytecode are passed from the untrusted host (QEMU) to the guest firmware (OVMF) and on to the Linux kernel, whose AML interpreter executes them. An attacker controlling the host — an assumed adversary in Contrast's threat model — can craft a table with malicious, Turing-complete AML bytecode that the guest kernel interprets with access to the full guest memory, including private pages, resulting in arbitrary code execution and disclosure or modification of confidential guest data. The issue affects the AMD SEV-SNP platforms Metal-QEMU-SNP and Metal-QEMU-SNP-GPU; Metal-QEMU-TDX is not affected because ACPI table contents are measured into RTMR 0 by OVMF on Intel TDX. Version v1.18.0 mitigates the attack by sandboxing the kernel AML interpreter so that it cannot read or write private memory pages. This weakness is not specific to Contrast but is generic to Confidential Computing setups that expose the ACPI interface to the host.

CVSS v3
8.4
EG Score
8.4HIGHmedium confidence
EG Risk
38
EG Risk 38/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)
Severity84% × 45%
Impact severity (EG Severity): CVSS 8.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 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.1%
EPSS %ILE
4th
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.4): severity, escalated by confirmed exploitation. This CVE's 8.4 is its impact severity (EG Severity), not escalated.

EG Severity
8.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). 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, and whom BOD 26-04 binds: 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.

The score's inputs: 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

September 27, 2026

Last Modified

October 8, 2026

Advisory Details (2)

Auto-updated Sep 27, 2026
Patch available. Sources: github.
Web page

Contrast before 1.18.0 AML Injection Remote Code Execution | Advisories | VulnCheck

https://www.vulncheck.com/advisories/contrast-before-1.18.0-aml-injection-remote-code-execution
GitHub advisoryMentions a patch (unverified)

BadAML - AML injection allows arbitrary code execution · Advisory · edgelesssys/contrast · GitHub

https://github.com/edgelesssys/contrast/security/advisories/GHSA-g9ww-x58f-9g6m

Vendor Advisories for CVE-2026-100839(1)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/edgelesssys/contrast—
  • every version up to 1.18.0: fixed in 1.18.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 70× 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 100 of 103 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. None are among the latest 100 rows. The 3 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  3. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  4. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  5. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  6. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  7. 2026-10-27 03:33 UTCEG score recompute
  8. 2026-10-27 03:32 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  9. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  11. 2026-10-25 15:57 UTCEG score recompute
  12. 2026-10-25 01:09 UTCEG score recompute
  13. 2026-10-25 01:09 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  14. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  21. 2026-10-18 05:11 UTCEG score recompute
  22. 2026-10-17 20:05 UTCEG score recompute
  23. 2026-10-17 20:05 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  24. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
Show 75 more
  1. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-10-12 16:41 UTCEG score recompute
  5. 2026-10-11 21:50 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  6. 2026-10-11 20:16 UTCEG score recompute
  7. 2026-10-11 18:28 UTCEG score recompute
  8. 2026-10-11 15:02 UTCEG score recompute
  9. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-11 10:56 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  11. 2026-10-10 23:59 UTCEG score recompute
  12. 2026-10-10 23:59 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  13. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-10 13:02 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  15. 2026-10-10 02:08 UTCEG score recompute
  16. 2026-10-10 02:08 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  17. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-09 15:14 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  19. 2026-10-09 03:26 UTCEG score recompute
  20. 2026-10-09 03:26 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  21. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-10-08 16:33 UTCEG score recompute
  23. 2026-10-08 16:32 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  24. 2026-10-08 15:37 UTCEG score recompute
  25. 2026-10-08 15:37 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  26. 2026-10-08 09:59 UTCEG score recompute
  27. 2026-10-08 09:59 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  28. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  29. 2026-10-07 23:05 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  30. 2026-10-07 12:12 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  31. 2026-10-07 01:16 UTCEG score recompute
  32. 2026-10-07 01:16 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  33. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  34. 2026-10-06 14:22 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  35. 2026-10-06 03:26 UTCEG score recompute
  36. 2026-10-06 03:26 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  37. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  38. 2026-10-05 16:32 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  39. 2026-10-05 05:39 UTCEG score recompute
  40. 2026-10-05 05:39 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  41. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  42. 2026-10-04 18:45 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  43. 2026-10-04 07:45 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  44. 2026-10-03 20:52 UTCEG score recompute
  45. 2026-10-03 20:52 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  46. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  47. 2026-10-03 09:58 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  48. 2026-10-02 22:59 UTCEG score recompute
  49. 2026-10-02 22:59 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  50. 2026-10-02 12:05 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  51. 2026-10-02 01:08 UTCEG score recompute
  52. 2026-10-02 01:08 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  53. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  54. 2026-10-01 14:14 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  55. 2026-10-01 03:20 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  56. 2026-09-30 16:27 UTCEG score recompute
  57. 2026-09-30 16:27 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  58. 2026-09-30 15:31 UTCEG score recompute
  59. 2026-09-30 15:31 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  60. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  61. 2026-09-30 11:09 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  62. 2026-09-30 00:15 UTCEG score recompute
  63. 2026-09-30 00:15 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  64. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  65. 2026-09-29 13:21 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  66. 2026-09-29 02:24 UTCEG score recompute
  67. 2026-09-29 02:24 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  68. 2026-09-28 15:30 UTCEG score recompute
  69. 2026-09-28 15:30 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  70. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  71. 2026-09-28 11:17 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  72. 2026-09-28 00:24 UTCEG score recompute
  73. 2026-09-28 00:24 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4
  74. 2026-09-27 13:30 UTCEG score recompute
  75. 2026-09-27 13:30 UTCGHSA enrichmentGHSA-qm93-38mp-vr3v · GitHub severity HIGH · GitHub CVSS 8.4

Frequently asked(5)

What is CVE-2026-100839?
CVE-2026-100839 is a high-severity vulnerability; its CVE record was published on September 27, 2026. Contrast is a confidential-computing runtime for Kubernetes. In versions before 1.18.0, the guest kernel's ACPI/AML handling is vulnerable to an AML injection attack ("BadAML"). ACPI tables containing AML bytecode are passed from the untrusted host (QEMU) to the guest firmware (OVMF) and on to the…
When was CVE-2026-100839 made public?
CVE-2026-100839 was made public on March 24, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 27, 2026. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-100839 actively exploited?
CVE-2026-100839 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100839?
CVE-2026-100839 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100839?
A fix for CVE-2026-100839 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100839 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-100839

Explore →

Is Your Infrastructure Affected by CVE-2026-100839?

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