Skip to main content
VulnerabilityPublished Updated

CVE-2026-58085: After dispatching a decrypt operation to OCF and receiving the result, the wg(4) driver failed to

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-58085· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

AI-suggested

Until an official fix is available, users should consider restricting UDP access to WireGuard endpoints to trusted sources and monitor for unusual activity. Avoid relying on the affected FreeBSD wg(4) driver for critical security until patched.

Description

The wg(4) driver in FreeBSD fails to verify the success of the MAC (Poly1305) authentication step after decrypting packets. This flaw allows remote attackers who can send UDP packets to a WireGuard endpoint and guess the replay window bounds to inject forged or modified transport data packets into the tunnel. Additionally, attackers intercepting WireGuard packets can modify ciphertext and authenticated data without detection.

References

Community reviews

Loading reviews…