How severe is CVE-2017-1000212?

CVE-2017-1000212 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-1000212?

CVE-2017-1000212 affects the following packages: alchemist.vim (Hex). Ecosystems affected: Hex.

How do I fix CVE-2017-1000212?

Update alchemist.vim to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000212 is resolved across your whole dependency graph.

How do I detect CVE-2017-1000212 in my Hex dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for alchemist.vim, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2017-1000212 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2017-1000212 actively exploited in the wild?

No public exploit code has been indexed for CVE-2017-1000212 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2017-1000212?

CVE-2017-1000212 has an EPSS (Exploit Prediction Scoring System) score of 2.9%, placing it in the 87th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2017-1000212 published, and has it been updated?

CVE-2017-1000212 was published on May 13, 2022 and was last updated on December 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💧

💧 Hex

Not in CISA KEV

CRITICAL severity

CVE-2017-1000212 — alchemist.vim

CRITICALFix: tonini/alchemist-server#16

CVE-2017-1000212 is a critical-severity (CVSS 9.8) remote code execution vulnerability in alchemist.vim. A fix is available for alchemist.vim — see the affected versions and patch details below.

alchemist.vim vulnerable to remote code execution

Published

May 13, 2022

Updated

Dec 10, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs87th percentile — riskier than 87% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

💧alchemist.vim

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Hex packages — download data is not available via public APIs for these ecosystems.

Description

Elixir's vim plugin, alchemist.vim is vulnerable to remote code execution in the bundled alchemist-server. A malicious website can execute requests against an ephemeral port on localhost that are then evaluated as elixir code.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💧Hex	`alchemist.vim`	all versions	1.3.2`mix deps.update alchemist.vim`

Affected Products

1 product · 1 configurations

Application

alchemist-serveralchemist-elixir

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for alchemist.vim, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update alchemist.vim to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000212 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-1000212 in your dependencies?

Find it across Hex, including transitive dependencies.

Scan my dependencies How O3 SCA works