VPN technology

OpenVPN 2.7.8 was released around 6–7 October 2026 as a maintenance update with four security-hardening items. Three carry CVE IDs: CVE-2026-84790 (NULL bytes in certificate subjects), CVE-2026-88964 (unsigned underflow in domain-search / PUSH_REPLY handling on Windows and Android for versions 2.7_alpha3 through 2.7.7), and CVE-2026-84256 (continued Windows CreateProcess/cmd.exe quoting hardening). A fourth tls-crypt-v2 change that stops clients from blindly resending wrapped keys when no key material is available was left without a CVE under Italy CRA robustness policy. The release also improves multi-client DCO stability, including restarting a single instance instead of crashing the whole server when a peer key install races with peer removal. Linux Compatible notes the release was tagged by Gert Doering after about 22 commits across 40 files from 11 contributors, riding on the 2.7.0 architectural overhaul from February. Operators running multi-client servers or kernel-accelerated DCO should treat 2.7.8 as an availability and security maintenance release rather than a feature drop. Certificate tooling teams must inventory subject strings for embedded NULL bytes before OpenSSL fleets upgrade, because previously accepted certificates may suddenly fail handshake checks. Windows administrators should regression-test scripts that shell out through CreateProcess around OpenVPN after the continued quoting hardening.

If you run community OpenVPN 2.7.x clients on Windows/Android or multi-client DCO servers, schedule 2.7.8 and re-test certificate inventories for embedded NULL bytes. Record package versions and advisory URLs in the change ticket before closing the item.

Source: Linux Compatible

The OpenVPN community wiki’s CVE-2026-88964 page states that an integer underflow allows remote authenticated servers to cause denial of service or memory disclosure via crafted domain search options, names Cole Munz as reporter, links GitHub private issue OpenVPN/openvpn-private-issues#178, and points operators to the openvpn-2.7.8 ReleaseHistory entry dated 7 October 2026. The wiki also links the community ReleaseHistory anchor for openvpn-2.7.8 released 7 October 2026 and the private GitHub issue path used during coordinated disclosure. Readers should treat PUSH_REPLY DNS search domains as sensitive option material: only trusted servers should be allowed to push them, and client About screens should be captured after upgrade to prove 2.7.8 or newer is running on Windows and Android endpoints in the previously affected 2.7.x window.

Treat PUSH_REPLY DNS search options from only trusted servers and confirm client About screens show 2.7.8+ after upgrade. Record package versions and advisory URLs in the change ticket before closing the item.

Source: OpenVPN community wiki

Internet security

On 5 October 2026, Linux kernel mailing list discussion of a WireGuard noise patch described a failure mode where WireGuard can accept an old handshake response after a newer initiation has started, reinstalling old keys and resetting transport counters and replay state. That would enable nonce reuse, replay, and packet forgery, breaking confidentiality and integrity guarantees. The proposed fix compares ephemeral secrets under the write lock to reject responses for replaced initiations; Jason A. Donenfeld questioned the exact flow in reply on the same thread. The thread emphasizes that accepting a stale handshake response after a newer initiation has begun can reinstall older keys and reset replay state. That is a confidentiality and integrity concern for in-kernel WireGuard peers, distinct from userspace VPN brand apps. Distributions should be monitored for stable backports; do not assume a mailing-list patch is already present in every kernel package your fleet runs.

Kernel and distribution WireGuard consumers should watch stable backports of handshake-response rejection patches and avoid assuming userspace VPN apps alone cover in-kernel WireGuard peers. Record package versions and advisory URLs in the change ticket before closing the item.

Source: LKML / IU archive

NVD’s record for CVE-2026-13735 describes a Zephyr RTOS WireGuard implementation bug: keepalive (16-byte empty plaintext plus Poly1305 tag) messages were accepted before decryption, so the Poly1305 tag was never verified. An attacker who knew or brute-forced a cleartext receiver index could spoof keepalive status signals without session keys. The fix forces 16-byte payloads through decryption and anti-replay checks. Impact is limited to integrity of status signals, not plaintext injection or session takeover. The NVD description clarifies that forged keepalives fail Poly1305 verification after the fix and are counted as authentication failures. No plaintext is decrypted or injected in the pre-fix path, and endpoints and liveness timers were not updated by the early return, so traffic injection and session takeover are out of scope for this particular defect. Product security teams should still patch because spoofed VPN-connected signals can mislead management planes and operators.

Embedded/IoT products shipping Zephyr WireGuard should pull the authenticated-keepalive fix and not equate this CVE with Linux kernel WireGuard. Record package versions and advisory URLs in the change ticket before closing the item.

Source: NVD — CVE-2026-13735

Regulation

Linux Compatible’s 2.7.8 write-up notes that Italy’s Computer Resilience Agency (CRA) guidelines were cited as the reason a tls-crypt-v2 client-disruption fix received no CVE: a malicious server stopping a client from working properly was classified as robustness degradation rather than a confidentiality or integrity failure. That policy choice does not remove the operational need to patch, but it does change how compliance ticketing systems may label the change. Security programs that only open tickets when a CVE ID exists will miss this class of change unless release-note review is part of the intake process. Document the CRA rationale in the ticket body and still require staging verification for tls-crypt-v2 clients after 2.7.8, because availability failures against authenticated peers remain expensive during incident response.

Security programs should track non-CVE robustness fixes in VPN clients when CRA-style policies omit identifiers. Record package versions and advisory URLs in the change ticket before closing the item.

Source: Linux Compatible

Forums

OpenVPN’s public CVE wiki entry for 88964 cross-links the private GitHub issue tracker path OpenVPN/openvpn-private-issues#178 and the community ReleaseHistory anchor for 2.7.8, illustrating the project’s pattern of publishing reporter names and private-issue numbers alongside release notes rather than silent patches. Starting from project-owned security announcement pages reduces the risk of chasing incomplete secondary summaries. Cross-check reporter names, private-issue references, and ReleaseHistory anchors before closing vulnerability tickets as mitigated.

When triaging VPN CVEs, start from the project’s own security announcement wiki and ReleaseHistory anchors before secondary aggregators. Record package versions and advisory URLs in the change ticket before closing the item.

Source: OpenVPN community wiki

Vendors

Linux Compatible reports that OpenVPN Inc.’s Access Server team filed the iroute race bug fixed in 2.7.8, where per-client routes were removed during delayed multi-instance cleanup instead of at actual client-exit time, risking systems left with no routes under reconnect races. The same article notes external research groups such as BreachX (certificate NULL-byte report) feeding the 2.7.x security cadence. Staging should include reconnect storms that exercise route install and removal while clients flap. If routes disappear under load after upgrade, capture netlink and instance logs before rolling further. BreachX’s involvement in the certificate NULL-byte report also illustrates why external research pipelines matter to OpenVPN’s 2.7.x cadence.

Access Server and large DCO operators should validate route cleanup behavior on staging after 2.7.8 before production waves. Record package versions and advisory URLs in the change ticket before closing the item.

Source: Linux Compatible