Xerox AltaLink B8045/B8055/B8065/B8075/B8090 and C8030/C8035/C8045/C8055/C8070 multifunction printers with software releases before 101.00x…

published 2021-03-04 5y ago modified 2026-06-17 4mo ago also EUVD-2019-8351

cvss: 4.9; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits: 0; none known

Xerox AltaLink B8045/B8055/B8065/B8075/B8090 and C8030/C8035/C8045/C8055/C8070 multifunction printers with software releases before 101.00x.099.28200 allow a user with administrative privileges to turn off data encryption on the device, thus leaving it open to potential cryptographic information disclosure.

Patch / fix

fixed in 10 links 1

xerox altalink_b8045_firmware 103.008.010.14010
xerox altalink_b8055_firmware 103.008.010.14010
xerox altalink_b8065_firmware 103.008.010.14010
xerox altalink_b8075_firmware 103.008.010.14010
xerox altalink_b8090_firmware 103.008.010.14010
xerox altalink_c8030_firmware 103.001.010.14010
xerox altalink_c8035_firmware 103.001.010.14010
xerox altalink_c8045_firmware 103.002.010.14010
xerox altalink_c8055_firmware 103.002.010.14010
xerox altalink_c8070_firmware 103.003.010.14010

securitydocs.business.xerox.com/wp-content/uploads/2021/03/cert_Security_Mini_Bulletin_XRX… advisory

Is CVE-2019-18628 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.66% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	4.9	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	4.0	AV:N/AC:L/Au:S/C:P/I:N/A:N

References

securitydocs.business.xerox.com /wp-content/uploads/2021/03/cert_Security_Mini_Bulletin_XRX20I_for_ALB80xx-C80xx_v1.1.pdf
patch, vendor-advisory
security.business.xerox.com
vendor-advisory

Sources

CVE List CVE-2019-18628
NVD CVE-2019-18628

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.