CVE-2016-8649

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-14. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
9.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: 2.8%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

lxc-attach in LXC before 1.0.9 and 2.x before 2.0.6 allows an attacker inside of an unprivileged container to use an inherited file descriptor, of the host's /proc, to access the rest of the host's filesystem via the openat() family of syscalls.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
42
EG Risk 42/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)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation2.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
2.8%
EPSS %ILE
86th
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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

May 1, 2017

Last Modified

June 17, 2026

Advisory Details (6)

Auto-updated Aug 1, 2026
Patch available. Sources: redhat, github_commit.
Red HatMentions a patch (unverified)

1398242 – (CVE-2016-8649) CVE-2016-8649 lxc: lxc-attach to malicious container allows access to host

https://bugzilla.redhat.com/show_bug.cgi?id=1398242
Web page

Bug #1639345 “lxc-attach to malicious container allows access to...” : Bugs : lxc package : Ubuntu

https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1639345
Web pageMentions a patch (unverified)

#845465 - lxc: CVE-2016-8649: attach: do not send procfd to attached process - Debian Bug report logs

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845465
Web page

SecurityFocus

http://www.securityfocus.com/bid/94498
Web page

CVE-2016-8649

https://security-tracker.debian.org/tracker/CVE-2016-8649
GitHub commit Patch Available

commit 81f466d05f2a (lxc/lxc)

Patch available: lxc/lxc v6.0.0 (contains commit 81f466d05f2a)

https://github.com/lxc/lxc/commit/81f466d05f2a89cb4f122ef7f593ff3f279b165c

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulxc1 (2.0.5-0ubuntu1.2) @ yakkety2026-05-22ubuntu

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
lxc—
  • every version up to 1:2.0.6-1: fixed in 1:2.0.6-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
lxc—
  • every version up to 1:2.0.6-1: fixed in 1:2.0.6-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
lxc—
  • every version up to 1:2.0.6-1: fixed in 1:2.0.6-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
lxc—
  • every version up to 1:2.0.6-1: fixed in 1:2.0.6-1
—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 27× 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 88 of 153 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. 12 repeat rows among the latest 100 are merged into the row they repeat. The 65 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2016-8649?
CVE-2016-8649 is a critical-severity vulnerability; its CVE record was published on May 1, 2017. lxc-attach in LXC before 1.0.9 and 2.x before 2.0.6 allows an attacker inside of an unprivileged container to use an inherited file descriptor, of the host's /proc, to access the rest of the host's filesystem via the openat() family of syscalls.
When was CVE-2016-8649 made public?
CVE-2016-8649 was made public on May 1, 2017: 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 May 1, 2017. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2016-8649 actively exploited?
CVE-2016-8649 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.8% probability of exploitation in the next 30 days (86th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2016-8649?
CVE-2016-8649 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2016-8649?
A fix for CVE-2016-8649 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2016-8649

Explore →

Is Your Infrastructure Affected by CVE-2016-8649?

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

Book a Demo →Browse All CVEs