CVE-2026-116676

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-27. 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
Elevated

Also known asEUVD-2026-111231 (ENISA EUVD) · GHSA-rjh2-4xgw-p2hj (GitHub Security Advisories) · GO-2026-6871 (OSV.dev)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Atlantis is a self-hosted golang application that listens for Terraform pull request events via webhooks. From version 0.4.0 until 0.47.1, Atlantis passes the pull-request-controlled workspace value from atlantis.yaml into Terraform command arguments that are joined with strings.Join(args, " ") and executed through sh -c. An authenticated contributor whose pull request is eligible for an Atlantis plan can include shell metacharacters in the workspace name, causing arbitrary commands to execute as the Atlantis service account without custom workflows, apply permission, or a malicious Terraform provider. External contributors can reach the flaw through fork pull requests only when --allow-fork-prs is enabled, while eligible same-repository branches do not require that option. The commands inherit the Atlantis process environment and can access cloud-provider, Terraform, and version-control credentials as well as files, state, and network resources available to the service. This issue is fixed in version 0.47.1.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
56
EG Risk 56/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.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
40th
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.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). 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, Track* at medium and Attend at high mission impact.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, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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

October 27, 2026

Last Modified

November 3, 2026

Advisory Details (5)

Auto-updated Oct 27, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github, github_pr.
GitHub release Patch Available

v0.47.1

Patch available: runatlantis/atlantis v0.47.1

https://github.com/runatlantis/atlantis/releases/tag/v0.47.1
GitHub commit

commit f04df0d53f05 (runatlantis/atlantis)

Fix landed in runatlantis/atlantis commit f04df0d53f05 — awaiting tagged release

https://github.com/runatlantis/atlantis/commit/f04df0d53f0544d9eb6f5026dd8b74fbefd82ac8
GitHub commit

commit 8dd22b4d0a9d (runatlantis/atlantis)

Fix landed in runatlantis/atlantis commit 8dd22b4d0a9d — awaiting tagged release

https://github.com/runatlantis/atlantis/commit/8dd22b4d0a9d7c129fdbf6a3398dd1c4cf8c3a59
GitHub pull request

fix: prevent pull request input from reaching a shell (GHSA-rjh2-4xgw-p2hj)

Fix merged in runatlantis/atlantis PR #6792 on 2026-08-20 — awaiting tagged release

https://github.com/runatlantis/atlantis/pull/6792
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

OS command injection through PR-controlled Terraform workspace enables RCE during plan · Advisory · runatlantis/atlantis · GitHub

https://github.com/runatlantis/atlantis/security/advisories/GHSA-rjh2-4xgw-p2hj

Vendor Advisories for CVE-2026-116676(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/runatlantis/atlantis @ 0.47.1 (fixes >= 0.4.0, <= 0.47.0)—ghsa

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)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/runatlantis/atlantis—
  • 0.4.0 up to 0.47.1: fixed in 0.47.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 23× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  3. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  4. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-11-09 20:34 UTCEchelonGraph re-scored
  6. 2026-11-09 20:34 UTCGHSA enrichmentGHSA-rjh2-4xgw-p2hj · GitHub severity HIGH · GitHub CVSS 8.8
  7. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  10. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-11-03 12:26 UTCEchelonGraph re-scored
  15. 2026-11-03 12:26 UTCGHSA enrichmentGHSA-rjh2-4xgw-p2hj · GitHub severity HIGH · GitHub CVSS 8.8
  16. 2026-11-03 11:52 UTCEchelonGraph re-scored
  17. 2026-11-03 11:52 UTCGHSA enrichmentGHSA-rjh2-4xgw-p2hj · GitHub severity HIGH · GitHub CVSS 8.8
  18. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-rjh2-4xgw-p2hj · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-11-01 07:59 UTCEchelonGraph re-scored
  22. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
Show 4 more
  1. 2026-10-27 18:27 UTCEchelonGraph re-scored
  2. 2026-10-27 18:01 UTCENISA EUVD ID recordedEUVD-2026-111231 · Source: ENISA EUVD
  3. 2026-10-27 17:19 UTCEchelonGraph re-scoredFirst assessed: 8.8 HIGH
  4. 2026-10-27 17:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-116676?
CVE-2026-116676 is a high-severity vulnerability; its CVE record was published on October 27, 2026. Atlantis is a self-hosted golang application that listens for Terraform pull request events via webhooks. From version 0.4.0 until 0.47.1, Atlantis passes the pull-request-controlled workspace value from atlantis.yaml into Terraform command arguments that are joined with strings.Join(args, " ") and…
When was the CVE record for CVE-2026-116676 published?
The CVE record for CVE-2026-116676 was published on October 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 3, 2026; the record at its source may have been updated since.
Is CVE-2026-116676 actively exploited?
CVE-2026-116676 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-116676?
CVE-2026-116676 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-116676?
A fix for CVE-2026-116676 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-116676 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-116676

Explore →

Is Your Infrastructure Affected by CVE-2026-116676?

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