Loading vulnerability…
CVE-2026-84790 is a certificate name validation vulnerability affecting OpenVPN, including the Debian Linux package. When certificate name verification is enabled through --verify-x509-name, embedded null bytes copied by extract_x509_field_ssl() can cause an incorrect certificate name to be accepted. A name containing the expected identity followed by a null byte and additional characters can pass verification against the expected identity, bypassing the intended name check.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An OpenVPN certificate-name verification flaw when using OpenSSL allows embedded null bytes in certificate fields to cause an incorrect name to be accepted. The advisory rates it Important, with CVSS v3.1 score 7.4 and vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N. An upstream fix is identified in OpenVPN v2.7.8, commit cf4384eef4676a01bd3ee98fa602f7b2af8079ea, while fixes for the listed Amazon Linux packages remain pending.
A reported critical vulnerability affecting the OpenVPN package in Debian Linux, with a CVSS v3 base score of 9.8. The listed vector indicates network accessibility, low attack complexity, no required privileges or user interaction, and high confidentiality, integrity, and availability impacts. The content does not describe the underlying flaw or exploitation mechanism. Nessus detects exposure based on vendor-reported package presence rather than demonstrated exploitation.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.