Skip to main content
VulnerabilityPublished Updated

CVE-2025-23019: IETF IPv6 · Improper Verification of Source of a Communication Channel

Affects IETF IPv6Source CVE Database V5

0

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 17:16 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Jan 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
IETF IPv6Affected
  • =6
Fixed in–

AI-suggested

European organizations should implement strict ingress and egress filtering on network interfaces that handle IPv6-in-IPv4 tunneled traffic to ensure only legitimate source addresses are accepted. Network administrators must audit and restrict which interfaces are exposed to tunneled traffic and disable IPv6 tunneling where native IPv6 connectivity is available. Deploying deep packet inspection (DPI) tools capable of validating tunneling protocols can help detect and block spoofed packets. Monitoring network traffic for anomalies in tunneled IPv6 flows is critical to early detection of exploitation attempts. Organizations should also review firewall and router configurations to enforce source address validation and consider segmenting networks to limit the exposure of critical assets to tunneled traffic. Since no patches are currently available, these network-level controls are essential. Additionally, updating network device firmware and software when vendors release patches addressing this vulnerability is recommended. Training network security teams on this specific threat will improve incident response readiness.

Description

IPv6-in-IPv4 tunneling (RFC 4213) allows an attacker to spoof and route traffic via an exposed network interface.

References

Community reviews

Loading reviews…