SecurityBrief Australia - Technology news for CISOs & cybersecurity decision-makers
Australia
HP patches three high-severity flaws in Easy Start

HP patches three high-severity flaws in Easy Start

Sat, 5th Sep 2026 (Today)
Joseph Gabriel Lagonsin
JOSEPH GABRIEL LAGONSIN News Editor

HP has patched three high-severity vulnerabilities in its Easy Start software for macOS. The issues affect versions of the printer setup utility released before HP Easy Start 2.16.7.260722.

Cipher Security Labs published technical research on the flaws, assigned CVE-2026-12554, CVE-2026-12555 and CVE-2026-12556. The vulnerabilities involve software download methods, temporary file handling during privileged operations and transport security in a tool used to discover HP printers and install related software on Apple devices.

The research examined HP Easy Start 2.16.0 build 251010 and described how several security assumptions intersected in a single installation workflow. In the analysed version, the software downloaded components, handled temporary files and then carried out installation steps with administrative privileges.

The most severe issue, CVE-2026-12554, received a CVSS 4.0 score of 8.5. It involved an unmaintained OSPFTP download stack that remained in the software installation path.

Static analysis found that OSPFTP download classes and fallback URL scheme mechanisms were still tied to component acquisition. The concern was not that every installation necessarily relied on FTP, but that an obsolete FTP-capable component remained accessible within a privileged software delivery process.

CVE-2026-12555 and CVE-2026-12556 both received severity ratings of 7.7. CVE-2026-12555 involved predictable temporary file paths used by the HP Uninstaller while running with administrative rights.

In the analysed build, fixed names were used under /tmp and /private/tmp. An unprivileged local user could place a symbolic link at the expected log path before the user approved the standard macOS elevation prompt.

After the prompt was accepted, the elevated uninstaller followed the link and appended HP-generated log data to an attacker-chosen file as the root user. The research described this as privileged file modification or corruption rather than unrestricted arbitrary file writing, because an attacker could choose the destination path but not the content written.

The third flaw, CVE-2026-12556, concerned cleartext software download transport. In the affected version, HP Easy Start allowed arbitrary loads through macOS App Transport Security settings and also included an FTP fallback in the download stack.

That combination broadened the conditions in which a network-positioned attacker could interfere with component acquisition if a primary download route failed. The analysis also stressed that it did not conclude that all installations used FTP, that the transport setting by itself bypassed certificate validation or that a network attacker would automatically gain code execution.

Design changes

The updated 2.16.7 build included broader changes than direct fixes for the three cited weaknesses. Cipher Security Labs said the vulnerable Uninstaller bundle was removed, the OSPFTP-related software download components and FTP markers were gone, broad App Transport Security relaxation had been tightened, and an older privileged helper design had been replaced.

The research also noted a separate design issue involving HP Easy Start's former SWHelper component, which used Apple's deprecated AuthorizationExecuteWithPrivileges API. It confirmed the presence of the legacy interface and a path-oriented privileged installation workflow, but did not demonstrate a full package-swap time-of-check to time-of-use exploit in the production staging path.

As a result, the observation was not treated as a fourth vulnerability identifier. Instead, it was described as a risky privilege-boundary design with conditional exploitability.

In the patched build, the replacement helper architecture uses SMAppService and NSXPCConnection. The helper restricts clients by code-signing identity and checks a supplied SHA-256 value against an already open file descriptor before invoking the macOS installer.

Research findings

The case highlights the security risks around installer software that combines downloads, file system activity and elevated permissions. Such utilities often receive less public scrutiny than browsers or endpoint security products, even though they can occupy a similarly sensitive point in the software chain.

In this case, the issues did not all lead to the same outcome. The local flaw depended on predictable file paths and user-approved privilege elevation, while the network-related issue depended on download path conditions and did not by itself establish code execution.

The research also drew a clear distinction between what it demonstrated directly and what it considered plausible only under additional environmental conditions.

"Privileged installers deserve the same scrutiny as security-sensitive services because they sit at the intersection of network input, filesystem state and administrative authority," said Nir Yehoshua, Founder and Lead Researcher, Cipher Security Labs.

Yehoshua said the findings mattered because multiple small trust assumptions appeared within a single administrative workflow.

"The interesting part of this case is not any single bug in isolation. It is how small trust decisions - a reusable temporary path, an obsolete download component or a relaxed transport policy - become more important when they exist inside one privileged software-delivery workflow," said Yehoshua.

The research group also set limits on its conclusions about exploitability, saying the public analysis was intended to distinguish between directly observed behaviour and attack chains that would require additional steps.

"We also wanted the public analysis to be precise about what was and was not proven. We demonstrated privileged write-through a symbolic link and documented live cleartext and legacy download surfaces, but we did not turn every design concern into a stronger exploitation claim than the evidence supports. Responsible vulnerability research should preserve those boundaries," said Yehoshua.