CVE-2026-58085
CVE-2026-58085 — Missing MAC validation in wg(4) packet decryption
After dispatching a decrypt operation to OCF and receiving the result, the wg(4) driver failed to check whether the MAC verification step succeeded. The driver thus silently accepted packets with an invalid Poly1305 authentication tag. A remote attacker who can send UDP packets to a WireGuard endpoint, and who can guess the bounds of the receiver's replay window, can inject forged or modified transport data packets into the tunnel. A remote attacker who can intercept WireGuard packets bound for a FreeBSD host can modify the ciphertext and authenticated data without detection by the receiver.
Published Updated Sources: NVD, FreeBSD (CNA), GitHub, SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
Unscored
no source published a base score
Remediation
The vendor's own words where we have them.
Upgrade FreeBSD to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| FreeBSD | FreeBSD | 15.1-RELEASE | Vulnerable |
| FreeBSD | FreeBSD | 15.0-RELEASE | Vulnerable |
| FreeBSD | FreeBSD | 14.4-RELEASE | Vulnerable |
What this weakness leads to
MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.
CWE-347 · Improper Verification of Cryptographic Signature
- Gain Privileges or Assume Identity
- Modify Application Data
- Execute Unauthorized Code or Commands
Weakness & attack patterns
- CWE-347
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Initial · CVE published
Aug 19, 2026 · NVD
References
1 on the record
- security.freebsd.org/advisories/FreeBSD-SA-26:52.if_wg.asc
Vendor Advisory
Elsewhere on this site
- FreeBSDevery CVE for this vendor
- Remote Code Execsame class
- CWE-347other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-58085 is Missing MAC validation in wg(4) packet decryption, a unscored vulnerability affecting FreeBSD from FreeBSD. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-58085. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-58085. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS null describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.