CVE-2016-1896

CVE-2016-1896 is a critical-severity vulnerability in Lexmark Printer Firmware with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-254.

Key facts

Description

Race condition in the initialization process on Lexmark printers with firmware ATL before ATL.02.049, CB before CB.02.049, PP before PP.02.049, and YK before YK.02.049 allows remote attackers to bypass authentication by leveraging incorrect detection of the security-jumper status.

Frequently asked questions

What is CVE-2016-1896?
Race condition in the initialization process on Lexmark printers with firmware ATL before ATL.02.049, CB before CB.02.049, PP before PP.02.049, and YK before YK.02.049 allows remote attackers to bypass authentication by leveraging incorrect detection of the security-jumper status.
How severe is CVE-2016-1896?
CVE-2016-1896 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2016-1896 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (87th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-1896?
CVE-2016-1896 affects Lexmark Printer Firmware. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2016-1896?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2016-1896 published?
CVE-2016-1896 was published on 2016-01-27 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Lexmark Printer Firmware

All CVEs affecting Lexmark Printer Firmware →

Other CWE-254 vulnerabilities

Browse all CWE-254 vulnerabilities →