PatchTheCVECVE-2017-7239: Ninka before 1.3.2 might allow remote attackers to obtain sensitive information, manipulate license compliance
CVE-2017-7239 is a critical-severity flaw (CVSS 9.8) affecting ninka. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Ninka before 1.3.2 might allow remote attackers to obtain sensitive information, manipulate license compliance scan results, or cause a denial of service (process hang) via a crafted filename.
Why this priority
- Critical severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 3.6% (top 11%) |
| CISA exploited list | No |
| Weakness | CWE-74 |
| Published | 2017-04-10 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2017-7239?
ninka: upgrade to newer than 1.3.0. Exact commands for each OS are on this page.
Is CVE-2017-7239 being exploited?
CVE-2017-7239 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2017-7239 affect?
CVE-2017-7239 affects ninka. Severity is critical (CVSS 9.8). Ninka before 1.3.2 might allow remote attackers to obtain sensitive information, manipulate license compliance scan results, or cause a denial of service (process hang) via a crafted filename.
How urgent is CVE-2017-7239?
Priority 62/100. Critical severity; Remotely exploitable, no login, no user action