Zarro Technology · Security briefing

Today’s shorter update revisits the Alpine/musl OpenSSH flaw following new evidence of successful exploitation on monitored systems. This changes the urgency of outstanding remediation, while the observed activity does not establish compromise of unrelated production servers.

1. Alpine OpenSSH: successful honeypot exploitation now observed (Critical)

CVE-2026-123158

What changed

GreyNoise’s 8 November update reports 14 confirmed post-exploitation sessions, with the first successful exploitation observed on 7 November. Its definition requires shell-command execution on a vulnerable monitored system. These are honeypot observations, not a count of affected customer organisations. This is a material development since our 6 November patch briefing.

Exposure and remediation

The bypass affects musl-based Linux running sshd without PAM password checks, with password authentication enabled, an asterisk password field on a target account, and another local account with a SHA-crypt password hash. Alpine identifies releases 3.16–3.24 and edge. Containers that do not run sshd are outside this exposure.

Install Alpine’s fixed package for your branch and restart sshd. Fixed packages can retain older upstream version numbers because fixes are backported: consult Alpine’s package matrix. Point releases 3.21.10, 3.22.8, 3.23.8 and 3.24.4 include the correction; upstream mitigation is in 10.6p2.

If updating is delayed, disable password authentication, validate the configuration and restart the daemon. Test working key access first and retain your current session and recovery-console access. Server configuration:

PasswordAuthentication no

Checks and IoCs

GreyNoise attributes 7 November activity to source 20.255.63.133 and reports an uploaded file at /opt/py3/tac_agent.py. Search retained SSH authentication records for that source and unexpected successful password logins to accounts intended for keys only. Check endpoint/file telemetry for the reported path. These indicators are specific to observed sensor activity; addresses may be shared and filenames can change.

On an Alpine host, this read-only check reports file metadata if the path exists; root may be required for access:

ls -l /opt/py3/tac_agent.py

A match warrants investigation and evidence preservation; no match does not establish safety. Review authorised keys, accounts and privilege changes if unauthorised access is suspected. Patching closes the bypass but does not remove an existing intrusion. Critical follows OpenSSH’s qualitative assessment; no numeric score is asserted here.

Sources: GreyNoise: current sensor observations and incident indicators · Alpine: conditions, fixed package matrix and restart guidance

Zarro Technology