CVE-2026-82017
Physical boot-parameter injection in IGEL OS allows arbitrary boot-time code execution.
Is CVE-2026-82017 being exploited?
Not confirmed. CVE-2026-82017 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.15% probability of exploitation in the next 30 days.
How severe is CVE-2026-82017?
CVE-2026-82017 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-82017?
Yes. A fix has been recorded for CVE-2026-82017. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-82017 affect?
CVE-2026-82017 affects IGEL OS 12 < 12.7.6, IGEL OS 11 < 11.11.150, IGEL thin clients running affected OS. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-82017?
Upgrade to IGEL OS 12.7.6 or 11.11.150, restrict physical access, verify device integrity.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker with physical access can inject kernel cmdline to execute arbitrary boot-time code and gain boot/root privileges, bypassing TPM PCR detection.
Immediate action required
- affected>= 11.0.0 and < 11.11.150
- affected>= 12.0.0 and < 12.7.6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.