CVE-2025-23018

CVE-2025-23018 is a medium-severity vulnerability in Ietf Ipv6 with a CVSS 3.x base score of 5.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-940.

Key facts

Description

IPv4-in-IPv6 and IPv6-in-IPv6 tunneling (RFC 2473) do not require the validation or verification of the source of a network packet, allowing an attacker to spoof and route arbitrary traffic via an exposed network interface. This is a similar issue to CVE-2020-10136.

Frequently asked questions

What is CVE-2025-23018?
IPv4-in-IPv6 and IPv6-in-IPv6 tunneling (RFC 2473) do not require the validation or verification of the source of a network packet, allowing an attacker to spoof and route arbitrary traffic via an exposed network interface. This is a similar issue to CVE-2020-10136.
How severe is CVE-2025-23018?
CVE-2025-23018 has a CVSS 3.x base score of 5.4, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.
Is CVE-2025-23018 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (59th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-23018?
CVE-2025-23018 affects Ietf Ipv6. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-23018?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-23018 have an EU (EUVD) identifier?
Yes. CVE-2025-23018 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-3076.
When was CVE-2025-23018 published?
CVE-2025-23018 was published on 2025-01-14 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Ietf Ipv6

All CVEs affecting Ietf Ipv6 →

Other CWE-940 vulnerabilities

Browse all CWE-940 vulnerabilities →