Dropbear skips permitopen checks on unix-socket forwarding
First merged summary.
Restricted Dropbear SSH keys can still forward to unix sockets such as docker.sock; no fix or CVE is named.
Posts to oss-security and Full Disclosure say Dropbear, the small SSH server used on routers, embedded systems and appliances, does not enforce permitopen and permitlisten when forwarding to unix sockets. Those authorized_keys options are meant to limit a key to a named host and port. The reporter says a restricted key can still reach docker.sock, and calls the issue live-proven on HEAD 99baf182. Neither post names a CVE or a fixed release.
- Bug is in unix-socket forwarding, not host:port checks.
- permitopen and permitlisten are the restricted-key options involved.
- Reporter says docker.sock is reachable through a restricted key.
- Cited revision is HEAD commit 99baf182; issue called live-proven.
- No patch version or CVE is named.
Timeline
dated events in the reporting · oldest first- Nov 13, 2026oss-security reports the unix-socket forwarding bypass. · oss-security
- Nov 17, 2026Full Disclosure reposts the same Dropbear claim. · Full Disclosure
What each outlet adds
beyond the shared facts- oss-securityNames routers and appliances and HEAD 99baf182 as live-proven.
- Full DisclosureNovember 17 repost; no CVE or fix in the cut-off text.
- Products
- Dropbear
Coverage
oldest first · one row per article · UTCDropbear skips permitopen and permitlisten on unix-socket forwarding
A restricted SSH key can still reach unix sockets such as docker.sock; shown on HEAD 99baf182.
Dropbear ignores permitopen limits on unix-socket forwarding
A Full Disclosure post says a restricted key can reach docker.sock; the claim is tied to HEAD 99baf182.