Sign2Shell: how to approve signing software updates
A signing extension can reach software installed on a workstation. Sign2Shell provides a useful basis for deciding what to verify before approving an update.
Leer en portuguésBy Pentesty
The workstation is part of the signing workflow
On November 17, 2026, Bay Area Labs published its Sign2Shell research, covering Lacuna Web PKI, Softplan Web Signer, Certisign WebSigner, CertiPlugin and BRy Assinatura Digital. The researchers report that vulnerable versions allowed pages to influence which libraries the native program loaded. The resulting code ran with the logged-in Windows user’s permissions.
The estimate of roughly ten million installations combines browser stores; it does not represent confirmed victims or workstations that remain vulnerable today. The demonstrations required Windows and the vendor’s native component. The extension bridges the page and that program, an architecture also described in Lacuna’s documentation. An inventory confined to application servers misses this dependency.
Record what each correction actually addresses
The authors classify four products as fixed and CertiPlugin as mitigated through origin restrictions, with its underlying library-loading behavior unchanged. In the responses published by CISO Advisor, Certisign says it implemented corrections and made updated versions available. Keep these positions attributed to their respective sources; a general assurance alone does not establish which path was blocked.
Bry and Certisign also state that they have no records of exploitation. The research says it did not investigate exploitation in the wild and cannot rule it out. The study therefore does not establish intrusions at vendors’ named customers, certificate theft or fraudulent signatures. An environment assessment should record its own findings before extending those conclusions.
Define the evidence required for approval
We propose acceptance by workstation group and signing workflow. Record the owner, authorized scope, previous condition and subsequent result; a completed installation is only one piece of that evidence.
Check which user runs the component and its effective permissions over files, networks and test certificates. Lacuna’s documentation says its program does not need administrative privileges to operate. Record local exceptions: elevating privileges to work around an integration difficulty extends the process’s reach and requires a separate decision, rather than becoming an undocumented support shortcut.
- Identify the extension, store, browser, profile, version and native component. In Lacuna’s changelog, the extension, JavaScript library and native program have separate versions. Compare the correct component with the corresponding guidance.
- Confirm deployment on the machines actually used, including managed profiles and shared workstations. Retain the management tool’s report and a locally checked sample instead of assuming automatic updates reached everyone.
- In an isolated, authorized environment, sign a synthetic document through the approved portal and check the result. Include a controlled check that an unapproved origin does not receive the same authorization, without using third-party pages or running malicious payloads.
- If there is concrete evidence of abuse, preserve workstation records and establish which credentials, files and sessions were reachable. Decisions to revoke certificates or rebuild a machine depend on that investigation and the procedure agreed with its owners.
Keep the service working without extending trust
A physical token protects custody of its key, but that property does not establish the integrity of every workstation operation. The research describes risks within the user’s execution context; it does not show that all tokens were extracted or compromised. Avoid turning a technical possibility into a confirmed incident.
Restoration needs stop conditions, an owner for exceptions and another review when the browser or component changes. Connect this work to checking authentication paths: improving passwords does not replace verifying the software operating on the device.
Frequently asked questions
Do ten million installations mean ten million victims?
No. This is the researchers’ estimate from browser stores. It measures neither currently vulnerable machines nor confirmed exploitation.
Does updating the extension alone finish the assessment?
Do not assume so. Identify the native program, the deployed version and the authorized workflow that must continue to function.
Is CertiPlugin fixed or mitigated?
The researchers describe mitigation; Certisign says corrections are available. Request evidence for the specific component and the behavior it blocks.
Does the research prove theft of every certificate’s key?
No. It documents code-execution paths. Establishing a compromise and its scope requires evidence from the environment under investigation.
Sources and references
- CISO Advisor: research and vendor responses
- Bay Area Labs: original Sign2Shell research, November 17
- Lacuna: Web PKI architecture and authorization
- Lacuna: separate extension, library and native-component changelogs
Original Pentesty analysis, published November 17, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.