Skip to main content
VulnerabilityPublished

CVE-2026-4748: FreeBSD · Use of Incorrect Operator

Affects FreeBSDSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 12 Nov 2026, 00:47 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.17.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Apr 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 11 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Freebsdfreebsd/freebsdpkg:deb/freebsd/freebsdOther threatsAffected
  • =15.0-RELEASE
  • =14.4-RELEASE
  • =14.3-RELEASE
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, users should review pf configurations for rules using the address range syntax and consider rewriting them using the address[/mask-bits] syntax, which is not affected. Monitoring for vendor updates and applying official patches when released is recommended.

Description

CVE-2026-4748 is a vulnerability in FreeBSD's packet filter (pf) where a regression in hash calculation causes rules with address range syntax (x.x.x.x - y.y.y.y) that differ only in the address ranges to be silently dropped as duplicates. This results in only the first such rule being loaded, potentially causing unexpected behavior including overblocking or underblocking of network traffic. Some action keywords like 'log', 'return tll', or 'dnpipe' may also be affected, though such configurations are unlikely. Ranges using the address[/mask-bits] syntax are not impacted.

References

Community reviews

Loading reviews…