CVE-2017-9110

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2022-05-13. NVD baseline CVSS 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 6.5Exploit: None knownExposed: 0

A fix is available — apply it.

In OpenEXR 2.2.0, an invalid read of size 2 in the hufDecode function in ImfHuf.cpp could cause the application to crash.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

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
Severity65% × 45%
Exploitation2% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
77%
KEV
Not listed

Published

May 21, 2017

Last Modified

June 17, 2026

Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.

Frequently asked(5)

What is CVE-2017-9110?
CVE-2017-9110 is a medium vulnerability published on May 21, 2017. In OpenEXR 2.2.0, an invalid read of size 2 in the hufDecode function in ImfHuf.cpp could cause the application to crash.
When was CVE-2017-9110 disclosed?
CVE-2017-9110 was first published in the National Vulnerability Database on May 21, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-9110 actively exploited?
CVE-2017-9110 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 23.5% of all scored CVEs.
What is the CVSS score of CVE-2017-9110?
CVE-2017-9110 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2017-9110?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-9110, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-9110

Explore →

Is Your Infrastructure Affected by CVE-2017-9110?

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