CVE-2026-100839

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH confidence

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, ghsa, secondary
Trending — 3 sources updated this week
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • 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.4HIGHhigh confidence
EG Risk
38
EG Risk 38/100CISA SSVC

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
Severity84% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 27, 2026

Last Modified

September 30, 2026

Advisory Details (2)

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

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 Patch Available

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 rangeFixed inDependents
github.com/edgelesssys/contrast—1.18.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 33× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-04 07:45 UTCGHSA enrichment
  2. 2026-10-03 20:52 UTCEG score recompute
  3. 2026-10-03 20:52 UTCGHSA enrichment
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-03 09:58 UTCGHSA enrichment
  6. 2026-10-02 22:59 UTCEG score recompute
  7. 2026-10-02 22:59 UTCGHSA enrichment
  8. 2026-10-02 12:05 UTCGHSA enrichment
  9. 2026-10-02 01:08 UTCEG score recompute
  10. 2026-10-02 01:08 UTCGHSA enrichment
  11. 2026-10-01 19:49 UTCEPSS rescore
  12. 2026-10-01 14:14 UTCGHSA enrichment
  13. 2026-10-01 03:20 UTCGHSA enrichment
  14. 2026-09-30 16:27 UTCEG score recompute
  15. 2026-09-30 16:27 UTCGHSA enrichment
  16. 2026-09-30 15:31 UTCEG score recompute
  17. 2026-09-30 15:31 UTCGHSA enrichment
  18. 2026-09-30 15:02 UTCEPSS rescore
  19. 2026-09-30 11:09 UTCGHSA enrichment
  20. 2026-09-30 00:15 UTCEG score recompute
  21. 2026-09-30 00:15 UTCGHSA enrichment
  22. 2026-09-29 15:20 UTCEPSS rescore
  23. 2026-09-29 13:21 UTCGHSA enrichment
  24. 2026-09-29 02:24 UTCEG score recompute
  25. 2026-09-29 02:24 UTCGHSA enrichment
Show 11 more
  1. 2026-09-28 15:30 UTCEG score recompute
  2. 2026-09-28 15:30 UTCGHSA enrichment
  3. 2026-09-28 13:50 UTCEPSS rescore
  4. 2026-09-28 11:17 UTCGHSA enrichment
  5. 2026-09-28 00:24 UTCEG score recompute
  6. 2026-09-28 00:24 UTCGHSA enrichment
  7. 2026-09-27 13:30 UTCEG score recompute
  8. 2026-09-27 13:30 UTCGHSA enrichment
  9. 2026-09-27 02:37 UTCEG score recompute
  10. 2026-09-27 01:53 UTCEG score recompute
  11. 2026-09-27 01:49 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-100839?
CVE-2026-100839 is a high vulnerability 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 disclosed?
CVE-2026-100839 was first published on September 27, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 (3rd 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.

Book a Demo →Browse All CVEs