BSD Ports

Erlang/OTP -- TLS hostname verification bypass via Subject CommonName fallback and name constraints

· CVE-2026-42790 · VuXML entry

https://github.com/erlang/otp/security/advisories/GHSA-22cw-4ph4-6447 reports: Erlang/OTP's TLS hostname verification implements a legacy RFC 6125 fallback that checks the Subject CommonName when the Subject Alternative Name (SAN) extension is absent, rather than following RFC 9525 which requires validation to fail without SAN. Combined with weak handling of X.509 Name Constraints, this enables man-in-the-middle …

Affected versions

By system

3 still vulnerable, 4 fixed. Where VuXML applies (FreeBSD, DragonFly, FreeBSD's derivatives) a port is vulnerable while its version is in a range; pkgsrc says itself whether it lists a CVE of this advisory; OpenBSD and MidnightBSD keep no list this site reads, so their row is only an estimate: FreeBSD's ranges applied to upstream's version.

SystemPortVersionStateFixed
DragonFlylang/erlang25.3.2.7_1,4 vulnerable since 2026-05-28
NetBSDlang/erlang27.3.4.7 not listed
MidnightBSDlang/erlang25.3.2.20_1,4 in range, by version
FreeBSDlang/erlang28.5.0.8_1,4 fixed (61 days after)
DragonFlylang/erlang-runtime2727.3.4 vulnerable since 2026-05-28
FreeBSDlang/erlang-runtime2727.3.4.19_1 fixed (61 days after)
DragonFlylang/erlang-runtime2828.0 vulnerable since 2026-05-28
MidnightBSDlang/erlang-runtime2828.5.0.8 out of range, by version
FreeBSDlang/erlang-runtime2828.5.0.8_1 fixed (61 days after)
FreeBSDlang/erlang-runtime2929.1.2_1 fixed (36 days after)